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
{{ message }}
Repository navigation
Islington reports status check being a success but also reports ❌ when checks fail #564
message=f"Status check is done, and it's a {result['state']}{emoji} ."
This seems rather straightforward so I'm not immediately sure what is broken here. Can there be some sort of race condition where result["state"] is "success" on L103 but has changed when we reach L112?
Oh no, I'm stupid. This is actually pretty straightforward. If result["state"] == "success" but there are timed out checks then the f-string will still use "success" even though the if success check fails.
That should be easily fixable. Working on a PR.
Activity
DanielNoord commentedon Jul 11, 2022
Oh no, I'm stupid. This is actually pretty straightforward. If
result["state"] == "success"but there are timed out checks then the f-string will still use "success" even though theif successcheck fails.That should be easily fixable. Working on a PR.
jacobtylerwalls commentedon Oct 9, 2022
Interesting. I fixed this in #501 but it was re-caused by a faulty merge in #481. Goes to show the value of tests.