-
Notifications
You must be signed in to change notification settings - Fork 8
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
E2E tests failing with Cache not found for input keys #243
Comments
It looks like there is some problem related to loading
|
Similar issues seem to be created in GitHub Actions cache repository in past few days:
We had updated revision of actions/cache last week in #241 . I think for now we can try reverting to the previous version of actions/cache |
…jkube#243) Latest update of actions/cache seems to be causing issues in E2E test runs. Looks like some bug has been introduced (linked in the issue comment). Reverting to previous version of actions/cache for now. Signed-off-by: Rohan Kumar <[email protected]>
Latest update of actions/cache seems to be causing issues in E2E test runs. Looks like some bug has been introduced (linked in the issue comment). Reverting to previous version of actions/cache for now. Signed-off-by: Rohan Kumar <[email protected]>
The issue is still there even after merging this fix. Need to think of something else. |
From what I've seen, it seems that the problem is related to the Runner VM and the version of zstd. |
We can either add another step for downgrading zstd to 1.5.0 or wait for this PR to get merged actions/cache#1118 |
Let's wait a couple of hours and see if they merge it. Else we can implement the temporary workaround. |
The abovementioned PR seems to have been merged. Let me try to bump actions/cache to this revision |
…a0a42d2b0` revision (eclipse-jkube#243) Upgrade actions/cache to latest revision that contains fix related to zsh Signed-off-by: Rohan Kumar <[email protected]>
…a0a42d2b0` revision (eclipse-jkube#243) Upgrade actions/cache to latest revision that contains fix related to zstd Signed-off-by: Rohan Kumar <[email protected]>
…a0a42d2b0` revision (eclipse-jkube#243) Upgrade actions/cache to latest revision that contains fix related to zstd Signed-off-by: Rohan Kumar <[email protected]>
…a0a42d2b0` revision (#243) Upgrade actions/cache to latest revision that contains fix related to zstd Signed-off-by: Rohan Kumar <[email protected]>
Not sure why but i still see failures after restarting some workflows |
…a0a42d2b0` revision (#243) Related to eclipse-jkube/jkube-integration-tests#243 Upgrade actions/cache to latest revision that contains fix related to zstd Signed-off-by: Rohan Kumar <[email protected]>
I think we need to do it on jkubeio/ci as well, as pointed by Marc in #244 (comment) Okay, on E2E workflows I see actions/v2 getting used. Looks like they're picked from jkubeio/ci repository: |
…a0a42d2b0` revision (#243) Related to eclipse-jkube/jkube-integration-tests#243 Upgrade actions/cache to latest revision that contains fix related to zstd Signed-off-by: Rohan Kumar <[email protected]>
This morning I'm seeing unrelated failures in all E2E tests, it seems to be happening in all tests:
These are the PRs I updated this morning:
jkube.io
annotation prefix in favor ofjkube.eclipse.org
for JKubeAnnotations (#1273) jkube#1995The text was updated successfully, but these errors were encountered: