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

google.golang.org/api/idtoken: TestNewClient_WithCredentialFile failed #1833

Closed
flaky-bot bot opened this issue Jan 30, 2023 · 2 comments
Closed

google.golang.org/api/idtoken: TestNewClient_WithCredentialFile failed #1833

flaky-bot bot opened this issue Jan 30, 2023 · 2 comments
Assignees
Labels
flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Jan 30, 2023

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I'm commenting on this issue too often, add the flakybot: quiet label and
I will stop commenting.


commit: 602b6a4
buildURL: Build Status, Sponge
status: failed

Test output
    integration_test.go:58: unable to create Client: oauth2: cannot fetch token: 400 Bad Request
        Response: {"error":"invalid_grant","error_description":"Invalid JWT Signature."}
@flaky-bot flaky-bot bot added flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Jan 30, 2023
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Jan 30, 2023
@flaky-bot
Copy link
Author

flaky-bot bot commented Jan 30, 2023

Looks like this issue is flaky. 😟

I'm going to leave this open and stop commenting.

A human should fix and close this.


When run at the same commit (602b6a4), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

@codyoss codyoss assigned quartzmo and unassigned codyoss Jan 30, 2023
@quartzmo
Copy link
Member

We manually rotated the secret for the credentials used in this test. The secret had failed its last scheduled rotation on 2023-01-01.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

2 participants