-
Notifications
You must be signed in to change notification settings - Fork 52
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
Adds smoke test workflow and tests #424
base: main
Are you sure you want to change the base?
Conversation
Test groups are divided into three categories: 1) unit tests 2) smoke tests 3) benchmark tests They each have a dedicated tox entrypoint. Adds outer product of [FSDP, DeepSpeed] x [CPU offload, Not] test matrix. DEEPSPEED TESTS ARE BROKEN IN THIS COMMIT and are marked xFail- to be fixed in another, later commit. Signed-off-by: James Kunstle <[email protected]>
This PR removes the reusable workflow contributions in #419 but keeps the smoke testing. |
ced2123
to
f832e78
Compare
users can dispatch a workflow that runs smoke tests against a selected branch Signed-off-by: James Kunstle <[email protected]>
f832e78
to
782e425
Compare
This PR needs to go in so that we can test the manual functionality of the smoke-test addition. It works on a dev machine. |
|
||
|
||
@pytest.fixture(scope="module") | ||
def custom_tmp_path(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Apologies for the drive-by comment. The rest of this PR is over my head 😆 . I was just reading this PR and noticed something related to this fixture.)
The implementation of this method looks similar to pytest's own tmp_path
fixture. I wondered if you could call custom_tmp_path(tmp_path)
and simply return tmp_path
here, or even use tmp_path_factory
if you want a session-scoped fixture.
adds a smoke-test.yaml workflow that's very similar to unit-test.yaml but calls a different tox+pytest path and requires a cuda runner.