-
Notifications
You must be signed in to change notification settings - Fork 128
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]: generic schedule main multi-subjects slsa3 #601
Comments
Seems like another rekor error: Maybe some kind of backwards incompatibility with /cc @asraa |
Hmmm checking in on this. I'll try to reproduce it. |
Locally, things worked fine (I usually comment out the provider code and give an empty GH workflow context to run It is very weird that this might be a flake. I went through Rekor logs and searched via time to find the Rekor entry:
Running I will try with |
I also tried a Unfortunately, the inclusion proof size is not "reproducible" -- the current inclusion proof for that entry is now 20 hashes long, as opposed to the 14 sized one from before. |
Ok, I guess we can see if it closes on its own when it runs next and keep our eye out for similar errors in the future. |
Repo: https://github.com/slsa-framework/example-package/tree/main Tests are passing now. Closing this issue. |
Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2709376655
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.multi-subjects.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.multi-subjects.slsa3.yml
Trigger: schedule
Branch: main
Date: Thu Jul 21 04:51:41 UTC 2022
The text was updated successfully, but these errors were encountered: