Skip to content
This repository has been archived by the owner on Oct 15, 2020. It is now read-only.

Flaky test sequential/test-net-bytes-per-incoming-chunk-overhead #561

Open
kfarnung opened this issue Jun 28, 2018 · 2 comments
Open

Flaky test sequential/test-net-bytes-per-incoming-chunk-overhead #561

kfarnung opened this issue Jun 28, 2018 · 2 comments
Assignees
Labels

Comments

@kfarnung
Copy link
Contributor

  • Version: master
  • Platform: Windows
  • Subsystem: net,test

It looks like sequential/test-net-bytes-per-incoming-chunk-overhead is flaky in the NodeJS Windows CI:

not ok 515 sequential/test-net-bytes-per-incoming-chunk-overhead
  ---
  duration_ms: 11.614
  severity: fail
  exitcode: 1
  stack: |-
    assert.js:273
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: measured 521.699328 bytes per chunk
       at Anonymous function (c:\workspace\node-test-binary-windows\test\sequential\test-net-bytes-per-incoming-chunk-overhead.js:40:3)
       at Reflect.apply (native code:0:0)
       at emit (events.js:187:7)
  …

I've seen this in master and v10.x only in the CI.

@kfarnung kfarnung added the test label Jun 28, 2018
@addaleax
Copy link
Member

You can bump the limit, it makes sense that it’s somewhat engine-specific. If ChakraCore’s ArrayBuffers and TypedArrays are larger than V8’s, then this is an expected result.

@kfarnung
Copy link
Contributor Author

Ok, thanks!

@kfarnung kfarnung self-assigned this Jun 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants