parallel/test-npm-install failure on ARM - Intermittent ?  #13498

Activity

1. mscdex

   added

   armIssues and PRs related to the ARM architecture.Issues and PRs related to the ARM architecture.

   npmIssues and PRs related to the npm client dependency or the npm registry.Issues and PRs related to the npm client dependency or the npm registry.

   testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.

   on Jun 6, 2017
2. Trott commented on Jul 3, 2017

   

   Trott

   on Jul 3, 2017

   Last edited by refack

   Member

   More actions

   The test was marked FLAKY by @refack: https://github.com/nodejs/node/pull/14035/commits/ed19a18
   Problem still happening intermittently.

   _{[refack] updated commit link}
3. Trott

   added

   flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.

   on Jul 3, 2017
4. refack commented on Jul 4, 2017

   

   refack

   on Jul 4, 2017

   Contributor

   More actions

   https://ci.nodejs.org/job/node-test-binary-arm/9040/RUN_SUBSET=3,label=pi3-raspbian-jessie/

   128		parallel/test-npm-install	TODO : Fix flaky test
   		duration_ms	120.128
   		severity	fail
   		stack		timeout
   
5. Trott commented on Jul 14, 2017

   

   Trott

   on Jul 14, 2017

   Member

   More actions

   Failing on Windows too:

   https://ci.nodejs.org/job/node-test-binary-windows/9816/RUN_SUBSET=0,VS_VERSION=vcbt2015,label=win10/console

   not ok 226 parallel/test-npm-install
     ---
     duration_ms: 0.901
     severity: fail
     stack: |-
       assert.js:48
         throw new errors.AssertionError({
         ^
       
       AssertionError [ERR_ASSERTION]: npm install got error code 1
           at ChildProcess.handleExit (c:\workspace\node-test-binary-windows\RUN_SUBSET\0\VS_VERSION\vcbt2015\label\win10\test\parallel\test-npm-install.js:54:10)
           at ChildProcess.<anonymous> (c:\workspace\node-test-binary-windows\RUN_SUBSET\0\VS_VERSION\vcbt2015\label\win10\test\common\index.js:513:15)
           at emitTwo (events.js:125:13)
           at ChildProcess.emit (events.js:213:7)
           at Process.ChildProcess._handle.onexit (internal/child_process.js:201:12)
     ...
6. BridgeAR commented on Sep 28, 2017

   

   BridgeAR

   on Sep 28, 2017

   Member

   More actions

   Is this still an issue? I am not aware that we ran into this one recently. The test itself was changed to output better debugging information in case of a failure since this was reported.
7. Trott commented on Sep 29, 2017

   

   Trott

   on Sep 29, 2017

   Member

   More actions

   Haven't noticed it lately although I haven't been as meticulous about watching CI as I once was. Nonetheless, I think this can be closed. It can always be re-opened if it starts failing again.
8. Trott

   closed this as completedon Sep 29, 2017
9. Trott

   added 2 commits that reference this issue on Mar 8, 2018

   test: remove flaky status for test-npm-install

   ...

   43b1d95

   test: remove flaky status for test-npm-install

   ...

   9757906
10. targos

    added a commit that references this issue on Mar 17, 2018

    test: remove flaky status for test-npm-install

    ...

    6c455a7
11. MylesBorins

    added a commit that references this issue on Mar 20, 2018

    test: remove flaky status for test-npm-install

    ...

    411f3e0
12. MayaLekova

    added a commit that references this issue on May 8, 2018

    test: remove flaky status for test-npm-install

    ...

    473b6cc