-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ci] increase timeout on R Hub Solaris job to 4 hours #5071
Conversation
Looks like it won't help. Actually, I think the whole job fails because the second Solaris job isn't starting. LightGBM/.ci/run_rhub_solaris_checks.R Lines 31 to 36 in f834cab
|
/gha run r-solaris Workflow Solaris CRAN check has been triggered! 🚀 solaris-x86-patched: https://builder.r-hub.io/status/lightgbm_3.3.2.99.tar.gz-c4b69b0803c145309dc6ccb5cb9bf16a |
oh sad! Ok yes, looks like you're right. I'll investigate as soon as possible. I did check and can confirm both of those environments are still active, according to
This job you just triggered won't read the new timeout value, right? I thought that the triggering-comments jobs had to read their configuration only from |
Yep! Just wanted to check again. Maybe there were temporary problems on the R-Hub side. |
This time CI job (both Solaris R-Hub jobs) passed in less than 1h... |
oh wow, interesting! Ok, maybe it was just an infrastructure issue with R Hub then! We can close this PR and try again on #4827. Thanks for investigating. |
This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this. |
Proposes increasing the timeout on the R-package CI job testing on Solaris via R Hub, from 2 hours to 4 hours.
I recently observed a run that took 3h32m, which led to the GitHub Actions job being marked failed, blocking merging of a PR.
#4827 (comment)