-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
[Blocking] [ci] CI for R freeze #3280
Comments
Ok I can look in 10 minutes |
ok looking right now |
I'm going to push changes to #3277 to test, since that is a small R change that was already approved. |
😕 I tried removing https://github.com/microsoft/LightGBM/pull/3277/checks?check_run_id=956113469
Those logs tell us that:
Since there has not been an Rtools release since June 22, and since we're seeing this issue even on Rtools35, I have these theories:
I just looked on the pacman mirrors and I see a LOT of errors recently!!! and other mirrors not reporting errors are way out of sync Given this, @guolinke I think you should use your administrator privileges to merge #3071 . We don't know how long it will take for this to be resolved, and it shouldn't hold up releases for all the other non-R components any longer. |
@jameslamb thank you so much. |
I just checked and the |
I have been trying with #3277 and I still see this issue :/ This is difficult because even after removing the It seems that a lot of the |
Ok making progress!!! Now I think that the pacman thing was completely unrelated. I found that the download code we've been using to get Rtools is returning a successful status, but not actually downloading anything!!! and then if you run the code to install Rtools and the file doesn't exist, you get a dialog box that has to be confirmed in a GUI. That is why it's hanging in CI!! I'm investigating how to fix this. Maybe the download link from CRAN is now redirecting and the powershell code in |
According to your screenshots you are downloading from LightGBM/.ci/test_r_package_windows.ps1 Lines 105 to 106 in 33af069
On my local machine CI code works fine and downloads both R and Rtools sucessfully. |
😱 😱 😱 😱 😱 |
I just switched to This is tough because you cannot (as far as I know) pin to one distribution of Rtools as long as it is not "frozen" (https://cran.r-project.org/bin/windows/Rtools/history.html). So the |
I just pushed a commit to #3277 that switches from |
ok from the logs on #3277, it seems that the files ARE getting downloaded successfully. So something else is failing for Rtools 4.0 specifically :/ My guesses now are:
When I run this on my laptop Start-Process -FilePath C:\Users\James\repos\sandbox\Rtools.exe -NoNewWindow -Wait -ArgumentList "/DIR=C:\Users\James\repos\sandbox" A dialogue box pops up |
oh I forgot to add Start-Process -FilePath C:\Users\James\repos\sandbox\Rtools.exe -NoNewWindow -Wait -ArgumentList "/VERYSILENT /DIR=C:\Users\James\repos\sandbox\rtools" the process just hangs forever :/ |
Can you please try to UPD: OK, according to the screenshot |
oooo sure! I also just found that I can stop the "hangs forever" problem locally by changing the command to this: C:\Users\James\repos\sandbox\Rtools.exe /VERYSILENT /DIR=C:\users\James\repos\sandbox\rtools So maybe something about the new |
hey maybe that is working? Here is one of the R 4.0 jobs getting past Rtools (https://github.com/microsoft/LightGBM/pull/3277/checks?check_run_id=962455060) I need to step away for a few hours, but hopefully that was it and the build on #3277 will work. @StrikerRUS please feel free to push to that PR if you want, I know that this issue is blocking everything right now. I'll be back on in about 3 hours to try other things. |
this was fixed by #3277 |
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. |
refer to https://github.com/microsoft/LightGBM/runs/955837580
It seems the installation of Rtools (with R 4.0) freezes.
ping @jameslamb
The text was updated successfully, but these errors were encountered: