Task #11511 (new)
Opened 11 years ago
Last modified 9 years ago
On develop, blitz unit tests hang
| Reported by: | mtbcarroll | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | Rendering |
| Component: | Services | Version: | n.a. |
| Keywords: | n.a. | Cc: | java@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
For me ./build.py -f components/blitz/build.xml test isn't terminating after many minutes' wait.
Attachments (1)
Change History (13)
Changed 11 years ago by mtbcarroll
comment:1 Changed 11 years ago by mtbcarroll
Output ceases after a long pre-instantiating singletons line.
comment:2 Changed 11 years ago by mtbcarroll
- Milestone changed from 5.0.0-beta1 to 5.0.0-beta2
comment:3 Changed 11 years ago by jamoore
- Cc java@… added; omero-team@… removed
- Milestone changed from 5.0.0-beta2 to 5.0.0-beta3
- Owner jamoore deleted
I don't see myself as having the time for the investigation needed for this. Pushing and unassigning from me. If wants to make progress during Q4, feel free to move it back to beta2.
comment:4 Changed 10 years ago by jamoore
- Milestone changed from 5.1.0 to 5.1.1
comment:5 Changed 9 years ago by jamoore
- Milestone changed from 5.1.1 to 5.1.2
- Priority changed from blocker to critical
Can't see getting to this for 5.1.1. Pushing (and lowering priority since it's more an internal issue)
comment:6 Changed 9 years ago by jburel
- Milestone changed from 5.1.2 to 5.1.3
"Testing" cards have been moved out of 5.1.2
Probably a summer card.
comment:7 Changed 9 years ago by sbesson
Is this the same issue as the one which led to https://github.com/joshmoore/openmicroscopy/commit/c50cf49e1c7763fff405110ed3ebfdfcc8a08249?
comment:8 Changed 9 years ago by jamoore
I wouldn't think so. The attached stack trace looks more like an OOM where the JVM is completely unhappy, whereas the travis issue was just a single call in the networking stack.
comment:9 Changed 9 years ago by jamoore
- Milestone changed from 5.1.4 to OMERO-5.1.4
Splitting 5.1.4 due to milestone decoupling
comment:10 Changed 9 years ago by sbesson
- Milestone changed from OMERO-5.1.4 to 5.x
As per discussion today, pushing to 5.x
comment:11 Changed 9 years ago by jamoore
- Milestone changed from 5.x to Unscheduled
comment:12 Changed 9 years ago by jburel
- Milestone changed from Unscheduled to Rendering
jstack for TestNG thread