uschindler commented on issue #15095: URL: https://github.com/apache/lucene/issues/15095#issuecomment-3204817704
> I do think it's the hanging build, yes. But it's weird that sometimes it does stop on its own (timeout on the suite) and other times it's just hanging. Yes thats strange, I often figured out that the "site timeout" doe snot work correctly. Another thing to keep in mind: If the suite timeout is very long (like it was in this case), it may happen that Jenkins kills it earlier. This is causing the different behaviour. And the timeout of Jenkins is "dynamic" (that proofed to be useful). Instead of having absolute timeouts (which depend on hardware), Jenkins is configured to have a dyanmic timeout: It measures the time a build takes and if it suddenly takes much longer (I think the limit starts about 2 or 3 times as long as average build) it kills it: <img width="2138" height="919" alt="Image" src="https://github.com/user-attachments/assets/1b0b49ce-381b-470d-befd-3e43b16ccd7a"; /> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
