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.

Sign up for GitHub

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

Jump to bottom

Configuration class Initialization fuzzing the constructor: Should return default values failed #733

Closed
flaky-bot bot opened this issue Nov 18, 2023 · 2 comments
Closed

Configuration class Initialization fuzzing the constructor: Should return default values failed #733

flaky-bot bot opened this issue Nov 18, 2023 · 2 comments
Assignees
@cindy-peng
Labels
api: clouderrorreporting Issues related to the googleapis/nodejs-error-reporting API. 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: p3 Desirable enhancement or fix. May not be included in 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 Nov 18, 2023

Note: #711 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

commit: 3f883e2
buildURL: Build Status, Sponge
status: failed
@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 Nov 18, 2023
@product-auto-label product-auto-label bot added the api: clouderrorreporting Issues related to the googleapis/nodejs-error-reporting API. label Nov 18, 2023
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Nov 19, 2023
@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Nov 19, 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 (3f883e2), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

@triplequark triplequark added priority: p3 Desirable enhancement or fix. May not be included in next release. and removed priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Nov 27, 2023
@kolea2
Copy link

kolea2 commented May 16, 2024

Fixed in #742

@kolea2 kolea2 closed this as completed May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cindy-peng cindy-peng

Labels
api: clouderrorreporting Issues related to the googleapis/nodejs-error-reporting API. 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: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kolea2 @triplequark @cindy-peng