You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sycl/test-e2e/ESIMD/hardware_dispatch.cpp is failing with dev-igc , so we XFAIL it first for now in #14761 .
The issue is when we use igc-dev build, hardware_dispatch.cpp will fail. If we build the igc locally using the same commit, it will pass. And when they build the same commit in the release that we use in normal testing, it also passed.
Looks like there are some differences in how igc is build in CI and built in release that is causing the issue.
To reproduce
remove the XFAIL and run test using igc_dev env.
Environment
OS: Linux
Target device and vendor: Intel GPU
DPC++ version:
Dependencies version: igc-dev
Additional context
No response
The text was updated successfully, but these errors were encountered:
@jsji My understanding is we believe the problem is in the way the igc-dev packages we use in CI are built and not a product issue. I asked the IGC team to investigate this before and they refused because they do not support the packages we are using. Not sure if there is anything for the ESIMD team to do here.
@jsji My understanding is we believe the problem is in the way the igc-dev packages we use in CI are built and not a product issue. I asked the IGC team to investigate this before and they refused because they do not support the packages we are using. Not sure if there is anything for the ESIMD team to do here.
Yes. Understand. So this is more of a FYI to ESIMD team that this test is XFAILed in igc-dev CI testing.
I think this will be a limitation for near future. We may spend time working with IGC CI team to investigate later once we have more resource to do so.
Describe the bug
sycl/test-e2e/ESIMD/hardware_dispatch.cpp
is failing with dev-igc , so we XFAIL it first for now in #14761 .The issue is when we use igc-dev build, hardware_dispatch.cpp will fail. If we build the igc locally using the same commit, it will pass. And when they build the same commit in the
release
that we use in normal testing, it also passed.Looks like there are some differences in how igc is build in CI and built in
release
that is causing the issue.To reproduce
remove the XFAIL and run test using igc_dev env.
Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: