./miri run: directly run binary instead of using 'cargo run' #3881
Conversation
|
@bors r+ |
./miri run: directly run binary instead of using 'cargo run' This avoids re-building miri without dev dependencies, so it makes `./miri run` a lot faster if `./miri test` was already executed before.
|
💔 Test failed - checks-actions |
|
@bors r+ |
./miri run: directly run binary instead of using 'cargo run' This avoids re-building miri without dev dependencies, so it makes `./miri run` a lot faster if `./miri test` was already executed before.
|
💔 Test failed - checks-actions |
|
Hm, it works everywhere except on Windows... but the file path seems right. The error code translates to Cc @ChrisDenton any idea what could help here? :) |
|
Maybe using |
./miri run: directly run binary instead of using 'cargo run' This avoids re-building miri without dev dependencies, so it makes `./miri run` a lot faster if `./miri test` was already executed before.
|
💔 Test failed - checks-actions |
|
Nope, unfortunately this does not help. :( |
|
The only other idea I have is to keep using |
|
A DLL's directory has to be in (Well there are also other options but they're more complicated) |
|
So probably we have to add |
|
Let's see... |
|
☀️ Test successful - checks-actions |
This avoids re-building miri without dev dependencies, so it makes
./miri runa lot faster if./miri testwas already executed before.