-
Notifications
You must be signed in to change notification settings - Fork 120
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
Make file locations appear in zebrad error messages #4956
Comments
This makes diagnosing errors in the docker tests tricky, but it can wait until next sprint. |
This important, but it's not causing any particular issues right now. |
@gustavovalverde does it make sense to look at this issue opportunistically since we're making other changes to the Dockerfile? Especifically this part:
|
@gustavovalverde @mpguerra I just re-checked this on my local machine, and it happens in all release builds, even outside Docker. So I don't think we can fix it by changing the Docker config. |
I had a look at this, we can fix this issue using the But the debug info adds 300 MB to the Since this hasn't been a blocker for diagnosing any bugs, I made it into a branch which developers can use if we need it: |
Motivation
When Zebra's Rust test harness fails in CI, I can't see the file and line in the panic backtrace:
https://github.com/ZcashFoundation/zebra/runs/7992118921?check_suite_focus=true#step:6:246
This happens in both Docker, and in release builds on my local machine.
But debug builds on my local machine show the file locations:
Tasks
Try adding debugging info to the Rust release profile:
zebra/Cargo.toml
Line 67 in 5866fc3
The text was updated successfully, but these errors were encountered: