You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Turn on cargo test for the hyperactor crate (#1417)
Summary:
Pull Request resolved: #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
fbshipit-source-id: 87c1fe1053e092fc0c4076bca5856912be3c4ea0
Copy file name to clipboardExpand all lines: hyperactor/src/host.rs
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1194,6 +1194,8 @@ mod tests {
1194
1194
}
1195
1195
1196
1196
#[tokio::test]
1197
+
// TODO: OSS: called `Result::unwrap()` on an `Err` value: ReadFailed { manifest_path: "/meta-pytorch/monarch/target/debug/deps/hyperactor-0e1fe83af739d976.resources.json", source: Os { code: 2, kind: NotFound, message: "No such file or directory" } }
0 commit comments