aqa-test-tools
aqa-test-tools copied to clipboard
adoptium
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 e...
### Problem Description Currently, TRSS supports parsing of both PerfNext and Perffarm jobs. While PerfNext builds that use Jenkins are parsed right away after runs are done, Perffarm builds are...
### Problem Description Currently, Perf Graph uses hard-coded names for pipelines. We should dynamically get this list from the database by looking at all the perf pipelines stored in it...
### Problem Description Currently, all benchmark configs are using older version of benchmarks. We should update them to these latest benchmarks. | Current Version | Version to Use -- |...
### Problem Description Currently, TRSS has 2 parsing mechanisms for extract benchmark metric values. First mechanism is used for Jenkins, which is used by PerfNext and Adopt builds, to parse...
### Problem Description Currently, we fetch the latest machine data file every time PerfNext is loaded. If some benchmark is selected and the machine data hasn't been fetched yet—fetching that...
With the current code, we are using a single node when running TRSS server. As we monitor more and more projects, the TRSS server can be very busy to process...
Test Result Summary is using the Jenkins term "build" incorrectly instead of "project" in some places. So it's easy to get confused when the code might actually be referring to...
Currently, for internal testing, we are using `master_machine_list.xml`, a file that has info about all machines regarding their HW and specific benchmark variables, with PerfNext to dynamically populate HW specific...
### Problem Description Originally, we were running multiple iterations of the benchmarks in one Jenkins build (i.e. Old design). Now, we're moving to a new design in https://github.com/AdoptOpenJDK/openjdk-test-tools/issues/24 in which...
### Relevant Code Snippet https://github.com/AdoptOpenJDK/openjdk-test-tools/blob/414ec78d4edadf6542ba2a53357e73037494ba21/TestResultSummaryService/JenkinsInfo.js#L64-L77 `JenkinsInfo.js` can't use the password that has special characters such as "!" to communicate with Jenkins properly, giving 401 Unauthorized error. ### Helpful Links https://github.com/jansepar/node-jenkins-api...