debug_output.txt
thread_dump.txt
[GRADLE-1156] gradle "Could not stop connection" after a particular failed unit test Created: 22/Sep/10 Updated: 04/Jan/13 Resolved: 20/Jan/11 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 0.9 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Michael Plump | Assignee: | Unassigned |
| Resolution: | Not A Bug | Votes: | 0 |
| Attachments: |
debug_output.txt
thread_dump.txt
|
| Description |
|
We have some tests that run fine when they're passing, but when they fail, gradle hangs. The debug output shows the test exiting. The thread dump does show we have one thread still running (a connection to a Rabbit MQ server), but I don't think that's the problem because that should be left running even with the test succeeds. Eventually, it will throw an exception and exit. The debug output and thread dump are attached. |
| Comments |
| Comment by Michael Plump [ 20/Jan/11 ] |
|
It is with much shame and embarrassment that I close this bug. It turns out that, deep within some legacy code of ours, there was a call to System.exit (!!). Yikes. So that was shutting down the test runner early. Oops! |