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 Oct 12, 2022. It is now read-only.
Hi, i found 2 issues around this same problem, and the other 2 seem to be slightly different.
In my build, I have continue on error checked for my run tests step, yet it doesnt continue. It just continuously runs that same step over and over, never moving on to my publish test results step. Anyone else come across this issue before?
The text was updated successfully, but these errors were encountered:
kanoutaisuke
changed the title
Step with "Always Run" does not run if previous step fails
Step with "Continue on Error" does not end if step fails
Jun 2, 2016
Let me rephrase this a little, It runs the step over and over until it hits the 1 hour timeout and then fails the entire build. I can remote in and see it running the tests, but it hangs up on most and fails them all. It consistently says 0 passed in the log, even though I viewed 1 that passed for sure. On top of that, even if it hits the 1 hour limit currently set, should the publish results step still go off since it's set to always run?
Also, running the current version of agents and controller available on the remote machine.
I understand this one is deprecated, accidentally posted this in this one as this was where I saw the similar questions. I'm not using the deprecated agent to begin with.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, i found 2 issues around this same problem, and the other 2 seem to be slightly different.
In my build, I have continue on error checked for my run tests step, yet it doesnt continue. It just continuously runs that same step over and over, never moving on to my publish test results step. Anyone else come across this issue before?
The text was updated successfully, but these errors were encountered: