Skip to content

ci: Add a way to run libm tests that would otherwise be skipped #998

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

Merged
merged 4 commits into from
Jul 30, 2025

Conversation

tgross35
Copy link
Contributor

@tgross35 tgross35 commented Jul 30, 2025

More details are in the commit messages.

@tgross35 tgross35 force-pushed the ci-add-libm-trigger branch 7 times, most recently from 1b218c2 to a8c452f Compare July 30, 2025 08:59
tgross35 added 4 commits July 30, 2025 08:59
Replace the current system with something that is more structured and
will also catch unknown directives.
Use `tee` rather than printing to both stdout and stderr.
Introduce a new directive `ci: test-libm` to ensure tests run.
@tgross35 tgross35 force-pushed the ci-add-libm-trigger branch from a8c452f to 1d58d4c Compare July 30, 2025 09:00
@tgross35 tgross35 merged commit 1d58d4c into rust-lang:master Jul 30, 2025
74 of 76 checks passed
@tgross35 tgross35 deleted the ci-add-libm-trigger branch July 30, 2025 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant