element-hq / element-hq/element-web
Sonarcloud scan can fail but still be marked successful
- Dominant language
- TypeScript
- Stars
- 13.5k
- Forks
- 2.8k
- PR merge metrics
- PR metrics pending
Description
### Steps to reproduce
The sonarcloud job failed due to a network / server flake but was marked successful. This left the actual results job just pending forever.
https://github.com/matrix-org/matrix-react-sdk/actions/runs/8629722585/job/23654502439
### Outcome
#### What did you expect?
#### What happened instead?
### Operating system
_No response_
### Application version
_No response_
### How did you install the app?
_No response_
### Homeserver
_No response_
### Will you send logs?
No
Contributor guide
Research direction
Start with the linked GitHub Actions run and identify the workflow responsible for the SonarCloud scan and the subsequent results job. Reproduce or trace the network/server failure handling; done means a failed scan is reported as failed and the results job does not remain pending indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100