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

Enable weka on models post commit workflow #14431

Merged
merged 1 commit into from
Oct 29, 2024

Conversation

TT-billteng
Copy link
Contributor

@TT-billteng TT-billteng commented Oct 29, 2024

Problem description

There are references to /mnt/MLPerf in models post-commit workflow. We've held the position (so far) that no job post-commit will rely on weka as it has been very unreliable in the past.

What's changed

Let's relax this restriction for the models post-commit sub-pipeline. FAFO

Checklist

  • Post commit CI passes
  • Blackhole Post commit (if applicable)
  • Model regression CI testing passes (if applicable)
  • Device performance regression CI testing passes (if applicable)
  • New/Existing tests provide coverage for changes

@TT-billteng TT-billteng changed the title #0: enable weka on models post commit workflow Enable weka on models post commit workflow Oct 29, 2024
@TT-billteng TT-billteng marked this pull request as ready for review October 29, 2024 20:55
@TT-billteng TT-billteng force-pushed the bteng/enable_weka_models_postcommit branch from 63855b8 to 2b4e351 Compare October 29, 2024 20:55
@tt-rkim
Copy link
Collaborator

tt-rkim commented Oct 29, 2024

FAFO BABY

@TT-billteng TT-billteng merged commit 9680012 into main Oct 29, 2024
8 checks passed
@TT-billteng TT-billteng deleted the bteng/enable_weka_models_postcommit branch October 29, 2024 20:56
ct-clmsn pushed a commit to ct-clmsn/tt-metal that referenced this pull request Nov 12, 2024
#0: enable weka on models post commit workflow
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.

2 participants