Closed Dylan-DPC-zz closed 4 years ago
Hey, thanks for the bug report. I wonder if this issue isn't related to a symlink handling bug discovered in https://github.com/darakian/ddh/issues/23 Is it possible to rerun the crater test with a feature branch?
I don't think that would be possible.
Dang that's unfortunate. I'm not sure what I can do to fix this without a test case :(
Closing this issue do not having possible solution merged and no replicable test case.
@darakian I think this is a bug in crossbeam-epoch; the crate seems to depend on v0.7.1. v0.7.2 fixes a critical bug.
I am wondering why that version was not picked automatically? crossbeam-epoch is a transitive dependency it seems.
(Btw, the relevant rustc change here is https://github.com/rust-lang/rust/pull/71274.)
The dependency seems to be via rayon. But that doesn't explain why it did not use v0.7.2.
Crater has been testing ddh-0.10.9; unfortunately there seem to be no tags in this repository so I cannot easily look at the code as it was back then.
@RalfJung Thanks for the follow up and sorry about the lack of tags. The dependencies at the time of 0.10.9
were
[dependencies]
clap = "2.33.0"
rayon = "1.1"
serde = "1.0"
serde_json = "1.0"
serde_derive = "1.0"
siphasher = "0.3"
nohash-hasher = "0.1.1"
Is it just 0.10.9
that shows this problem? If so that's certainly odd as 0.11.0
was only a license change release and is identical code.
Here's a link to the repo on 0.10.9
commit if it helps
https://github.com/darakian/ddh/tree/1d4f4922ba24a49c31d3359e584df9903c22b87c
0.10.9 was the latest version at the time the test was run, so I cannot say if newer versions still show this problem.
In your local lockfile, which version of crossbeam-epoch does it use? cargo tree
can help figure that out.
Looks like 0.8.2
jon~/G/!/ddh:(HEAD detached at 1d4f492)❯❯❯ cargo tree | rg crossbeam
│ ├── crossbeam-deque v0.7.3
│ │ ├── crossbeam-epoch v0.8.2
│ │ │ ├── crossbeam-utils v0.7.2
│ │ ├── crossbeam-utils v0.7.2 (*)
│ ├── crossbeam-deque v0.7.3 (*)
│ ├── crossbeam-queue v0.2.3
│ │ ├── crossbeam-utils v0.7.2 (*)
│ ├── crossbeam-utils v0.7.2 (*)
Okay. I think we can consider this issue resolved then, and the next time around crater should pick up the latest version of crossbeam-epoch I hope.
🤞
Thanks again for reaching out :)
I got a panic from a crater run which included this crate (in case you are not aware, crater is a tool that runs rustc against a set number of locked crates to check for regressions). It was with 0.10.9 version so i'm not sure if it still holds true in the 0.11.0 or not. Also, it could be caused by one of the dependencies. I tried tracking it down but I couldn't find anything.
The main point of the crater run was to find UB according to this advisory: https://github.com/RustSec/advisory-db/issues/298.
Edit: there is a small possibility that this could be due to the file permissions being denied in crater runs
The crater output is: