You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
File "/home/runner/work/operator/operator/test/test_real_pebble.py", line 132, in test_checks_and_health
assert bad_check.failures == 2
AssertionError: assert 3 == 2
+ where 3 = CheckInfo(name='bad', level=CheckLevel.READY, status=CheckStatus.DOWN, failures=3, threshold=2, change_id=ChangeID('12')).failures
=========================== short test summary info ============================
FAILED test/test_real_pebble.py::TestRealPebble::test_checks_and_health - AssertionError: assert 3 == 2
I assume it's because test_checks_and_health has some code in it that's too timing-sensitive. Not sure why it just started happening recently. It's happened a couple of times today, but I don't remember seeing it before that.
The text was updated successfully, but these errors were encountered:
Example failed run here.
The failure is:
I assume it's because
test_checks_and_health
has some code in it that's too timing-sensitive. Not sure why it just started happening recently. It's happened a couple of times today, but I don't remember seeing it before that.The text was updated successfully, but these errors were encountered: