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 }}
This repository has been archived by the owner on Jun 15, 2024. It is now read-only.
If we retrigger some-flaky-step, in-parallel is retriggered as well, and it's state changes if some-flaky-steps state changes. But it also contains a retrigger-marker and it keeps the original first-updated-at timestamp as if it didn't run at all. This is inconsistent and leads to bugs in code processing those timestamps, e.g. flosell/lambdacd-cctray#3
The text was updated successfully, but these errors were encountered:
Consider this pipeline:
(in-parallel some-step some-flaky-step)
If we retrigger
some-flaky-step
,in-parallel
is retriggered as well, and it's state changes ifsome-flaky-step
s state changes. But it also contains a retrigger-marker and it keeps the originalfirst-updated-at
timestamp as if it didn't run at all. This is inconsistent and leads to bugs in code processing those timestamps, e.g. flosell/lambdacd-cctray#3The text was updated successfully, but these errors were encountered: