Conversation
|
Re. failures with The failures with not ok 3 - pauses in next line of the script
---
found: |-
break in examples/break.js:1
> 1 const x = 10;
2 let name = 'World';
3 name = 'Robin';
debug>
pattern: 'break in examples/break.js:2'
at:
line: 31
column: 9
file: test/cli/break.test.js
function: cli.waitForInitialBreak.then.then.then.then
stack: |
cli.waitForInitialBreak.then.then.then.then (test/cli/break.test.js:31:9)
source: |
t.match(
... |
|
From #75 (comment)
@jkrems I could always leave 10.x out of this PR, which would allow a passing CI on 12 and 13 (which would be a better position than no CI at all). We could then add 10.x in a later PR if deemed necessary. |
Add a workflow to run tests with GitHub Actions.
|
Rebased on master and commented out 10.x. Thanks for setting this up, this is great! |
Add a workflow to run tests with GitHub Actions.
Based on the standard Node.js starter workflow with the following changes:
pull_requestevent so tests are run on pull requestsfail-fast: falseso that all versions of Node.js are tested (without this as soon as one job fails the rest are canceled)npm cireplaced withnpm installas this project doesn't have apackage-lock.jsonor shrinkwrap file committedTests seem very broken with
tap14 so I've downgraded totap12 where tests pass on Node.js 12.x and 13.x but there are still failures on 10.x (hence this being WIP). Any help with fixing those failures would be appreciated as I'm not that familiar withnode-inspect.