-
Notifications
You must be signed in to change notification settings - Fork 769
Tests failing on BMG Windows #17165
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
Labels
Comments
sarnex
added a commit
that referenced
this issue
Mar 6, 2025
We got a Windows BMG machine, so add Windows BMG testing. There are two categories of failures here: consistent failures/timeouts and really slow tests causing CI to take 30min extra. I disabled both of these and made two GH issues: [one](#17165), [two](#17255). --------- Signed-off-by: Sarnie, Nick <[email protected]>
Noting that additional graph fails outwith
If the RecordReplay tests fail it is likely that other Graph tests could also fail, so disabling all graph tests on Windows BMG until this can be investigated #17348 |
sarnex
pushed a commit
that referenced
this issue
Mar 7, 2025
#17348) We currently only disable the RecordReplay variant of E2E testing on battlemage, however we have many other tests and the likihood is that if the RecordReplay tests are failing then other tests will start failing too. Disable all Graphs tests until Graph support on Windows battlemage can be investigated more thoroughly. See #17165
AlexeySachkov
pushed a commit
to AlexeySachkov/llvm
that referenced
this issue
Mar 31, 2025
intel#17348) We currently only disable the RecordReplay variant of E2E testing on battlemage, however we have many other tests and the likihood is that if the RecordReplay tests are failing then other tests will start failing too. Disable all Graphs tests until Graph support on Windows battlemage can be investigated more thoroughly. See intel#17165
AlexeySachkov
pushed a commit
to AlexeySachkov/llvm
that referenced
this issue
Mar 31, 2025
We got a Windows BMG machine, so add Windows BMG testing. There are two categories of failures here: consistent failures/timeouts and really slow tests causing CI to take 30min extra. I disabled both of these and made two GH issues: [one](intel#17165), [two](intel#17255). --------- Signed-off-by: Sarnie, Nick <[email protected]>
AlexeySachkov
added a commit
that referenced
this issue
Apr 1, 2025
This is a joined cherry-pick of #17347 and #17105 made to align disabled tests between `sycl` and `sycl-rel-6_1_0` branches to make the pre-commit more stable on the latter. Descriptions of cherry-picked commits: --- [SYCL][Graph][E2E] Disable all Graph E2E testing on Windows Battlemage (#17348) We currently only disable the RecordReplay variant of E2E testing on battlemage, however we have many other tests and the likihood is that if the RecordReplay tests are failing then other tests will start failing too. Disable all Graphs tests until Graph support on Windows battlemage can be investigated more thoroughly. See #17165 Patch-By: Ewan Crawford <[email protected]> --- [CI] Add Windows BMG testing in precommit (#17105) We got a Windows BMG machine, so add Windows BMG testing. There are two categories of failures here: consistent failures/timeouts and really slow tests causing CI to take 30min extra. I disabled both of these and made two GH issues: [one](#17165), [two](#17255). Patch-by: Sarnie, Nick <[email protected]> ---
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
sycl/test-e2e/Adapters/level_zero_eager_init.cpp
and
Seems all graph and matrix tests fail, in addition to one DeviceLib
link
example failures:
To reproduce
No response
Environment
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: