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

R jobs fail on Windows without any logs #4050

Closed
StrikerRUS opened this issue Mar 5, 2021 · 8 comments
Closed

R jobs fail on Windows without any logs #4050

StrikerRUS opened this issue Mar 5, 2021 · 8 comments

Comments

@StrikerRUS
Copy link
Collaborator

StrikerRUS commented Mar 5, 2021

The most recent master build fails with the following error:

Running R CMD check
R CMD check build logs:
Get-Content: D:\a\LightGBM\LightGBM\.ci\test_r_package_windows.ps1:164
Line |
 164 |    Get-Content -Path "$INSTALL_LOG_FILE_NAME"
     |    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Cannot find path 'C:\tmp-r-cmd-check\lightgbm.Rcheck\00install.out' because it does not exist.

Error: Process completed with exit code 1.

I re-run several times, but the error is still occurs.

Quite weird because there is no any error reported during infrastructure installation 😕 .

Full logs: https://github.com/microsoft/LightGBM/runs/2039644549.

cc @jameslamb

@jameslamb
Copy link
Collaborator

😱 I'm so confused. Maybe something with how we carefully redirect output (

function Run-R-Code-Redirect-Stderr {
) is now incompatible with something in those images. Like maybe the version of powershell was upgraded or something?

I won't be able to look at this for a few hours, apologies.

@StrikerRUS
Copy link
Collaborator Author

Maybe something with how we carefully redirect output

Hmmm, very likely. I didn't thought about it!

@jameslamb
Copy link
Collaborator

It seems that a more recent build of the R jobs (9 hours ago, for #1767) passed, so maybe this was something temporary?

https://github.com/microsoft/LightGBM/actions/runs/627184704

I just restarted the builds on master (https://github.com/microsoft/LightGBM/actions/runs/624383739), let's see what happens.

@jameslamb
Copy link
Collaborator

This build just passed on master, so maybe it is something temporary? https://github.com/microsoft/LightGBM/runs/2047939220

I'll at least remove the "blocking" label from this and #4049 since it seems the problem was temporary, but we shouldn't close it yet without figuring out the root cause.

@jameslamb jameslamb removed the blocking label Mar 6, 2021
@StrikerRUS
Copy link
Collaborator Author

but we shouldn't close it yet without figuring out the root cause.

I guess it will be difficult because we have no reproducible case and after re-running failed job old logs were overwritten.

@StrikerRUS
Copy link
Collaborator Author

Just a remark: I haven't seen this error for a while. Maybe it is enough to look through Run-R-Code-Redirect-Stderr source code for possible bugs and close this issue in case of no findings for now?

@jameslamb
Copy link
Collaborator

I also have not! I think it's ok to close for now. I can't see anything problematic in Run-R-Code-Redirect-Stderr.

@github-actions
Copy link

This issue 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

No branches or pull requests

2 participants