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

[CI] Add punet export test #623

Merged
merged 6 commits into from
Dec 3, 2024
Merged

Conversation

nithinsubbiah
Copy link
Contributor

@nithinsubbiah nithinsubbiah commented Nov 27, 2024

Adds back punet export test to the CI to run on pre-commit. Takes about ~15 minutes for the tests to run

.github/workflows/ci-sharktank.yml Outdated Show resolved Hide resolved
Comment on lines 59 to 61
- name: Run punet tests
run: |
pytest -v sharktank/ -m "model_punet and export"
Copy link
Member

Choose a reason for hiding this comment

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

Adding 40 lines of boilerplate to run tests matching a combination of marks for one particular model is a pretty bad code smell. Workflow changes generally shouldn't be required to add test coverage - tests should just get picked up by existing workflows automatically.

The work in #584 will simplify the pip install steps, but the test setup still needs more refactoring. Why are these tests not running as part of pytest -n 4 sharktank/ below? Maybe we could add a "integration test" mark or directory path and run those in a job, instead of specializing this to punet? (Remember - we're going to be supporting 10s-100s of models, and we can't scale this sort of test or workflow code as currently written)

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah Nithin is going to add an integration test mark for now. We can also have it all under pytest -n 4 sharktank/ but maybe good to have a bit of separation, so it is clear what jobs are testing going forward when bringing in a lot more models

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added this test as the first of many integration tests, I think its better to keep it as a separate tab integration test as Sai suggested

Copy link
Member

Choose a reason for hiding this comment

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

As part of #584, I think we should keep integration tests in separate workflow files that use package builds while we keep unit tests building from source.

This should merge with https://github.com/nod-ai/shark-ai/blob/main/.github/workflows/ci-llama-quick-tests.yaml and https://github.com/nod-ai/shark-ai/blob/main/.github/workflows/ci_eval_short.yaml as just "short integration tests" (20-30 minute target)

It can start here for now, but it will need to move soon IMO.

.github/workflows/ci-sharktank.yml Outdated Show resolved Hide resolved
@marbre
Copy link
Collaborator

marbre commented Nov 28, 2024

Seems running punet_quick takes ~ 15 minutes on pre-summit when using the GH-hosted runners (see https://github.com/nod-ai/shark-ai/actions/runs/12061110538/job/33632617843?pr=623). Might be a little to long for pre-summit still?

@saienduri
Copy link
Contributor

15 minutes should be fine. If that's too long, we can switch to the mi250 runners

Copy link
Member

@ScottTodd ScottTodd left a comment

Choose a reason for hiding this comment

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

Please add a PR description explaining what new test coverage this adds and how much CI time it takes.

@nithinsubbiah nithinsubbiah enabled auto-merge (squash) December 2, 2024 19:41
@nithinsubbiah nithinsubbiah merged commit 5b75ea1 into nod-ai:main Dec 3, 2024
8 checks passed
@nithinsubbiah nithinsubbiah deleted the punet_export_ci branch December 3, 2024 01:54
monorimet pushed a commit that referenced this pull request Dec 13, 2024
Adds back punet export test to the CI to run on pre-commit. Takes about
~15 minutes for the tests to run
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.

4 participants