Home of Test Results Summary Service (TRSS) and PerfNext. These tools are designed to improve our ability to monitor and triage tests at the Adoptium project. The code is generic enough that it is extensible for use by any project that needs to monitor multiple CI servers and aggregate their results.
Due to various reasons (i.e., invalid builds, network issues, and query before the build is fully created, etc), TRSS may not have access to the builds. Currently, we retry 3 times, then set the build status to Done. This is to prevent wasting resources to query invalid builds or expired builds. However, in the case of temporary network issues or query before the build is fully created, we may want to wait for a while and retry or repopulate/recan the build.
ToDo:
add 2 secs sleep between each retry
add AuditLogs when the error code is 404 (for debugging purposes)
We have noticed that sleep 2secs is not enough in some cases. It is hard to predict how long TRSS should wait for Jenkins server to come back when there is a network issue. To increase the efficiency and reliability of TRSS, we removed the sleep logic completely. The logic is updated to check the header in the response to determine the invalid/expired build case. See https://github.com/adoptium/aqa-test-tools/pull/858
For security reasons, we may not want to add a button for rescanning builds on UI at this point.
Due to various reasons (i.e., invalid builds, network issues, and query before the build is fully created, etc), TRSS may not have access to the builds. Currently, we retry 3 times, then set the build status to Done. This is to prevent wasting resources to query invalid builds or expired builds. However, in the case of temporary network issues or query before the build is fully created, we may want to wait for a while and retry or repopulate/recan the build.
ToDo:
related: backlog/issues/1388