Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Triage.md #4299

Merged
merged 2 commits into from
Feb 2, 2023
Merged

Update Triage.md #4299

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
86ec588
Update Triage.md
vedant-z Feb 1, 2023
4daf6d4
Update Triage.md
vedant-z Feb 2, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 12 additions & 7 deletions doc/Triage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,18 @@
# Test Triage at Adoptium

## TRSS Parser for Release Builds
## Generate a Release Summary Report

We've created a NodeJS module to parse TRSS output, convert it to Markdown so folks can paste that summary into a GitHub issue.
Locate the pipeline you wish to triage in the ["By Pipeline" view](https://trss.adoptium.net/tests/Test) of TRSS.

```bash
npm install -g trss-parser
trss-parser <parent id of TRSS pipeline run>
```
![image](https://user-images.githubusercontent.com/93431609/216171285-c313c957-6c8e-49df-95dd-6a68a9897f90.png)

Navigate to the Grid view by clicking on the Grid link for the pipeline you wish to triage and click on the Release Summary Report button at the top of the Grid view page.

![image](https://user-images.githubusercontent.com/93431609/216171387-abebba1d-0ff7-46a9-b486-8aba8fc4bcbc.png)

Click on the 'Copy` icon and paste the .md formatted content into a new Github issue that you wish to use to track triage investigation.

![image](https://user-images.githubusercontent.com/93431609/216171428-705c1933-eea4-4598-a9f2-e488c229bab0.png)

## Triage Guidance

Expand All @@ -25,7 +30,7 @@ There are many different test jobs running at the adoptium project. No matter w

### Raise an issue if no issue exists

- infra issue - raise an issue in [openjdk-infrastructure](https://github.com/adoptium/infrastructure/issues)
- infra issue - raise an issue in [infrastructure](https://github.com/adoptium/infrastructure/issues)
- test issue - ideally, there are enough details to determine which test repo to raise an issue in ond of the test repositories from which test material is pulled (OpenJDK, [aqa-systemtest](https://github.com/adoptium/aqa-systemtest/issues), [aqa-tests](https://github.com/adoptium/aqa-tests/issues) or any of the various 3rd party application suites). If in doubt, ask some questions in the [#testing channel](https://adoptium.slack.com/archives/C5219G28G) and/or raise in [aqa-tests](https://github.com/adoptium/aqa-tests/issues) where it will get routed to proper repo
- OpenJDK test issues - see [Guidance for creating OpenJDK bugs](https://github.com/adoptium/aqa-tests/wiki/Guidance-for-Creating-OpenJDK-Test-Defects)
- Additional guidance for external tests - [Triage Rules for Application tests](https://github.com/adoptium/aqa-tests/tree/master/external#triage-rules)
Expand Down