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

[IGC-DEV] hardware_dispatch.cpp failing with igc-dev from igc CI #14774

Open
jsji opened this issue Jul 25, 2024 · 3 comments
Open

[IGC-DEV] hardware_dispatch.cpp failing with igc-dev from igc CI #14774

jsji opened this issue Jul 25, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@jsji
Copy link
Contributor

jsji commented Jul 25, 2024

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

  • OS: Linux
  • Target device and vendor: Intel GPU
  • DPC++ version:
  • Dependencies version: igc-dev

Additional context

No response

@jsji jsji added the bug Something isn't working label Jul 25, 2024
@jsji jsji changed the title [IGC-DEV] [IGC-DEV] hardware_dispatch.cpp failing with igc-dev from igc CI Jul 25, 2024
@jsji
Copy link
Contributor Author

jsji commented Jul 25, 2024

FYI. @intel/dpcpp-esimd-reviewers

@sarnex
Copy link
Contributor

sarnex commented Jul 25, 2024

@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
Copy link
Contributor Author

jsji commented Jul 25, 2024

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants