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

appengine/redis: "after all" hook for "should be listening" failed #1691

Closed
flaky-bot bot opened this issue Mar 31, 2020 · 24 comments
Closed

appengine/redis: "after all" hook for "should be listening" failed #1691

flaky-bot bot opened this issue Mar 31, 2020 · 24 comments
Assignees
Labels
api: appengine Issues related to the App Engine Admin API API. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. 🚨 This issue needs some love. 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 api: appengine Issues related to the App Engine Admin API API. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Mar 31, 2020
@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 5, 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

@fhinkel fhinkel added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. and removed priority: p2 Moderately-important priority. Fix may not be included in next release. labels Apr 13, 2020
@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 17, 2020

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

@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label Apr 17, 2020
@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 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: 7e5ebe3
buildURL: Build Status, Sponge
status: failed

@flaky-bot
Copy link
Author

flaky-bot bot commented May 6, 2020

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

Test output
process.exitCode is not a function
TypeError: process.exitCode is not a function
    at Context.after (test/server.test.js:6:11)

@flaky-bot
Copy link
Author

flaky-bot bot commented May 8, 2020

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

Test output
process.exitCode is not a function
TypeError: process.exitCode is not a function
    at Context.after (test/server.test.js:6:11)

@flaky-bot
Copy link
Author

flaky-bot bot commented May 9, 2020

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

Test output
process.exitCode is not a function
TypeError: process.exitCode is not a function
    at Context.after (test/server.test.js:6:11)

@flaky-bot
Copy link
Author

flaky-bot bot commented May 12, 2020

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

Test output
process.exitCode is not a function
TypeError: process.exitCode is not a function
    at Context.after (test/server.test.js:6:11)

@flaky-bot
Copy link
Author

flaky-bot bot commented May 13, 2020

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

Test output
process.exitCode is not a function
TypeError: process.exitCode is not a function
    at Context.after (test/server.test.js:6:11)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: appengine Issues related to the App Engine Admin API API. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. 🚨 This issue needs some love. 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

4 participants