We're not considering test failures a problem
Open
- Dominant language
- C++
- Stars
- 61
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/MirServer/wlcs/blob/f2161a11c57529f40b3ae208bfca151ed381ba1c/spread/build/ubuntu/task.yaml#L28-L33
So e.g. MirServer/mir#2823 was caused by canonical/mir#267.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with spread/build/ubuntu/task.yaml at lines 28-33 and inspect how test results are handled. Use the MirServer/mir#2823 and canonical/mir#267 references as examples, then verify that a failing test causes the relevant task to be reported as a failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100