Skip to content
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.

Sign up for GitHub

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

Jump to bottom

CI failure due to SIGSEGV #514

Closed
jeehoonkang opened this issue May 23, 2020 · 2 comments
Closed

CI failure due to SIGSEGV #514

jeehoonkang opened this issue May 23, 2020 · 2 comments

Comments

@jeehoonkang
Copy link
Contributor

https://github.com/crossbeam-rs/crossbeam/runs/702734820#step:5:103
https://github.com/crossbeam-rs/crossbeam/runs/702730520#step:5:107

It seems to lurk up from time to time. I guess it's maybe due to a recently merged PR? (I'm suspicious of #416, but not 100% sure about this.)
@jeehoonkang jeehoonkang mentioned this issue May 23, 2020
Merged
@jeehoonkang
Copy link
Contributor Author

https://github.com/crossbeam-rs/crossbeam/runs/702745639 another failure w/ address sanitizer

@ghost
Copy link

ghost commented May 23, 2020

It could be - can you check if the issue is present of we revert #416?

@jeehoonkang jeehoonkang mentioned this issue May 24, 2020
Merged
bors bot added a commit that referenced this issue May 25, 2020
@bors @jeehoonkang
Merge #517
5c74eb1 
517: Revert "Require three epoch advancements for deallocation " r=jeehoonkang a=jeehoonkang

Reverts #416

I'm suspecting may this PR causes #514.  Here's a revert PR, and I'd like to test if SIGSEGV is gone after reverting the PR...

Co-authored-by: Jeehoon Kang <jeehoon.kang@kaist.ac.kr>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeehoonkang