Investigate flaky test test-vm-syntax-error-stderr #2660

Activity

1. joaocgreis

   added

   buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.

   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 Sep 2, 2015
2. joaocgreis

   added a commit that references this issue on Sep 2, 2015

   test: mark test-vm-syntax-error-stderr as flaky

   ...

   6d7659a
3. Fishrock123 commented on Sep 2, 2015

   

   Fishrock123

   on Sep 2, 2015

   Contributor

   More actions

   not ok 922 - test-vm-syntax-error-stderr.js
   # net.js:523
   # var ret = self.push(buffer);
   # ^
   # 
   # TypeError: Cannot read property 'objectMode' of undefined
   # at Pipe.onread (net.js:523:20)
   

   Uh, this looks like something's stdio failed to spawn? That's not good.
4. joaocgreis

   added 2 commits that reference this issue on Sep 2, 2015

   test: mark test-vm-syntax-error-stderr as flaky

   ...

   68a658d

   test: mark test-vm-syntax-error-stderr as flaky

   ...

   93ba585
5. Fishrock123

   added a commit that references this issue on Sep 3, 2015

   test: mark test-vm-syntax-error-stderr as flaky

   ...

   1865cad
6. whitlockjc commented on Oct 22, 2015

   

   whitlockjc

   on Oct 22, 2015

   Contributor

   More actions

   Mind adding an arm label?
7. Fishrock123

   added

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

   on Oct 22, 2015
8. Fishrock123 commented on Oct 22, 2015

   

   Fishrock123

   on Oct 22, 2015

   Contributor

   More actions

   @whitlockjc Done. :)
9. Fishrock123 commented on Oct 22, 2015

   

   Fishrock123

   on Oct 22, 2015

   Contributor

   More actions

   @joaocgreis I suggest we close this. I am quite sure this was the result of some awful jenkins misconfiguration somewhere, I haven't seen the armv7 bot go conditional pass recently.
10. whitlockjc commented on Oct 22, 2015

    

    whitlockjc

    on Oct 22, 2015

    Contributor

    More actions

    I would offer to help but I don't have an arm environment.
11. joaocgreis commented on Oct 22, 2015

    

    joaocgreis

    on Oct 22, 2015

    MemberAuthor

    More actions

    @Fishrock123 The armv7 machines have been replaced since this was opened, and they are much more stable now. I haven't seen this fail recently either, so let's blame the old machines for now and reopen this if it fails again.
12. joaocgreis

    closed this as completedon Oct 22, 2015
13. Trott

    added 3 commits that reference this issue on Feb 26, 2016

    test: remove flaky designation from fixed tests

    ...

    6a39eb3

    test: remove flaky designation from fixed tests

    ...

    4d6b4c3
14. Fishrock123

    added a commit that references this issue on Mar 2, 2016

    test: remove flaky designation from fixed tests

    ...

    0ebbf6c
15. MylesBorins

    added 2 commits that reference this issue on Mar 17, 2016

    test: remove flaky designation from fixed tests

    ...

    48d069d

    test: remove flaky designation from fixed tests

    ...

    f242e62