Skip to content
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

PRs failing with "Cirrus CI / Build Parsing Results" failed to retrieve "ci/docker_linux/Gemfile": file does not exist #89993

Closed
jmagman opened this issue Sep 13, 2021 · 10 comments
Labels
P1 High-priority issues at the top of the work list team-infra Owned by Infrastructure team

Comments

@jmagman
Copy link
Member

jmagman commented Sep 13, 2021

@cirrus-cicirrus-ci
/ Build Parsing Results
.cirrus.yml#L20
failed to retrieve "ci/docker_linux/Gemfile": file does not exist

Screen Shot 2021-09-13 at 10 36 01 AM

#89988
#89991

Essentially a duplicate of cirruslabs/cirrus-cli#456 but I'm not sure why we're seeing this 2 hours after the fix cirruslabs/cirrus-cli#457.

@jmagman jmagman added team-infra Owned by Infrastructure team P1 labels Sep 13, 2021
@jmagman
Copy link
Member Author

jmagman commented Sep 13, 2021

@fkorotkov Is the fix just not propagated to us, or can we need to do something on our side to pick it up? Or shall I move this issue to cirruslabs/cirrus-cli for investigation?

@fkorotkov
Copy link
Contributor

You can ignore it for now. I've created cirruslabs/cirrus-cli#458 to fix it.

This is a side-effect of the recent feature which will include files you copy into the image in the cache key.

@fkorotkov
Copy link
Contributor

Does it block you from merging?

@keyonghan keyonghan added this to New in Infra Ticket Queue via automation Sep 13, 2021
@jmagman
Copy link
Member Author

jmagman commented Sep 13, 2021

Does it block you from merging?

It doesn't block manual merging, but we use a bot to auto-merge after approval and all tests pass--so that won't work until it's resolved.

@fkorotkov
Copy link
Contributor

Sorry about that! We'll fix it shortly

@christopherfujino
Copy link
Member

Sorry about that! We'll fix it shortly

Thanks Fedor!

@fkorotkov
Copy link
Contributor

I've deployed a workaround to make the check be in neutral status instead of failure so your bot will be able to continue working.

@godofredoc godofredoc moved this from New to Triaged in Infra Ticket Queue Sep 13, 2021
@godofredoc godofredoc moved this from Triaged to In progress in Infra Ticket Queue Sep 13, 2021
@jmagman
Copy link
Member Author

jmagman commented Sep 13, 2021

The neutral check worked, #89996 for example shows the failure but it's not an error.

@jmagman
Copy link
Member Author

jmagman commented Sep 20, 2021

Still seeing the warnings (though they are no longer blocking PRs), filed cirruslabs/cirrus-cli#463 to keep track.

@github-actions
Copy link

github-actions bot commented Oct 4, 2021

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P1 High-priority issues at the top of the work list team-infra Owned by Infrastructure team
Projects
No open projects
Development

No branches or pull requests

4 participants