https://cirrus-ci.com/task/4642327564124160
I can't tell what happened, but re-running the job worked, so this seems like a spurious failure. Opening this issue in case others see the same.
-
sdaftuar commented at 2:18 PM on October 6, 2020: member
- sdaftuar added the label Bug on Oct 6, 2020
- fanquake added the label Tests on Oct 6, 2020
-
MarcoFalke commented at 12:52 PM on October 8, 2020: member
Not sure what is going on here. I assume it is a fault on the ci provider's side. I can try switching the virtualization to another one to see if it helps. If not, we might have to run the ci on our own hardware.
- MarcoFalke cross-referenced this on Oct 8, 2020 from issue cirrus: Use kvm to avoid spurious CI failures in the default virtualization cluster by MarcoFalke
- MarcoFalke referenced this in commit 380705ef4f on Oct 9, 2020
- MarcoFalke closed this on Oct 9, 2020
- sidhujag referenced this in commit fe9d53196f on Oct 9, 2020
- curtcurt380 cross-referenced this on Dec 17, 2020 from issue ci: Move linter task to cirrus by dhruv
- fkorotkov referenced this in commit 0611cab27d on Mar 18, 2021
- fkorotkov cross-referenced this on Mar 19, 2021 from issue [ci] Use regular containers by fkorotkov
- fkorotkov referenced this in commit 6e4206038e on Mar 19, 2021
- duckdogg123 cross-referenced this on Oct 24, 2021 from issue Pull by duckdogg123
- bitcoin locked this on Feb 15, 2022
