| nephros | Is there a strategy what do do when OBS kills a job "Job seems to be stuck here, killed."? I have a build process where nothing *seems* to happen for a while wrt stdout/stderr, but it actually does something. | 06:34 |
|---|---|---|
| nephros | I don't think I can increase the timeout as a user, can I? | 06:34 |
| mal | nephros: can you point me to the build? | 11:58 |
| nephros | mal: See https://build.sailfishos.org/package/show/home:nephros:devel:lang/maxima | 13:31 |
| nephros | So you can see in the successful log, there is a point where the runtime jumps from less than 100 to over 1800 or so | 13:32 |
| nephros | Now, this isn't that non-x86 *always* hangs and is killed, sometimes it succeeds. | 13:33 |
| nephros | When e.g. aarch64 succeeds, you can see at about 66s, the next line that appears is much later, 1800 or more seconds of runtime. | 13:34 |
| mal | I'll do some test builds a bit later today to see what is happening | 13:36 |
| nephros | cool, thx! | 13:56 |
| mal | nephros: it seems making it build using only one thread fixed it | 20:13 |
| mal | I suspect that could be related to the threading issues in old make, there will be new make in next sfos release | 20:13 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!