-
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
[ci] Azure Linux jobs not running #5387
Comments
The issue has been resolved. Now the Linux agent for CI tests on Azure DevOps is available. I'm going to close this. Thanks! |
@shiyu1994 thanks for the help! But let's please not close this until we actually see a successful build on Azure DevOps. When I look at https://dev.azure.com/lightgbm-ci/lightgbm-ci/_build?definitionId=1&_a=summary, all builds since July 15 have failed. I've just pushed a commit to #5388 (which fixes the other issue blocking the project's CI). If that has a successful Azure build, I'll come back and close this. |
I just observed a full, successful run of Azure CI jobs, so I think this can be closed. https://dev.azure.com/lightgbm-ci/lightgbm-ci/_build/results?buildId=13155&view=results thanks for the help @shiyu1994 If you have time today, please do look at #5388 , which fixes the other issues currently blocking all CI. |
This issue has been automatically locked since there has not been any recent activity since it was closed. |
Description
Since around July 17, this project's CI has been broken.
Specifically,
Linux
andLinux_Latest
jobs running in Azure DevOps have been stuck in "queued" indefinintely.Reproducible example
This was first observed in #5362 (comment), but affects all pull requests and commits to
master
.Environment info
These jobs run on a dedicated Azure node pool that Microsoft pays for.
Azure DevOps is refusing to schedule CI jobs onto the nodes in that pool because the pool's authentication information has expired (#5362 (comment)).
Only Microsoft-employed maintainers have administrative access to this node pool, and those maintainers apparently do not have access to update the pool's security settings (#5362 (comment)) .
Additional Comments
This project's CI will continue to be blocked until @shiyu1994 gets assistance from whoever inside Microsoft has the power to update that node pool.
Opening this issue since it's now been more than a week that we've been facing this problem, and so that comments in pull request reviews and other issues can link to this instead of needing to link to the first PR where we happened to notice the problem (#5362).
The text was updated successfully, but these errors were encountered: