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

#0: Correcting bad dim check in CCL tests #17392

Merged
merged 3 commits into from
Jan 30, 2025
Merged

Conversation

jvegaTT
Copy link
Contributor

@jvegaTT jvegaTT commented Jan 30, 2025

When setting up the output shard specs in the pytest scripts, it was hardcoded that the tensor be 4D causing incorrect results when the tensor was not 4D.

Checklist

  • Post commit CI passes -- Unable to run due to CI problems, have run testing on local t3k machine.
  • Blackhole Post commit (if applicable)
  • Model regression CI testing passes (if applicable)
  • Device performance regression CI testing passes (if applicable)
  • (For models and ops writers) Full new models tests passes
  • New/Existing tests provide coverage for changes

@jvegaTT jvegaTT merged commit 230f71b into main Jan 30, 2025
9 checks passed
@jvegaTT jvegaTT deleted the jvega/correcting_CCL_tests branch January 30, 2025 21:04
yieldthought pushed a commit that referenced this pull request Jan 31, 2025
When setting up the output shard specs in the pytest scripts, it was
hardcoded that the tensor be 4D causing incorrect results when the
tensor was not 4D.

### Checklist
- [ ] Post commit CI passes -- Unable to run due to CI problems, have
run testing on local t3k machine.
- [ ] Blackhole Post commit (if applicable)
- [ ] Model regression CI testing passes (if applicable)
- [ ] Device performance regression CI testing passes (if applicable)
- [ ] **(For models and ops writers)** Full [new
models](https://github.com/tenstorrent/tt-metal/actions/workflows/full-new-models-suite.yaml)
tests passes
- [ ] New/Existing tests provide coverage for changes
nikileshx pushed a commit to nikileshx/tt-metal that referenced this pull request Feb 3, 2025
When setting up the output shard specs in the pytest scripts, it was
hardcoded that the tensor be 4D causing incorrect results when the
tensor was not 4D.

### Checklist
- [ ] Post commit CI passes -- Unable to run due to CI problems, have
run testing on local t3k machine.
- [ ] Blackhole Post commit (if applicable)
- [ ] Model regression CI testing passes (if applicable)
- [ ] Device performance regression CI testing passes (if applicable)
- [ ] **(For models and ops writers)** Full [new
models](https://github.com/tenstorrent/tt-metal/actions/workflows/full-new-models-suite.yaml)
tests passes
- [ ] New/Existing tests provide coverage for changes
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