-
Notifications
You must be signed in to change notification settings - Fork 156
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
Panic in the buddy_allocator #653
Comments
How can I reproduce the panic? |
You can find the full CI run here https://github.com/n0-computer/iroh/actions/runs/5738430197/job/15552011144?pr=1315 The command being executed is
on this branch: https://github.com/n0-computer/iroh/tree/sync-db. I am still working on reproducing it locally myself. |
On that branch, it reproduces locally with the above command, minimizing the execution to the relevant test
I got this, but unfortunately as you can see the backtrace is unusable |
@dignifiedquire surprisingly it looks like this is a compiler bug, or maybe an issue with the |
Looks like this does change the panic:
|
Some additional debugging with printing out the size of the created vec and its content when it fails. It looks like it works most of the time, until it doesn't..
|
It seems more related to |
Reproduced the issue on
But it gets more interesting, if I replace the init code in pub fn new_empty(len: u32, capacity: u32) -> Self {
let cap = Self::required_words(capacity);
// let data = vec![0; cap];
let data: Vec<u64> = (0..cap).map(|_| 0).collect();
assert!(data.iter().all(|x| *x == 0), "{}: {:?}", cap, &data[..1]);
Self { len, data }
} I get the following failures only
|
Going to close this since it doesn't seem to be a redb bug. I'd report it to either rustc or cross, depending on which you think is broken |
Hey, currently working on integrating of redb into our code, and got this error on CI.
The environment is
cross
with targetaarch64-linux-android
.The text was updated successfully, but these errors were encountered: