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

Regression ci #2350

Closed
wants to merge 3 commits into from
Closed

Regression ci #2350

wants to merge 3 commits into from

Conversation

Ryo-not-rio
Copy link
Contributor

Adding a regression test ci to compare a PR against the main branch

@Ryo-not-rio Ryo-not-rio requested review from a team as code owners January 7, 2025 15:55
@Ryo-not-rio Ryo-not-rio force-pushed the regression-ci branch 2 times, most recently from d706bf9 to db2314c Compare January 7, 2025 16:12
@theComputeKid theComputeKid marked this pull request as draft January 7, 2025 17:24
@theComputeKid
Copy link
Member

Changing this to draft so we don't annoy the rest of the world by tagging the reviewers. You should be able to continue working on it as usual pushing to the draft PRs and the github actions will still run.

runs-on: ${{ matrix.config.label }}
steps:

- name: Checkout oneDNN
Copy link
Contributor

Choose a reason for hiding this comment

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

I worry about replicating all this oneDNN building logic. Can we not have a common build oneDNN pipeline and use the artifacts from it to test or benchmark?

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.

3 participants