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.

streaming: forwards metadata and status failed #355

Description

@flaky-bot

This test failed!

To configure my behavior, see the Flaky Bot documentation.

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


commit: 52f2bb71a1fd9676d2d2e68590324e0f9d92d278
buildURL: Build Status, Sponge
status: failed

Test output
Input A expected to strictly deep-equal input B:
+ expected - actual

{
code: 200,
details: '',

  • message: 'OK'
  • message: 'OK',

  • metadata: {

  • metadata: true
    
  • }
    }

    • expected - actual

    {
    "code": 200
    "details": ""
    "message": "OK"

    • "metadata": {
    • "metadata": true
    • }
      }

AssertionError [ERR_ASSERTION]: Input A expected to strictly deep-equal input B:

  • expected - actual

    {
    code: 200,
    details: '',

  • message: 'OK'
  • message: 'OK',
  • metadata: {
  • metadata: true
    
  • }
    }
    at check (build/test/unit/streaming.js:195:24)
    at StreamProxy.s.on.data (build/test/unit/streaming.js:203:13)
    at Timeout.setTimeout [as _onTimeout] (build/test/unit/streaming.js:173:19)

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.
    flakybot: flakyTells the Flaky Bot not to close or comment on this issue.
    on Nov 27, 2021
  2. flaky-bot commented on Nov 27, 2021

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

  3. added
    🚨This issue needs some love.
    and removed
    🚨This issue needs some love.
    on Dec 2, 2021
  4. added
    priority: p2Moderately-important priority. Fix may not be included in next release.
    and removed
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    on Dec 6, 2021
  5. flaky-bot commented on Feb 15, 2022

    @flaky-bot
    Author

    Oops! Looks like this issue is still flaky. It failed again. 😬

    I reopened the issue, but a human will need to close it again.


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

    Test output
    Expected values to be strictly deep-equal:
    + actual - expected
    

    {
    code: 200,
    details: '',
    message: 'OK',

    • metadata: {

    • metadata: true
      
    • }
      }

      • expected - actual

      {
      "code": 200
      "details": ""
      "message": "OK"

      • "metadata": {
      • "metadata": true
      • }
        }

    AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:

    • actual - expected

      {
      code: 200,
      details: '',
      message: 'OK',

    • metadata: {
    • metadata: true
      
    • }
      }
      at check (build/test/unit/streaming.js:195:24)
      -> /workspace/test/unit/streaming.ts:235:16
      at StreamProxy. (build/test/unit/streaming.js:203:13)
      -> /workspace/test/unit/streaming.ts:244:7
      at Timeout._onTimeout (build/test/unit/streaming.js:173:19)
      -> /workspace/test/unit/streaming.ts:208:11
      at listOnTimeout (internal/timers.js:554:17)
      at processTimers (internal/timers.js:497:7)
  6. added
    🚨This issue needs some love.
    and removed
    🚨This issue needs some love.
    on May 16, 2022
  7. summer-ji-eng commented on May 31, 2022

    @summer-ji-eng
    Contributor

    I think it is a flaky test. The comparison between the object expectedResponse and received data should be pass using deepStrictEqual.

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

Metadata

Metadata

Assignees

Labels

🚨This issue needs some love.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: p2Moderately-important priority. Fix may not be included in 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