-
Notifications
You must be signed in to change notification settings - Fork 35
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
investigate segfaults on CI #594
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #594 +/- ##
==========================================
- Coverage 86.54% 82.26% -4.29%
==========================================
Files 12 12
Lines 2542 2458 -84
==========================================
- Hits 2200 2022 -178
- Misses 342 436 +94 ☔ View full report in Codecov by Sentry. |
Well, that certainly answers the question... 😅 |
😱 |
a84dce3
to
efb3299
Compare
d22c476
to
7beca92
Compare
8304c8c
to
6070f13
Compare
Hmm, at least nightly doesn't segfault anymore, the tests just fail... 🤔 |
How would you like to proceed with this issue? I'm of the view that for healthy development, it's acceptable to disable tests that are challenging to correct at the moment. My preference is to focus on restoring the CI as a first step. |
Yeah, unfortunately this PR showed that the issues ran deeper than just a single failing test. Wondering wether the segfaults might have to do with #591? |
Yeah, I will take a look on it later today. |
The segfaults on CI seem to point to these two tests in particular.
Let's see if disabling them fixes CI or whether that might have just
been a red herring