Skip to content

Conversation

dulinriley
Copy link
Contributor

Summary:
We should have Rust tests run in Github CI to ensure we don't break them.
Before we were blocked on issues with cargo test running tests in threads, and we
need process isolation because our tests modify things like environment variables.

Use cargo nextest which is a package that runs test in parallel processes instead of
threads.

Differential Revision: D83856634

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Meta Open Source bot. label Oct 3, 2025
Copy link

meta-codesync bot commented Oct 3, 2025

@dulinriley has exported this pull request. If you are a Meta employee, you can view the originating Diff in D83856634.

Summary:
Pull Request resolved: meta-pytorch#1417

We should have Rust tests run in Github CI to ensure we don't break them.
Before we were blocked on issues with `cargo test` running tests in threads, and we
need process isolation because our tests modify things like environment variables.

Use `cargo nextest` which is a package that runs test in parallel processes instead of
threads.

For now, just run these in a GPU environment. A cpu-only run may be beneficial for either
cost savings, faster iteration cycles, or for test coverage itself. But I'll add that later.

Some tests are failing in Github but not internally. Add a feature to skip these called "fb".

Reviewed By: mariusae

Differential Revision: D83856634
@facebook-github-bot
Copy link
Contributor

This pull request has been merged in 6b6136c.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Meta Open Source bot. fb-exported Merged meta-exported
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants