2

We have a TeamCity build that runs end to end tests, and every once in a while, for an unclear reason, it gets stuck. So I set a timeout after a certain amount of time and I want it to automatically run again after the timeout occurs.

I know there's a 'Retry Build Trigger' but I want it to retry only on timeout and not on every failure.

Any suggestions?

Extra information that might help:

  • The result appears as 'Execution timeout (new)'
  • When a timeout occurs the build log writes 'The build %Build-Name% {builId=63608} has been running for more than 100 minutes. Terminating...'
nirsky
  • 2,955
  • 3
  • 22
  • 35
  • 1
    what is the build doing that causes it to hang? you can look at the Build Log to see what it last did/is doing. it may be indicating a real issue – wal Nov 17 '14 at 14:27
  • It's under investigation, in the meanwhile we are looking for a workaround, the build log is not really informative: `[03:07:43]*Some print to console* [05:30:27]The build %Build-Name% {builId=63608} has been running for more than 100 minutes. Terminating...` – nirsky Nov 17 '14 at 14:34
  • 1
    attach your debugger to the test runner. – wal Nov 17 '14 at 14:38
  • Can you please elaborate? – nirsky Nov 17 '14 at 14:42
  • 1
    what is TC running when it hangs? not just `end to end tests` <-- what *sort* of tests, who is running the tests (which application or test runner) – wal Nov 17 '14 at 15:05
  • We're using TestNG to run E2E tests on android devices using Appium (written in Java). – nirsky Nov 17 '14 at 15:21
  • ok. suggest using eclipse to attach to the running process or get the callstack/threads of the test runner to see whats going on. eg http://stackoverflow.com/questions/14705451/how-to-get-java-call-stack-of-a-running-application – wal Nov 17 '14 at 22:56

0 Answers0