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 CI #708

Open
johnholdun opened this issue Nov 1, 2022 · 3 comments
Open

Fix CI #708

johnholdun opened this issue Nov 1, 2022 · 3 comments
Assignees

Comments

@johnholdun
Copy link
Contributor

It looks like CircleCI stopped returning results somewhat recently (see this PR, for example). We should either fix the config/API keys/whatever, or switch to GitHub Actions. I think my preference is for the latter.

@mcorrello
Copy link

It looks like the pipeline failed to run because the user who triggered the pipeline (the PR author) is not authorized in CircleCI. Either they need to logout and log back in or clear their CircleCi OAuth and re-authenticate.

More details from CircleCI support are here.

In the latest pipelines for parser they appear to still run successfully with a different user:

Image

@mcorrello
Copy link

To prevent this from happening again, we could switch to using GitHub Actions. Otherwise having the user who isn't triggering pipelines successfully try following the steps from CircleCi support should fix the issue.

Any preference on the fix? @johnholdun

@johnholdun
Copy link
Contributor Author

I'm certainly in favor of switching to GitHub Actions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants