COMPASS 443: Standardise mongodb-runner CI

[pzrq]

See also mongodb-js/connection-model#138

NOTE: npm run check && npm run test-unit passes for me locally on macOS, but the functional tests npm test still error with results:

177 passing (50s)
2 pending
10 failing

1. Compass #spectron when working with the application when working with collections when selecting a collection renders the sample collection in the title:
   Error: element (button[data-hook=start-button]) still not visible after 5000ms
   at elements("button[data-hook=start-button]") - isVisible.js:54:17
   at isVisible("button[data-hook=start-button]") - waitForVisible.js:37:22

2. Compass #spectron when working with the application when working with collections when selecting a collection renders the schema tab:
   Error: An element could not be located on the page using the given search parameters.
   at element("li#SCHEMA") - click.js:12:17
   at elementIdDisplayed("0.9192226665154364-7") - isVisible.js:71:55

3. Compass #spectron when working with the application when working with collections when selecting a collection when applying a filter the text in refine bar matches query:
   Error: Promise was rejected with the following reason: Error: An element could not be located on the page using the given search parameters ("input#refine_input").
   at elements("input#refine_input") - getValue.js:18:17
   at getValue("input#refine_input") - waitForValue.js:37:22

4. Compass #spectron when working with the application when working with collections when selecting a collection when applying a filter samples the matching documents:
   Error: element (div.sampling-message) still not visible after 15000ms
   at elements("div.sampling-message") - isVisible.js:54:17
   at isVisible("div.sampling-message") - waitForVisible.js:37:22

5. Compass #spectron when working with the application when working with collections when selecting a collection when applying a filter updates the schema view:
   Error: An element could not be located on the page using the given search parameters ("li.bubble code.selectable").
   at elements("li.bubble code.selectable") - getText.js:18:17
   at getText("li.bubble code.selectable") - compass-functional.test.js:120:16

6. Compass #spectron when working with the application when working with collections when selecting a collection when applying a filter filters out non-matches from the document list:
   Error: An element could not be located on the page using the given search parameters.
   at element("li#DOCUMENTS") - click.js:12:17
   at elementIdDisplayed("0.9192226665154364-7") - isVisible.js:71:55

7. Compass #spectron when working with the application when working with collections when selecting a collection when applying a filter includes documents that match the filter:
   Error: An element could not be located on the page using the given search parameters ("div.element-value-is-string").
   at elements("div.element-value-is-string") - getText.js:18:17
   at getText("div.element-value-is-string") - compass-functional.test.js:138:16

8. Compass #spectron when working with the application when working with collections when working in the documents tab when viewing documents renders the documents in the list:
   Error: An element could not be located on the page using the given search parameters.
   at element("li#DOCUMENTS") - click.js:12:17
   at elementIdDisplayed("0.9192226665154364-7") - isVisible.js:71:55

9. Compass #spectron when working with the application when working with collections when working in the explain tab when viewing the explain tab renders the stages:
   Error: An element could not be located on the page using the given search parameters.
   at element("li#EXPLAIN_PLAN") - click.js:12:17
   at elementIdDisplayed("0.9192226665154364-7") - isVisible.js:71:55

10. Compass #spectron when working with the application when working with collections when working in the indexes tab when viewing the indexes tab renders the indexes:
    Error: An element could not be located on the page using the given search parameters.
    at element("li#INDEXES") - click.js:12:17
    at elementIdDisplayed("0.9192226665154364-7") - isVisible.js:71:55

[pzrq]

Build hangs forever: travis-ci/travis-ci#317

The reason I'm less font of the pretest and posttest hooks for configuration is AFAICT we couldn't test multiple distinct topologies (i.e. standalone, replica set, cluster), something which considering the number of bugs on secondaries we've just fixed would be really nice to have.

[pzrq]

Having now force-pushed a few times and seeing results like:

  1 failing
  1) Compass #spectron when working with the application when working with collections when working in the indexes tab when viewing the indexes tab try empty create index:
     Error: An element could not be located on the page using the given search parameters (".modal-status-error-message").
      at elements(".modal-status-error-message") - getText.js:18:17
      at submit("0.7060162656529185-39") - submitForm.js:20:22

All considered, I suspect there's a race condition introduced here, but need more data from Travis to confirm statistically, and ideally without the sudo: required change.

[pzrq]

It's concerning that we depend on the cached Travis infrastructure for our builds to pass. Either way the try race condition seems to only be reproducible with sudo: required, so what's more likely to be going on is a semver accident somewhere like 2123fc4

I'll leave this here over Sydney's weekend in case anyone finds it useful and close it on Monday if we have bigger fish to fry to get 1.5 out the door.

[pzrq]

Example of build failing excluding changes on this branch:
https://travis-ci.com/10gen/compass/builds/35616231

EDIT: Via #631