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...
Currently Deep History is sorted by Build ID on initial loading of that view. In certain cases we have Build IDs that are greater than the most recent runs in...
jdk21 Pipeline triggerred both hotspot and temurin variant on aarch64-linux. Build pipeline https://ci.adoptium.net/job/build-scripts/job/openjdk21-pipeline/188/ . And get the grid result summary as followings [CryptoTests_0](https://trss.adoptium.net/output/test?id=6500bfe917052c67151bb7cb) => [deep history 0/32 passed](https://trss.adoptium.net/deepHistory?testId=6500bfe917052c67151bb7cb) | [possible...
x86-64_linux does not show up in TRSS as part of the most recent release build (see [tree view](https://github.com/adoptium/aqa-tests/issues/4723#issuecomment-1697201125) below, also not present in grid view), need to figure out why...
We need to support FIPS builds in TRSS: fips140_2 and fips_3_YYYYMMDD. And remove fips build. 
**Motivation** The current issue triage process often relies on manual analysis and decision-making by developers, which can be time-consuming and error-prone. And the increasing volume and complexity of software issues...
TRSS ML user feedback has been able to be stored in DB with PR https://github.com/adoptium/aqa-test-tools/pull/798. Regarding `accuracy`, we would like to replace it with `positive feedback` and `negative feedabck`, and...
The testOutput file name while storing user feedback should be sanitized. Issue details: 
TRSS monitors Jenkins's job. It would be nice if there was a link from the Jenkins build (top-level) to TRSS (both Build view and Grid view). It will make it...
Since we upgrade the node, we should upgrade to 18. 16 is out of active support and security support for 16 will end in Sep 2023. _Originally posted by @llxia...
We currently pull and parse information from Jenkins pipelines, but do not include the queue time (how long a job waits for a particular machine resource). It will be useful...