add fast test to check with bfloat16 - #2581
Conversation
|
@copilot in test_bf16_precision, do you check that speedup is here with no error? |
It wasn't — fixed in the latest commit. The run call now passes
|
There was a problem hiding this comment.
Pull request overview
This PR adds a new CLI smoke test intended to exercise the olive optimize + olive run --test flow when targeting BF16 precision, and to validate that the discrepancy report is produced with a speedup metric.
Changes:
- Add
test_bf16_precision/_assert_bf16_precisionto run an optimize+run workflow with--precision bf16. - Validate that
discrepancy_check_results.jsonis written and includes a numeric, positivespeedupvalue.
| "--device", | ||
| "cpu", | ||
| "--provider", | ||
| "CPUExecutionProvider", |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
@copilot resolve the merge conflicts in this pull request |
|
@copilot it does not seem related to my changes test/passes/onnx/test_mnb_to_qdq.py:154: in test_mnb_to_qdq |
I checked this branch against |
fix discrepancy tests for bfloat16