Receiving the following test failures:
14:07:53 1 failing 14:07:53 14:07:53 1) Categories I can view categories: 14:07:53 element (".category-button") still not existing after 10000ms 14:07:53 running chrome 14:07:53 Error: element (".category-button") still not existing after 10000ms 14:07:53 at elements(".category-button") - isExisting.js:46:17 14:07:53 at isExisting(".category-button") - waitForExist.js:67:22 14:07:53 14:07:53 14:07:53 npm ERR! code ELIFECYCLE 14:07:53 npm ERR! errno 1 14:07:53 npm ERR! @ selenium-test: `wdio ./tests/selenium/wdio.conf.js` 14:07:53 npm ERR! Exit status 1 14:07:53 npm ERR! 14:07:53 npm ERR! Failed at the @ selenium-test script. 14:07:53 npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 14:07:53 14:07:53 npm ERR! A complete log of this run can be found in: 14:07:53 npm ERR! /cache/npm/_logs/2019-08-09T19_07_53_384Z-debug.log 14:07:53 INFO:backend.ChromeWebDriver:Terminating ChromeWebDriver 14:07:53 INFO:backend.Xvfb:Terminating Xvfb 14:07:53 INFO:backend.DevWebServer:Terminating DevWebServer
and:
14:03:48 ✖ 1 test failed 14:03:48 14:03:48 FAILED TESTS: 14:03:48 ve.ce.Surface 14:03:48 ✖ onCopy 14:03:48 HeadlessChrome 73.0.3683 (Linux 0.0.0) 14:03:48 Copy list item: text 14:03:48 Expected: "g 14:03:48 14:03:48 " 14:03:48 Actual: "g" 14:03:48 at testRunner <...> at Object.<anonymous> <...> 14:03:48 at runTest (node_modules/qunit/qunit/qunit.js:1478:30) 14:03:48 at Test.run (node_modules/qunit/qunit/qunit.js:1464:6) 14:03:48 at node_modules/qunit/qunit/qunit.js:1670:12 14:03:48 at Object.advance (node_modules/qunit/qunit/qunit.js:1116:26)
Noticed for release-quibble-composer-mysql-hhvm-docker (example 1, example 2) when working with a completely unrelated security backport for REL1_31, REL1_32 and REL1_33. I manually merged these since the patch for master tested fine (and the patch was one line of unrelated code for an entirely separate extension.)
Dummy changes to test with: