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

Fix Automated Pulumi/Pulumi upgrade job #910

Closed
t0yv0 opened this issue Mar 23, 2023 · 1 comment · Fixed by #1003
Closed

Fix Automated Pulumi/Pulumi upgrade job #910

t0yv0 opened this issue Mar 23, 2023 · 1 comment · Fixed by #1003
Assignees
Labels
kind/engineering Work that is not visible to an external user resolution/fixed This issue was fixed
Milestone

Comments

@t0yv0
Copy link
Member

t0yv0 commented Mar 23, 2023

What happened?

Automated Pulumi/Pulumi upgrade job is failing.

Expected Behavior

Job works

Steps to reproduce

Observe GitHub Actions logs

Output of pulumi about

N/A

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@t0yv0 t0yv0 added needs-triage Needs attention from the triage team kind/bug Some behavior is incorrect or out of spec and removed needs-triage Needs attention from the triage team labels Mar 23, 2023
@t0yv0 t0yv0 added kind/engineering Work that is not visible to an external user and removed kind/bug Some behavior is incorrect or out of spec labels Apr 5, 2023
@jazzyfresh
Copy link
Contributor

Example failed pulumi core update #987

Linting step fails with error message

level=error msg="Running error: context loading failed: no go files to analyze"

Similar errors encountered for other users of golangci-lint github action golangci/golangci-lint#825

  • Users say error message is misleading, it indicates a failed go build
  • Can be resolved by running go mod tidy in the lint step

@t0yv0 t0yv0 added this to the 0.87 milestone Apr 18, 2023
@t0yv0 t0yv0 self-assigned this Apr 18, 2023
@t0yv0 t0yv0 added the resolution/fixed This issue was fixed label Apr 18, 2023
@t0yv0 t0yv0 closed this as completed Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/engineering Work that is not visible to an external user resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants