Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Build failing due to 143

See original GitHub issue

https://travis-ci.org/lathonez/clicker/builds/158345791

Presumably this is the error that @pvdyck was referring to:

✔ 40 tests completed
✖ 2 tests failed
FAILED TESTS:
  ClickerForm
    ✖ passes new clicker through to service
      Chrome 53.0.2785 (Linux 0.0.0)
    Expected spy newClickerLocal to have been called with [ Object({ clickerNameInput: 'dave' }) ] but it was never called.
        at Object.<anonymous> (/tmp/app/components/clickerForm/clickerForm.spec.ts:37:42 <- /tmp/234559cf23adb7a1c4581247f438d92e.browserify:159:58)
    Expected spy resetControl to have been called with [ FormControl({ validator: Function, asyncValidator: null, _pristine: false, _touched: false, _onChange: [ Function ], _value: 'dave', _errors: null, _status: 'VALID', _valueChanges: EventEmitter({ _isScalar: false, destination: undefined, source: undefined, observers: [  ], isUnsubscribed: false, isStopped: false, hasErrored: false, dispatching: false, hasCompleted: false, __isAsync: false }), _statusChanges: EventEmitter({ _isScalar: false, destination: undefined, source: undefined, observers: [  ], isUnsubscribed: false, isStopped: false, hasErrored: false, dispatching: false, hasCompleted: false, __isAsync: false }), _parent: FormGroup({ validator: null, asyncValidator: null, _pristine: false, _touched: false, controls: Object({ clickerNameInput: <circular reference: Object> }), _optionals: Object({  }), _valueChanges: EventEmitter({ _isScalar: false, destination: undefined, source: undefined, observers: [  ], isUnsubscribed: false, isStopped: false, hasErrored: false, dispatching: false, hasCompleted: false, __isAsync: false }), _statusChanges: EventEmitter({ _isScalar: false, destination: undefined, source: undefined, observers: [  ], isUnsubscribed: false, isStopped: false, hasErrored: false, dispatching: false, hasCompleted: false, __isAsync: false }), _value: Object({ clickerNameInput: 'dave' }), _errors: null, _status: 'VALID' }) }) ] but it was never called.
        at Object.<anonymous> (/tmp/app/components/clickerForm/clickerForm.spec.ts:38:31 <- /tmp/234559cf23adb7a1c4581247f438d92e.browserify:160:57)

Confirmed

No idea how we get from there ^ to the needed fix

This is what I get for not paying better attention to the travis builds in PRs.

Issue Analytics

State:
Created 7 years ago
Comments:9 (9 by maintainers)

Top GitHub Comments

1reaction

lathonezcommented, Sep 8, 2016

https://travis-ci.org/lathonez/clicker/builds/158281180

So what the needed fix did was to bypass the failing tests by causing karma to exit with a zero status on failure.

We can see from the above test during the PR that the tests were actually still failing.

At least that all makes sense now.

0reactions

lathonezcommented, Oct 30, 2016

no longer an issue

Top Results From Across the Web

ND build failure due to "Canceled (Exit code 143 " : TW-62186

The cloud profile agent Terminate instance idle time is set to 20 minutes. The server logs (Teamcity/logs/teamcity-server.log) show the agent is unregistered ...

Jenkins exit code 143 - due to Unexpected termination of the ...

Hello, I have a long running build that never runs to completion on the slave computer, it gets "Maven JVM terminated unexpectedly with...

Container killed with Exit Code is 143, not restarting

Exit Code 143 happens due to multiple reasons and one of them is related to Memory/GC issues. Your default Mapper/reducer memory setting may ......

ubuntu-latest: jobs fail with error code 143 #6680 - GitHub

Description We recently started seeing a high rate of failure in runs of a job that run go race on Linux runners (ubuntu-latest)....

When I run this code it return that "exit status 143" in java

Exit code 143 corresponds to SIGTERM, which is the signal sent by default when you run kill . Did you or the OS...