#21071 closed defect (fixed)
Jenkins hangs again
Reported by: | Klumbumbus | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Unit tests | Version: | |
Keywords: | Cc: | stoecker, Don-vip |
Description
Some processes running already since yesterday noon:
- Java-EarlyAccess-Integration
- JOSM-Integration
- JOSM-Plugins
Attachments (0)
Change History (10)
comment:1 by , 4 years ago
comment:3 by , 4 years ago
Replying to stoecker:
I restarted Jenkins. Let's see if that helps.
Nope :(
- Task "JOSM" running now for 3h (usual duration 45min)
- Task "JOSM-Integration" running now for 3h (usual duration 28min)
comment:4 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
It seems the first run after the restart simply took longer and it works fine all now .
comment:6 by , 4 years ago
Yep something is wrong with the plugin integration test. I still need to find out what. I cancelled the blocked jobs.
comment:9 by , 2 years ago
Jenkins is stuck yet again. It is currently stuck on the check-plugins
ant task. I don't know if that is what blocked it a few weeks ago. I also don't know if it is the plugin integration test mentioned in comment:6.
If we are getting stuck on check-plugins
frequently, we can look at wrapping it in a <parallel threadCount="1" timeout="10800000">...</parallel>
stanza. I'm waiting for the job to finish (so I can make certain the timeout is significantly longer than needed), but it did correctly kill the task when I had the time set shorter (note: timeout is in milliseconds).
There is only one build process defined in Jenkins and this one is blocked by "Java-EarlyAccess-Integration » JDK17" which runs in an endless loop executing:
Actually there are 9.5 GB(!) of log and counting.