Skip to content

Peer list test fails on make #56

@georgmittendorfer

Description

@georgmittendorfer

Expected behaviour

No test failures when running yarn make on master.

Actual behaviour

command line:

yarn make
yarn run v1.3.2
$ npm run test && npm run build && npm run make:binaries

> nelson.cli@0.4.0 test /home/.../prog/nelson.cli
> jest -b

 PASS  src/api/__tests__/api-test.js (13.519s)
 FAIL  src/node/__tests__/peer-list-test.js (26.382s)
  ● PeerListTest › should return correct peer trusts

    expect(received).toBeGreaterThan(expected)
    
    Expected value to be greater than:
      1
    Received:
      0.5447916099999999
      
      at src/node/__tests__/peer-list-test.js:265:70
          at <anonymous>

Test Suites: 1 failed, 1 passed, 2 of 10 total
Tests:       1 failed, 21 passed, 22 total
Snapshots:   0 total
Time:        29.779s
Ran all test suites.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! nelson.cli@0.4.0 test: `jest -b`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the nelson.cli@0.4.0 test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/.../.npm/_logs/2018-02-18T09_59_22_012Z-debug.log
error Command failed with exit code 1.

018-02-18T09_59_22_012Z-debug.log:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'test' ]
2 info using npm@5.6.0
3 info using node@v9.5.0
4 verbose run-script [ 'pretest', 'test', 'posttest' ]
5 info lifecycle nelson.cli@0.4.0~pretest: nelson.cli@0.4.0
6 info lifecycle nelson.cli@0.4.0~test: nelson.cli@0.4.0
7 verbose lifecycle nelson.cli@0.4.0~test: unsafe-perm in lifecycle true
8 verbose lifecycle nelson.cli@0.4.0~test: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/.../prog/nelson.cli/node_modules/.bin:/home/.../prog/nelson.cli/node_modules/.bin:/home/.../.config/yarn/link/node_modules/.bin:/home/.../prog/nelson.cli/node_modules/.bin:/home/.../.config/yarn/link/node_modules/.bin:/home/.../.yarn/bin:/usr/lib/node_modules/npm/bin/node-gyp-bin:/usr/bin/node_modules/npm/bin/node-gyp-bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/opt/maven/bin
9 verbose lifecycle nelson.cli@0.4.0~test: CWD: /home/.../prog/nelson.cli
10 silly lifecycle nelson.cli@0.4.0~test: Args: [ '-c', 'jest -b' ]
11 silly lifecycle nelson.cli@0.4.0~test: Returned: code: 1  signal: null
12 info lifecycle nelson.cli@0.4.0~test: Failed to exec test script
13 verbose stack Error: nelson.cli@0.4.0 test: `jest -b`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16)
13 verbose stack     at EventEmitter.emit (events.js:160:13)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:160:13)
13 verbose stack     at maybeClose (internal/child_process.js:943:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
14 verbose pkgid nelson.cli@0.4.0
15 verbose cwd /home/.../prog/nelson.cli
16 verbose Linux 4.9.0-5-amd64
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "test"
18 verbose node v9.5.0
19 verbose npm  v5.6.0
20 error code ELIFECYCLE
21 error errno 1
22 error nelson.cli@0.4.0 test: `jest -b`
22 error Exit status 1
23 error Failed at the nelson.cli@0.4.0 test script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

(replaced my user name with three dots)

Steps to reproduce

Follow steps on https://github.com/SemkoDev/nelson.cli for building locally.

Basic Info

  • Operating System: Debian (Linux 4.9.0-5-amd64 Unit tests fail sporadically  #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux)
  • Node (npm) Version: 5.6.0
  • IRI Version: 1.4.2.1
  • Nelson version: current master (1db62e4)

Nelson Info

  • Epoch:
  • Cycle:
  • Connected peers:

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