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

run/markdown-preview/editor: Can successfully make a request to the Renderer failed #1935

Closed
flaky-bot bot opened this issue Jul 29, 2020 · 3 comments · Fixed by #1938
Closed

run/markdown-preview/editor: Can successfully make a request to the Renderer failed #1935

flaky-bot bot opened this issue Jul 29, 2020 · 3 comments · Fixed by #1938
Assignees
Labels
api: run Issues related to the Cloud Run API. 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 Jul 29, 2020

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


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

Test output
Response code 500 (Internal Server Error)
HTTPError: Response code 500 (Internal Server Error)
    at onResponse (node_modules/got/dist/source/as-promise/index.js:142:28)
    at process._tickCallback (internal/process/next_tick.js:68:7)
@flaky-bot flaky-bot bot added buildcop: issue 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 Jul 29, 2020
@fhinkel fhinkel added the api: run Issues related to the Cloud Run API. label Jul 30, 2020
@grayside
Copy link
Collaborator

Investigating.

@grayside
Copy link
Collaborator

grayside commented Jul 30, 2020

In looking at this sample, I'm finding a number of issues in the sample around how to locally run the tests, structural issues in which unit tests are starting up the http server, and so on. I'm refactoring some to boost stability and clean up the tests in general.

@flaky-bot
Copy link
Author

flaky-bot bot commented Jul 30, 2020

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 (0cbaa0c), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: run Issues related to the Cloud Run API. 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
2 participants