-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
run some tests with Miri #2795
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
run some tests with Miri #2795
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
I can confirm that with seanmonstar/httparse#113, running the tests with |
Does httparse 1.7.0 contain seanmonstar/httparse#113? If yes, then this PR could move forward once hyper depends on the newer httparse. :D |
Oh, nice! I was wondering, the point of running all the tests through Miri is to check for any UB in the stack? |
Yes. Specifically this would have caught the UB fixed by #2545 if it had been added a year ago. |
It looks like the Miri CI job here has been rerun a few days ago (not quite sure what triggered that), has picked up the new httparse, and has subsequently gotten a green checkmark. :) |
94e9cf9
to
f974123
Compare
Ah, bummer, with strict provenance tests start to fail:
Looks like there are int-to-ptr casts somewhere. Probably in Checking without strict provenance is still valuable though. :) |
Yea, bytes was written in the dark ages, when pointers were integers and blindfolds were typical headgear :) So, normally I wouldn't have a contributor care about the commit format, since I can clean it up in a squash. But in this case, the commits really should be separate. So, either, could you rename the commits as |
|
How separate do you want the commits to be? All 4 individually like now? I can look into the commit format thing later -- or feel free to do it if you get to it first. |
Looking at the commits documentation, I think I best leave that part to you -- figuring out the "type" and "scope" of each of these changes seems rather subjective and certainly requires more familiarity with this crate than I have. |
We have to limit the set of features we test:
--feature full
does not work since it fires up the tokio runtime, which callsepoll_create1
and that is not supported by Miri.Fixes #2794