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.

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

Run doc tests with miri in ci #7060

Merged
merged 5 commits into from
Jan 2, 2025
Merged

Run doc tests with miri in ci #7060

merged 5 commits into from
Jan 2, 2025

Conversation

tiif
Copy link
Contributor

@tiif tiif commented Jan 1, 2025

This PR ran doc test with miri in CI. Since doc test couldn't be run through cargo miri nextest run, it needs to be run separately using cargo miri test. There are 844 successful tests and 72 ignored tests in total.

Happy new year! 🎉

Tracked under #6812

@tiif
Copy link
Contributor Author

tiif commented Jan 1, 2025

Hmm… what's going on in tokio full --unstable (windows-latest)?

@Darksonn Darksonn added the A-ci Area: The continuous integration setup label Jan 1, 2025
@@ -399,6 +399,7 @@ jobs:
- name: miri
run: |
cargo miri nextest run --features full --lib --tests --no-fail-fast
cargo miri test --doc --all-features --no-fail-fast
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The miri job is starting to take a rather long time. Could you add a new job for this, instead of adding additional work to the existing job? This will allow for parallelism.

Copy link
Contributor

@Darksonn Darksonn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.

@Darksonn Darksonn enabled auto-merge (squash) January 2, 2025 13:06
@Darksonn Darksonn merged commit 2052938 into tokio-rs:master Jan 2, 2025
83 checks passed
@@ -1535,6 +1553,7 @@ impl UnixDatagram {
///
/// # Examples
/// ```
/// # if cfg!(miri) { return } // No `socketpair` in miri.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, but we do have socketpair in Miri?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops should be only the SOCK_DGRAM flag

fixed in #7063

@@ -421,6 +421,7 @@ impl Runtime {
/// # Examples
///
/// ```
/// # if cfg!(miri) { return } // Miri reports error when main thread terminated without waiting all remaining threads.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Specifically we report a leak; this can be ignored -- but maybe you want to detect memory leaks in the other tests.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We definitely want the leak detection for lots of other tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-ci Area: The continuous integration setup
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants