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
I propose to continue running tests when build completes but previous unit tests fail. You can see from this log that GitHub Actions workflow stops once there is an error. However, for a workflow which completes building, stopping at one possible failed unit test is too inefficient.
An implementation to this feature can be as follows:
Sure, completely agree. In this case we will know about all failed tests, and avoid the situation when a test failed and you fix it, but another test failed in a new pipeline.
I propose to continue running tests when build completes but previous unit tests fail. You can see from this log that GitHub Actions workflow stops once there is an error. However, for a workflow which completes building, stopping at one possible failed unit test is too inefficient.
An implementation to this feature can be as follows:
This should work and show "failed" in overall page if one test fails.
What do you think? @alalek @asenyaev @asmorkalov
Reference:
The text was updated successfully, but these errors were encountered: