You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All sub jobs running in this pull request has same configuration. but only "Testing Farm - edge-9to9-9.4" and "Testing Farm - edge-8to9-9.4" has this strange timeout issue. Which means there might be something in the test scripts that caused this issue but not the configuration. The test script for these two sub jobs are https://github.com/yih-redhat/tmt-demo/blob/main/ostree-9-to-9.sh and https://github.com/yih-redhat/tmt-demo/blob/main/ostree-8-to-9.sh, but I cannot see anything special in these scripts, they are just normal shell scripts, like other test scripts in my repo.
Reproducer
No response
The text was updated successfully, but these errors were encountered:
If you look into the log, you can see the test script was actually passed and exit with 0, but it looks like some child process blocked the job to complete until timeout.
I have tried to set the timeout to a very long time, and still got this issue. And with the same timeout value, other sub jobs which take much longer than this script can pass.
@jamacku Could you please take a look of this bug?
Because of this bug, I cannot get green in our CI job, and need to check it manually to see it passed or not.
This bug only happens on these two sub jobs, no matter how long I set the timeout, it will always exit 0 and then timeout.
Type of issue
None
Description
This bug is as same as #166, as it was closed and I cannot reopen it, so created a new bug to track this.
Descripion:
Reproducer
No response
The text was updated successfully, but these errors were encountered: