This repository was archived by the owner on Mar 28, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you clarify why this test still fails in Jenkins environment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems to me, that test become pass only on OCL GEN9 Linux test suite. If it is related to the intel/llvm#5867, then test will fail on windows, drivers were updated only for linux.
May be, we can specialize test suites on which this test should pass? I don't know how to do it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test fails on Linux as well. I suggest we investigate the difference between test behavior in Jenkins and GitHub Actions environments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but I don't understand which test suite is used on jenkins for linux.
Yes, we should investigate. I'll try to figure out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I understand correctly, drivers in Github Actions docker container for OCL GEN9 more recent, than in the jenkins.
OCL GEN9 Github Actions have version
22.11.22682
, that matches version from the uplift PR for 'linux_staging'. Can be seen in raw logs from hereJenkins have version
22.10.22597
.Anyway, we can't enable test only for specific driver version. Should we disable it for now, while it fails on some driver versions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You seem to be right. I think we must align driver version for both systems before merging any patches.
@alexbatashev, could you clarify why GHA is using more recent version than buildbot for pre-commit? I assumed it should be used only for nightly jobs.
There is a PR uplifting Jenkins version to 22.11.*, but I see new failures in pre-commit for this change. intel/llvm#5897
Probably the safer way is to rollback the driver version for GHA and commit intel/llvm#5897 together with this patch once all pre-commit issues are addressed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reverted driver version in GHA precommit to 22.10.*.
This patch should go together with intel/llvm#5897.