@evanlucas made a good find just now. These build machines have not been running any tap tests under test-ci: Centos5-32 Centos5-64 Centos6-64 https://jenkins-iojs.nodesource.com/view/iojs/job/iojs+any-pr+multi/nodes=centos5-32/731/ https://jenkins-iojs.nodesource.com/view/iojs/job/iojs+any-pr+multi/nodes=centos5-64/731/ https://jenkins-iojs.nodesource.com/view/iojs/job/iojs+any-pr+multi/nodes=centos6-64/731/ I looked back and this appears to be the case all the way back to late April when we started using test-ci + tap tests again. Can we have Jenkins error if no tests were run? this just seems bad. Centos7-64 however seems ok, it is showing tests run. @rvagg / @jbergstroem / @nodejs/build
@evanlucas made a good find just now.
These build machines have not been running any tap tests under test-ci:
Centos5-32
Centos5-64
Centos6-64
https://jenkins-iojs.nodesource.com/view/iojs/job/iojs+any-pr+multi/nodes=centos5-32/731/
https://jenkins-iojs.nodesource.com/view/iojs/job/iojs+any-pr+multi/nodes=centos5-64/731/
https://jenkins-iojs.nodesource.com/view/iojs/job/iojs+any-pr+multi/nodes=centos6-64/731/
I looked back and this appears to be the case all the way back to late April when we started using test-ci + tap tests again.
Can we have Jenkins error if no tests were run? this just seems bad.
Centos7-64 however seems ok, it is showing tests run.
@rvagg / @jbergstroem / @nodejs/build