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

re-triage test_nn #653

Closed
5 tasks done
yuchengliu1 opened this issue Jul 25, 2024 · 0 comments
Closed
5 tasks done

re-triage test_nn #653

yuchengliu1 opened this issue Jul 25, 2024 · 0 comments
Assignees
Milestone

Comments

@yuchengliu1
Copy link
Contributor

yuchengliu1 commented Jul 25, 2024

🐛 Describe the bug

#258
these cases are target 2.5

Versions

main

@yuchengliu1 yuchengliu1 added this to the PT2.5 milestone Jul 25, 2024
This was referenced Jul 30, 2024
github-merge-queue bot pushed a commit that referenced this issue Jul 31, 2024
…ompatible for XPU (#665)

This fixes issues from #653

The case is verifying an expected assertion log raised in kernel. We
have different log in XPU backend, different keyword (we have no
'CUDA'), different index (we are using work item).
Original test case uses CUDA specific calls, and expected assert message
returned from CUDA. The test cases are now rewritten in `test_nn_xpu.py`
to adapt to XPU specific counterparts.

- "test_cross_entropy_loss_2d_out_of_bounds_class_index_xpu_float16",
- "test_cross_entropy_loss_2d_out_of_bounds_class_index_xpu_float32",
@daisyden daisyden closed this as completed Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants