Fix confusing test results for known-broken jobs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
E.g. { experiment: systemcrypto, os: windows, arch: amd64, config: test, distro: '2019', broken: true }
Currently the known-broken jobs still submit test results to AzDO, and the AzDO test viewer doesn't indicate that the tests were expected to fail. This should be fixed to avoid misleading results and wasting time on known failures.
A simple fix that preserves the data and would probably work well enough would be to prepend "(BROKEN)" to the job name, because it shows up in the test viewer and has to be expanded before seeing any of the misleading failures.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the code that submits known-broken jobs and their test results to AzDO. Check how the job name reaches the AzDO test viewer, then verify that known-broken results retain their data while being visibly marked as expected failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100