-
Notifications
You must be signed in to change notification settings - Fork 103
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
ci: get sanitizer results #2926
Conversation
59de261
to
b34a4fa
Compare
Codecov Report
@@ Coverage Diff @@
## ci-enable-asan #2926 +/- ##
=================================================
Coverage ? 77.70%
=================================================
Files ? 1056
Lines ? 73394
Branches ? 0
=================================================
Hits ? 57034
Misses ? 16360
Partials ? 0 📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today! |
f2d4a80
to
710c6aa
Compare
c643d00
to
f395fb2
Compare
f395fb2
to
4968b34
Compare
Ok. So, UBSan looks like it should be good to add to the block-CI set; we don't invoke any behaviour it can detect as UB. We should be able to turn on ASan and disable leak checking, but
So, current status: We should add UBsan to the list off builds required to pass in CI, and fix the bugs that asan detects. |
72a7aad
to
b263aaa
Compare
1832636
to
31238ed
Compare
31238ed
to
796e413
Compare
15d401c
to
5cd4c56
Compare
796e413
to
5d644fc
Compare
Sadly, we *know* we have benign leaks in hard-to-fix places. It would still be valuable to fail CI if ASan detects anything *else* - out of bounds writes, use-after-free, etc. Disable the leak checker so we can mark ASan failures as CI-fatal. Hopefully we can get get the leaks fixed or correctly-suppressed *some*time!
We're LD_PRELOAD'ing a bunch when running tests.
5d644fc
to
a4a7f3c
Compare
bbdd1a4
to
4a5defa
Compare
8458ca6
to
a580cc8
Compare
No description provided.