Not sure if this is the right place to report it, but I saw this job failure today: https://cirrus-ci.com/task/6078479919742976
I'll try re-running but opening this issue in case others see this kind of thing too.
-
sdaftuar commented at 10:42 PM on September 3, 2020: member
- sdaftuar added the label Bug on Sep 3, 2020
-
MarcoFalke commented at 12:11 PM on September 5, 2020: member
There are multiple options:
- Do nothing and reset builds because the timeouts are intermittent.
- Move to self-hosted runners/ci and hope they run more stable and don't time out. (Downside is that this needs maintenance)
- Remove tests until no timeouts can be observed. (Will be hard to decide which tests to drop, especially considering that our current tests don't even result in adequate coverage)
- Remove tsan test completely and run it once before every release. (Downside is that failures will be fixed last minute or not at all)
- Remove tsan test and run it nightly. (Downside is that failures will be fixed after they happened, nightly builds will fail until they are fixed)
- Pay cirrus ci to have no 2h timeout. (Downside: Forked repos would time out)
- Temporarily bump the CPU and memory to buy time.
- Something else ... ?
- MarcoFalke cross-referenced this on Sep 5, 2020 from issue ci: Double tsan CPU and Memory to avoid global timeout by MarcoFalke
- MarcoFalke referenced this in commit 0368931702 on Sep 6, 2020
- MarcoFalke closed this on Sep 6, 2020
- bitcoin locked this on Feb 15, 2022
Contributors
Labels