There's 2 problem related to this:

Once a cancellation has been detected, we print the calcellation tag, followed by the closing story tag, but since we were in a scenario, we must print thie close tag as well.
I committed it in my repo.

The second problem i more tricky...
Once we reach the timeout, the main thread calls Future.cancel(true), on another thread which is running the story.
The story running thread then throw an InterruptedException, which it catch itself to print the correct output.
But, the main thread consider the running thread as DONE at the time it calls Future.cancel().
This cause a race condition that may lead to the main thread terminating the JVM BEFORE the StoryRunner outputs its reports correctly.

Note that an invalid .xml output may cause view generation to fail, and also other plugins that rely on the xml version of the report, such as the Jenkins plugin.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to