-
I have a theory that the reason why we see some test flakiness is because we are running tests in parallel on already starved GitHub actions VMs. This issue is about testing that theory and removing f…
-
## Failure
saw this fail off of branch/v10
### CI Logs
- https://console.cloud.google.com/cloud-build/builds/8cd306c3-13b3-454f-bbb3-f3ccf70f797b?project=ci-account
- https://console.cloud.googl…
-
## Failure
#### Link(s) to logs
- https://github.com/gravitational/teleport/actions/runs/6352583155/job/17255687709#step:6:1179
#### Relevant snippet
```
client_test.go:465:
…
-
Despite some previous attempts (see #2836), there's still some instability in CI, such as #2886.
We need to come up with good lasting solution to avoid these write conflicts in build and test.
-
This started happening to our Github builds this weekend:
We never had any issues whatsoever, so initially w…
-
The post-submit test builder `Mac build_android_host_app_with_module_aar` had a flaky ratio 2.00% for the past (up to) 100 commits, which is above our 2.00% threshold.
One recent flaky example for …
-
The post-submit test builder `Mac_x64 build_tests_1_4` had a flaky ratio 2.08% for the past (up to) 100 commits, which is above our 2.00% threshold.
One recent flaky example for a same commit: http…
-
The post-submit test builder `Mac framework_tests_impeller` had a flaky ratio 2.08% for the past (up to) 100 commits, which is above our 2.00% threshold.
One recent flaky example for a same commit:…
-
One example of CI flakiness is here: https://github.com/runtimeverification/pyk/actions/runs/8330698269/job/22796012460?pr=991. It happens when a RPC server cannot be started:
 100 commits, which is above our 2.00% threshold.
One recent flaky example…