-
-
Notifications
You must be signed in to change notification settings - Fork 269
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
The artifacts override tests fail for me locally #2806
Comments
If I clone the But if I then change the UUID back to the original UUID, and then I run @staticfloat I'm probably going to need your help to debug this. We will need to figure out how to get these tests passing without changing the UUID in the Pkg.jl project file, because I don't think we'll be able to do the "change the UUID" trick when running the tests with |
The reason the tests don't pass is that if you don't change the UUID, you load the wrong Pkg; changing the UUID dodges the "is this an stdlib that I'm loading" check. It should be fine without changing the UUID when testing in Base, because we will be running a Julia that has the correct Pkg since we just built it. |
Hmmmm. I am still seeing the following test failure on Buildkite:
The full Buildkite log is here: https://buildkite.com/julialang/julia-master/builds/5345#6729df4a-5129-4510-a957-940bc1ed473c This is a Buildkite job triggered on the following pull request: JuliaLang/julia#42885 |
Yeah, I am continuing to see this consistently on JuliaLang/julia#42885 Another example log (from https://buildkite.com/julialang/julia-master/builds/5411#a702e08a-5079-489b-8697-83ad9e989913, which has an rr trace attached):
|
As far as I can tell, this is the last remaining Pkg failure when running the Pkg tests as part of Base Julia CI. |
Steps to reproduce:
The error that I get:
The text was updated successfully, but these errors were encountered: