Skip to content
This repository was archived by the owner on Mar 19, 2026. It is now read-only.
This repository was archived by the owner on Mar 19, 2026. It is now read-only.

Run end-to-end test: should be able to run tests against gRPC server failed #344

Closed

Description

@flaky-bot

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


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

Test output
Command failed with exit code 1: npm start
Error: Command failed with exit code 1: npm start
    at makeError (node_modules/execa/lib/error.js:60:11)
    at handlePromise (node_modules/execa/index.js:118:26)
    at runMicrotasks ()
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Context. (build/test/system-test/test.endtoend.js:67:9)
        -> /workspace/test/system-test/test.endtoend.ts:75:5

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 Feb 20, 2022
  2. flaky-bot commented on Feb 21, 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.


    When run at the same commit (bee3781ee4741a845597dad79bf4a0998c716fc1), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

  3. added
    flakybot: flakyTells the Flaky Bot not to close or comment on this issue.
    on Feb 21, 2022
  4. summer-ji-eng commented on Feb 23, 2022

    @summer-ji-eng
    Contributor

    Flaky issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    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.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