-
Notifications
You must be signed in to change notification settings - Fork 814
.github: check_cirrus_cron work around github bug #6120
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
Conversation
So I wondered why our email workflow only reported things for podman... It seems the secrets: inherit is broken and no longer working, I see all jobs on all repos failing with: Error when evaluating 'secrets'. .github/workflows/check_cirrus_cron.yml (Line: 19, Col: 11): Secret SECRET_CIRRUS_API_KEY is required, but not provided while calling. This makes no sense to me I doubled checked the names, nothing changed on our side and it is consistent for all projects. Interestingly this same thing passed on March 10 and 11 (on all repos) but failed before and after this as well. Per[1] we are not alone, anyway let's try to get this working again even if it means more duplication. [1] actions/runner#2709 Signed-off-by: Paul Holzinger <[email protected]>
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.
LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flouthoc, Luap99 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
LGTM
/lgtm |
/hold |
Total success is green with two integration tests still running? That doesn't seem right... |
0db4755
into
containers:main
That is most certainly not right, likely miss configured dependencies in cirrus.yml. Anyway I am not worried about this particular PR breaking anything cirrus related so it should be fine. |
As discovered by Matt[1], without this we could merge PRs even if they have failing rootless integration tests. [1] #6120 (comment) Signed-off-by: Paul Holzinger <[email protected]>
So I wondered why our email workflow only reported things for podman...
It seems the secrets: inherit is broken and no longer working, I see all jobs on all repos failing with:
Error when evaluating 'secrets'. .github/workflows/check_cirrus_cron.yml (Line: 19, Col: 11): Secret SECRET_CIRRUS_API_KEY is required, but not provided while calling.
This makes no sense to me I doubled checked the names, nothing changed on our side and it is consistent for all projects. Interestingly this same thing passed on March 10 and 11 (on all repos) but failed before and after this as well.
Per[1] we are not alone, anyway let's try to get this working again even if it means more duplication.
[1] actions/runner#2709
What type of PR is this?
What this PR does / why we need it:
How to verify it
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?