-
Notifications
You must be signed in to change notification settings - Fork 131
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 pipeline is broken #805
Comments
Wait what? This should point to https://dev.azure.com/Raku/nqp. |
I noticed when I submitted this PR: #804 All but the windows CI are failing, and if I click through to azure on any of the test statuses at the bottom of the PR it goes to a page seemingly tied to jjmerlo |
I've seen it. I have no idea how that happened. But we should fix that. I believe I have the permissions necessary to do something about it. I am very short on time in the next few weeks, but this is really not how it should be. I'll fit it in somewhere. |
Seems to have happened sometime between March 1st and April 15th. I wonder if it was related to the master -> main rename (no idea if that happened inside that time frame). |
Just for the record: Looking at the links of the CI runs I'd say the problem is not related to the The oldest link a found was for commit ff2f194 from 2022-04-01 -- and that one already pointed at https://dev.azure.com/jjmerelo0004/: See https://github.com/Raku/nqp/runs/5795161045. |
@JJ Hi! Long time no write! I hope you're fine. I think the Azure pipeline under Raku/nqp (https://dev.azure.com/Raku/nqp/_build?definitionId=1&_a=summary) is colliding with one of yours under jjmerelo0004/jjmerelo (https://dev.azure.com/jjmerelo0004/jjmerelo/_build?definitionId=1&_a=summary). This probably happened with the master -> main switch. Can you stop the builds under jjmerelo0004/jjmerelo so the pipeline will (hopefully) switch back to use the one at Raku/nqp? |
I have now switched over the pipeline at https://dev.azure.com/Raku/nqp/_build?definitionId=1&_a=summary to point at main instead of master. Also I have switched the images over to never versions following the respective changes in rakudo/rakudo in 6d03c11 |
Thanks, @patrickbkr . To be honest, I only have a vague recollection on having set this up and would be really hard pressed to even retrieve the Azure password. Do you still need me to stop those builds? |
I think it should be possible to change the hook on the GitHub side as well. I don't have administrator permissions on Raku/nqp though. Given that this is not the first time I'd like to fix stuff in our GitHub setup, can I get admin access to Raku/nqp, rakudo/rakudo and MoarVM/MoarVM? @JJ: Given we'll be able to sort this out on the GitHub side, it should be fine. If not I'll speak up. |
See https://dev.azure.com/jjmerelo0004/jjmerelo/_build/results?buildId=653&view=logs&j=1f3a7134-3b80-549a-eaff-49041f6b71c8 It appears that:
The text was updated successfully, but these errors were encountered: