-
Notifications
You must be signed in to change notification settings - Fork 380
Install Miri #1631
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
Install Miri #1631
Conversation
1f7def9 to
8e3ee2b
Compare
|
The miri build failed: |
|
@narpfel let me know if I can help with this: I don't really know what's going on there and the error seems to be in |
Building the Miri sysroot needs the standard library sources, which it tries to install, but this doesn’t work because CE’s If you’d prefer that |
|
This will need to be installed in the docker container. The error is in the docker - the docker image doesn't see anything other than the things we place in it. Maybe I'm misunderstanding this: do you mean for the infra package to install something ecxtra just so it appears in the docker container here? |
|
Yes, the build script in the docker container uses the |
|
Now I get it: I think we should only install it in the docker container if that's OK: it already takes hours to install rust things on our slow network drive, adding a ton more on the nightly install (unless it's needed at runtime anyway) just to have it available in the docker seems unfortunate. |
That’s also okay, as far as I know the sources are only needed during build time. It’s not a lot of space, just a lot of small files, so I imagine installing them on a network drive would be rather slow. |
|
Perfect: thanks @narpfel |
|
PR here: compiler-explorer/misc-builder#113 |
|
Merged; and building: https://github.com/compiler-explorer/compiler-workflows/actions/runs/15289645148 |
|
Still failing: https://github.com/compiler-explorer/compiler-workflows/actions/runs/15289645148 can you please run and confirm the docker image runs locally if possible? It will save a lot of long round-trips and is partly why we use docker; it should be fairly straightforward (if computiationally expensive I know) to test locally. |
|
The log file is large- here's the important part: |
I was trying to avoid that (I tested with just a few common (tier 1) targets), but in the end it wasn’t that bad. Builds successfully now. The “fix” was to not abort the whole build if one target fails to build. |
|
thanks @narpfel ! sorry this is so painful |
|
Success!! |
|
Now to work out why it's not finding the built stuff... |
|
Thanks! I wasn’t sure if it’s |
well, that didn't work unfortunatlely. I'll fix. the name of the container needs to match the exported name :) It'll be a quick fix |
|
Sorry this is taking so long, a number of subtle issues I didn't spot ... I'll get this in the next day or two for sure though |
|
Finally installed! |
Resolves #2563. `misc-builder` PR: compiler-explorer/misc-builder#112 `compiler-workflows` PR: compiler-explorer/compiler-workflows#36 `infra` PR: compiler-explorer/infra#1631 Screenshot: 
|
Thanks! |

misc-builderPR: compiler-explorer/misc-builder#112CE issue: compiler-explorer/compiler-explorer#2563