#93: syncStatic build failed and goes stuck ---------------------+------------------------ Reporter: shaiton | Owner: webmaster Type: defect | Status: new Priority: major | Milestone: Component: General | Version: Keywords: infra | Blocked By: Blocking: | ---------------------+------------------------ This need to be checked, but when the build fails because of transifex client timeout or whatever (make: *** [pullpos] Error 1), it goes stuck.
For exemple we have: apache 32594 32589 0 04:59 ? 00:00:00 /bin/bash /usr/local/bin /lock-wrapper syncStatic /usr/local/bin/syncStatic apache 32608 32594 0 04:59 ? 00:00:00 /bin/bash /usr/local/bin/syncStatic apache 32645 32608 0 05:00 ? 00:00:00 /bin/bash /usr/local/bin/syncStatic
Process 32594 attached - interrupt to quit waitpid(-1, q <unfinished ...>
Process 32608 attached - interrupt to quit read(3, <unfinished ...>
Process 32645 attached - interrupt to quit waitpid(-1, <unfinished ...>
Somewhere, we fail to catch this issue and stop the build.
#93: syncStatic build failed and goes stuck ----------------------+----------------------- Reporter: shaiton | Owner: webmaster Type: defect | Status: new Priority: major | Milestone: Component: General | Version: Resolution: | Keywords: infra Blocked By: | Blocking: ----------------------+-----------------------
Comment (by shaiton):
Ok, it appears when the `tx pull` command is running, and the network goes down. The transifex client just wait until the network goes back, and there is no timeout. The transifex client just continue then… But not in our server (or sometimes it fails, dunno).
We should see with the indifex team if they want to add a timeout switch. Asked upstream: https://github.com/transifex/transifex/issues/15
#93: syncStatic build failed and goes stuck ----------------------+----------------------- Reporter: shaiton | Owner: webmaster Type: defect | Status: closed Priority: major | Milestone: Component: General | Version: Resolution: fixed | Keywords: infra Blocked By: 136 | Blocking: ----------------------+----------------------- Changes (by shaiton):
* resolution: => fixed * blockedby: => 136 * status: new => closed
Comment:
This is linked to #136 which should be resolved soon (matter of minutes, really).
websites@lists.fedoraproject.org