Skip to content

Noissue - enable CI for shared runners

This patch adds CI support for shared runners (so that nobody needs to setup their own specific runners)

However, running CI on shared runners yields the following during the browser tests:

$ npm run test-only -- -g gecko

> adblockpluschrome@ test-only /builds/triluc/abpchrome_sharedrunners
> mocha "-g" "gecko"



  gecko
Downloading Firefox...
    ✓ test pages (77836ms)
    1) subscribe link
    ✓ qunit (1718ms)


  2 passing (2m)
  1 failing

  1) gecko
       subscribe link:

      AssertionError [ERR_ASSERTION]: title matches
      + expected - actual

      +ABP Testcase Subscription
      
      at Promise.all.then (test/wrappers/pages.js:229:18)
      at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:189:7)



npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! adblockpluschrome@ test-only: `mocha "-g" "gecko"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the adblockpluschrome@ test-only 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!     /root/.npm/_logs/2018-10-25T10_49_01_928Z-debug.log
ERROR: Job failed: exit code 1

@snoack Any idea, where this is coming from? (FWIW: raising the timeout in wrappers/pages.js to 5000 didn't solve anything)

Edited by Tristan Lucas

Merge request reports