Skip to content

run/logging-manual: "before all" hook for "can be reached by an HTTP request" failed #2915

Description

@flaky-bot

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


commit: 4ce1291
buildURL: Build Status, Sponge
status: failed

Test output
spawnSync /bin/sh ETIMEDOUT
Error: spawnSync /bin/sh ETIMEDOUT
    at Object.spawnSync (internal/child_process.js:1107:20)
    at spawnSync (child_process.js:776:24)
    at execSync (child_process.js:858:15)
    at Context. (test/system.test.js:99:7)
    at processImmediate (internal/timers.js:464:21)

Activity

  1. added
    flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    on Dec 7, 2022
  2. added
    api: runIssues related to the Cloud Run API.
    samplesIssues that are directly related to samples.
    on Dec 7, 2022
  3. ace-n commented on Dec 7, 2022

    @ace-n
    Contributor

    It looks like the initial Cloud Build failed.

    We can make have made it {less flaky, easier to debug} by:

    • Adding retries
    • Logging gcloud's stdout and/or stderr
  4. assigned and unassigned on Dec 7, 2022
  5. flaky-bot commented on Dec 12, 2022

    @flaky-bot
    Author

    Looks like this issue is flaky. 😟

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

    A human should fix and close this.


    commit: 78f43d2
    buildURL: Build Status, Sponge
    status: failed

    Test output
    Cloud Run service URL not found
    Error: Cloud Run service URL not found
        at Context. (test/system.test.js:136:28)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
  6. added
    flakybot: flakyTells the Flaky Bot not to close or comment on this issue.
    on Dec 12, 2022
  7. assigned and unassigned on Dec 12, 2022
  8. ace-n commented on Dec 13, 2022

    @ace-n
    Contributor

    I've submitted #2923 which:

    1. Adds retries to gcloud commands
    2. Properly logs gcloud command failures

    This was since reopened.


    Assigning to @averikitsch for investigation since they're on rotation this week.

  9. reopened this on Dec 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

api: runIssues related to the Cloud Run API.flakybot: flakyTells the Flaky Bot not to close or comment on this issue.flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.samplesIssues that are directly related to samples.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions