Skip to content

weird failures on arm #969

@MylesBorins

Description

@MylesBorins

https://ci.nodejs.org/job/node-test-binary-arm/11453/RUN_SUBSET=3,label=pi1-raspbian-wheezy/console
https://ci.nodejs.org/job/node-test-binary-arm/11453/RUN_SUBSET=6,label=pi1-raspbian-wheezy/console

real	0m34.398s
user	0m13.630s
sys	0m4.760s
+ rm -f ****
+ git checkout -f refs/remotes/jenkins_tmp
Warning: you are leaving 2 commits behind, not connected to
any of your branches:

  6e9f374 added binaries
  2c46fa7 src: explicitly register built-in modules

If you want to keep them by creating a new branch, this may be a good time
to do so with:

 git branch <new-branch-name> 6e9f374

HEAD is now at 93b0099... added binaries

real	0m39.148s
user	0m3.820s
sys	0m20.370s
+ git reset --hard
HEAD is now at 93b0099 added binaries

real	0m12.661s
user	0m3.520s
sys	0m3.350s
+ git clean -fdx
warning: failed to remove out/Release/.nfs0000000000218e500000054b
Build step 'Execute shell' marked build as failure
TAP Reports Processing: START
Looking for TAP results report in workspace using pattern: *.tap
Did not find any matching files. Setting build result to FAILURE.
Checking ^not ok
Jenkins Text Finder: File set '*.tap' is empty
Notifying upstream projects of job completion
Finished: FAILURE

found while testing nodejs/node#16691

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions