Flaky `test_aio` and `test_aio_local` CircleCI jobs
See original GitHub issueThe test_aio
and test_aio_local
CircleCI jobs started to be quite flaky recently (~50% of attempts results in false-positive failures). Example of the recent failure can be found here. It looks like the same tests produce flaky results:
Chrome Headless 83.0.4103.0 (Linux x86_64) DocViewerComponent #render() (swapping views) should unsubscribe from the previous "swap" observable when unsubscribed from FAILED
and
Chrome Headless 83.0.4103.0 (Linux x86_64) DocViewerComponent #render() (embedding components) should unsubscribe from the previous "embed" observable when unsubscribed from FAILED
CC @gkalpak
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5 (4 by maintainers)
Top Results From Across the Web
tadashi0713/flaky-tests-notify - CircleCI Developer Hub
Use flaky-tests-notify elements in your existing workflows and jobs. Opt-in to use of uncertified orbs on your organization's Security settings ...
Read more >How to reduce flaky test failures - CircleCI
Flaky tests, also known as flappers, fail to produce accurate and consistent results. These tests may be unreliable because of newly-written ...
Read more >Introducing Test Insights with flaky test detection - CircleCI
Test Insights includes a new layer of detection and analysis, specifically for flaky tests, which are tests that fail non-deterministically.
Read more >Jobs and Steps - CircleCI
A CircleCI job is a collection of steps. All of the steps in the job are executed in a single unit, either within...
Read more >Flaky Circle CI Tests - Build Environment - CircleCI Discuss
Parallelism on jobs runs all of the steps on every executor, not just the testing step. You'll either want to make your user...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Unfortunately, I haven’t been able to find the root cause (after several hours of investigating). See #37637 for some more info.
I have submitted #37673 to disable these tests for now.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.