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

endpoints/getting-started-grpc: "before all" hook for "should request a greeting from a remote Compute Engine instance using an API key" failed #1684

Closed
flaky-bot bot opened this issue Mar 31, 2020 · 26 comments · Fixed by #1794
Assignees
Labels
priority: p2 Moderately-important priority. 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 Mar 31, 2020

This test failed!

To configure my behavior, see the Build Cop Bot documentation.

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


commit: 3692a10
buildURL: Build Status, Sponge
status: failed

@fhinkel fhinkel added priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Mar 31, 2020
@fhinkel fhinkel self-assigned this Mar 31, 2020
@fhinkel
Copy link
Contributor

fhinkel commented Mar 31, 2020

Trying to find an owner for these samples. I think the GCE and GKE endpoints are not defined on CI.

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 2, 2020

commit: c519d07
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 3, 2020

commit: 46f6409
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 4, 2020

commit: 061a536
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 7, 2020

commit: aecc4c6
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 9, 2020

commit: f45ed2e
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 10, 2020

commit: a3f8099
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 11, 2020

commit: c3eff0f
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 14, 2020

commit: 30f851a
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 16, 2020

commit: 85290bf
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 17, 2020

commit: 682fda8
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 18, 2020

commit: fcbb72c
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 19, 2020

commit: e299924
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 20, 2020

commit: 0fbd74d
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 21, 2020

commit: 14df220
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 22, 2020

commit: 3a651b2
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 23, 2020

commit: 0270a10
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 25, 2020

commit: 45b32ee
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 28, 2020

commit: ff69c3b
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 29, 2020

commit: da03d9b
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 30, 2020

commit: 774ee22
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented May 1, 2020

commit: f67bf5e
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented May 2, 2020

commit: 7e5ebe3
buildURL: Build Status, Sponge
status: failed

Test output
Must set ENDPOINTS_API_KEY environment variable!
AssertionError [ERR_ASSERTION]: Must set ENDPOINTS_API_KEY environment variable!
    at Context.before (system-test/endpoints.test.js:38:10)

@flaky-bot
Copy link
Author

flaky-bot bot commented May 6, 2020

commit: 74ab5d7
buildURL: Build Status, Sponge
status: failed

Test output
Must set ENDPOINTS_API_KEY environment variable!
AssertionError [ERR_ASSERTION]: Must set ENDPOINTS_API_KEY environment variable!
    at Context.before (system-test/endpoints.test.js:38:10)

@flaky-bot
Copy link
Author

flaky-bot bot commented May 8, 2020

commit: 479077d
buildURL: Build Status, Sponge
status: failed

Test output
Must set ENDPOINTS_API_KEY environment variable!
AssertionError [ERR_ASSERTION]: Must set ENDPOINTS_API_KEY environment variable!
    at Context.before (system-test/endpoints.test.js:38:10)

@flaky-bot
Copy link
Author

flaky-bot bot commented May 9, 2020

commit: d789132
buildURL: Build Status, Sponge
status: failed

Test output
Must set ENDPOINTS_API_KEY environment variable!
AssertionError [ERR_ASSERTION]: Must set ENDPOINTS_API_KEY environment variable!
    at Context.before (system-test/endpoints.test.js:38:10)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. 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
Development

Successfully merging a pull request may close this issue.

2 participants