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.
Flaky tests for CancelCertificateOperation
See original GitHub issueOnly visible in the net - keyvault - tests-weekly pipeline, the VerifyCancelCertificateOperation and VerifyUnexpectedCancelCertificateOperation are randomly failing with:
Error Message:
Expected: <System.OperationCanceledException>
But was: null
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
How to Fix Flaky Tests - Semaphore CI
A test that intermittently fails for no apparent reason — or works in your local machine and fails with continuous integration — is...
Read more >A Detailed Guide on Flaky Tests: Causes, Detection, and ...
Flaky tests refer to tests that produce inconsistent results, passing or failing unpredictably, without any changes to the code under test.
Read more >What is a Flaky Test? Causes, Identification & Remediation
A flaky test is a software test that yields both passing and failing results despite zero changes to the code or test.
Read more >Flaky tests | GitLab
It's a test that sometimes fails, but if you retry it enough times, it passes, eventually. What are the potential cause for a...
Read more >What is a flaky test? Definition from WhatIs.com.
When the test fails to produce a consistent result, the test is deemed flaky. Flaky tests can be caused by various factors: an...
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
Yes, it happens from time to time but has been lower priority vs. features that needed to get out in preview first. I plan to address it in the April milestone.
To note, when I added more logging for the status and any error message, in the rare case the expected exception is not thrown, the status is “inProgress”. Yet, I can find no way to exit the wait loop in that case, so I’m adding more logging for
UpdateStatusandUpdateStatusAsyncvia EventSource.