[GHA] Uplift Linux IGC Dev RT version to igc-dev-3c5dac9

[bb-sycl]

Scheduled igc dev drivers uplift

[sarnex]

@jsji Any idea on this docker postcommit fail?

https://github.com/intel/llvm/actions/runs/10561303761/job/29259192728

ERROR: failed to solve: process "/bin/sh -c install_driver_opt=\"dependencies.json dependencies-igc-dev.json --use-dev-igc\";     GITHUB_TOKEN=$(cat /run/secrets/github_token) /install_drivers.sh $install_driver_opt --all" did not complete successfully: exit code: 9
Error: buildx failed with: ERROR: failed to solve: process "/bin/sh -c install_driver_opt=\"dependencies.json dependencies-igc-dev.json --use-dev-igc\";     GITHUB_TOKEN=$(cat /run/secrets/github_token) /install_drivers.sh $install_driver_opt --all" did not complete successfully: exit code: 9

[jsji]

@jsji Any idea on this docker postcommit fail?

https://github.com/intel/llvm/actions/runs/10561303761/job/29259192728

ERROR: failed to solve: process "/bin/sh -c install_driver_opt=\"dependencies.json dependencies-igc-dev.json --use-dev-igc\";     GITHUB_TOKEN=$(cat /run/secrets/github_token) /install_drivers.sh $install_driver_opt --all" did not complete successfully: exit code: 9
Error: buildx failed with: ERROR: failed to solve: process "/bin/sh -c install_driver_opt=\"dependencies.json dependencies-igc-dev.json --use-dev-igc\";     GITHUB_TOKEN=$(cat /run/secrets/github_token) /install_drivers.sh $install_driver_opt --all" did not complete successfully: exit code: 9

This is known limitation -- if the dev igc version we use (after uplift) are too old (more than 1 week old), we won't be able to download it from GitHub CI anymore, then it will fail.

[sarnex]

@jsji Thanks, I don't need to revert the PR right, this version just wont be used?

Could we update the bot to close any PRs after the IGC max retention days passes?

[jsji]

@jsji Thanks, I don't need to revert the PR right, this version just wont be used?

Yes, we don't. We will still use the old docker with very old version, until we uplift with new one succesfully.

Could we update the bot to close any PRs after the IGC max retention days passes?

We can do that, but it probably better if we could merge the PR when it is green, don't let it pass the date.

[sarnex]

We can do that, but it probably better if we could merge the PR when it is green, don't let it pass the date.

Sure, I was out last week and it seems nobody else looks at these so I guess whoops :)

[jsji]

We can do that, but it probably better if we could merge the PR when it is green, don't let it pass the date.

Sure, I was out last week and it seems nobody else looks at these so I guess whoops :)

Yeah, not your problem at all. Just wondering any other way that we can make sure we merge it on time?

[aelovikov-intel]

Yeah, not your problem at all. Just wondering any other way that we can make sure we merge it on time?

Make matrix/esimd teams codeowners for this file as they're the most interested in dev IGC testing. Ensure that they look into the failures in such PRs first, because I have an impression those are the tests that usually fail (might be wrong here).

[sarnex]

I think you're right and I talked with Jinsong offline and we're gonna do that, thanks

[jsji]

PR fo codeowner update: #15193