Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
CI fails due to an intermitent test
See original GitHub issuetests/products/test_file.py::test_task_with_client_and_metaproduct_isnt_outdated_rtrns_waiting_download[_delete_metadata]
https://github.com/ploomber/ploomber/runs/6765722111?check_suite_focus=true
Issue Analytics
- State:
- Created a year ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
How to Fix Flaky Tests - Semaphore CI
Randomly failing tests are the hardest to debug. Here's a framework you can use to fix them and keep your test suite healthy....
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 >How to fix intermittent test failures | Sergey Potapov (greyblake)
It's not obvious, but sometime a test may fail on CI just because it runs in a specific time in a specific (different...
Read more >Debugging Failing Tests and Test Pipelines - GitLab
Failure due to bug: If a test failure is a result of a bug, link the failure to the bug issue. It should...
Read more >Debugging Intermittent Test Failures - Firefox Source Docs
Intermittents are test failures which happen intermittently, in a seemingly random way. Often you'll write a test that passes fine locally on your...
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 Free
Top 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
We’ve encountered another similar issue (note that this links to a fork and the code hasn’t been merged)
What the two examples have in common is that they are both testing the File client logic. When a File client is configured in a pipeline, ploomber will automatically upload all products to remote storage. We support AWS and Google Cloud as backends; however, we also implemented a client with a local backend. The one with the local backend is giving trouble, and I believe is because of the race conditions when accessing the filesystem.
cc @idomic
Ok, if you feel like there’s no simple solution, let us know. we might need to find a workaround