Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

jameslamb
Copy link
Collaborator

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)

@StrikerRUS
Copy link
Collaborator

StrikerRUS commented Mar 15, 2022

Looks like it won't help.

image

Actually, I think the whole job fails because the second Solaris job isn't starting.

platforms <- c(
"solaris-x86-patched"
, "solaris-x86-patched-ods"
)
sink(file = null_file)
for (platform in platforms) {

@StrikerRUS
Copy link
Collaborator

StrikerRUS commented Mar 16, 2022

/gha run r-solaris

Workflow Solaris CRAN check has been triggered! 🚀
https://github.com/microsoft/LightGBM/actions/runs/1992800655

solaris-x86-patched: https://builder.r-hub.io/status/lightgbm_3.3.2.99.tar.gz-c4b69b0803c145309dc6ccb5cb9bf16a
solaris-x86-patched-ods: https://builder.r-hub.io/status/lightgbm_3.3.2.99.tar.gz-2786f8edef34469a8a1277a9aafbec06
Reports also have been sent to LightGBM public e-mail: https://yopmail.com?lightgbm_rhub_checks
Status: success ✔️.

@jameslamb
Copy link
Collaborator Author

Looks like it won't help.

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 rhub::platforms().

run r-solaris

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 master (#4397 (comment), #4503).

@StrikerRUS
Copy link
Collaborator

StrikerRUS commented Mar 16, 2022

This job you just triggered won't read the new timeout value, right?

Yep! Just wanted to check again. Maybe there were temporary problems on the R-Hub side.

@StrikerRUS
Copy link
Collaborator

StrikerRUS commented Mar 16, 2022

Maybe there were temporary problems on the R-Hub side.

This time CI job (both Solaris R-Hub jobs) passed in less than 1h...

@jameslamb
Copy link
Collaborator Author

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.

@jameslamb jameslamb closed this Mar 16, 2022
@jameslamb jameslamb deleted the ci/rhub-timeout branch March 16, 2022 13:52
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants