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 Jan 23, 2023. It is now read-only.
Hi @lyndsey-ferguson, I think try_count option works incorrectly, for ex. when we write try_count option greater than 1, if we have test construction like these:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi @lyndsey-ferguson, I think try_count option works incorrectly, for ex. when we write try_count option greater than 1, if we have test construction like these:
As I see in console logs tests falls into retry batches, and multi_scan trying to retry these tests -> receiving again skip
I assume that retry option shouldn't try to rerun skipped tests because it will not be modified during 1 run and it's increasing test run overall time
Is it correct current multi_scan logic, or am I wrong? Thanks
Beta Was this translation helpful? Give feedback.
All reactions