Skip to content

CircleCI with Ubuntu 14.04, 2x parallelism and WebGL jasmine tests #1455

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
Mar 9, 2017
Merged

CircleCI with Ubuntu 14.04, 2x parallelism and WebGL jasmine tests #1455

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
0e3c61f
merge karma ciconf with (regular) conf
etpinard Mar 9, 2017
aa1aaef
comment & lint in karma conf
etpinard Mar 9, 2017
62d33b9
rm hasWebGLSupport early return in jasmine specs
etpinard Mar 9, 2017
100b993
rm unnecessary quotes in yml
etpinard Mar 9, 2017
14621e1
revamp circle.yml for ubuntu 14.04 with 2x parallel containers !!!
etpinard Mar 9, 2017
b42f021
use `karma-jasmine-spec-tags` to skip a few test on CI
etpinard Mar 9, 2017
8d7171f
add karma-verbose-reporter in dev deps
etpinard Mar 9, 2017
b86bf06
add `karma-spec-reporter` to log info about skipped specs
etpinard Mar 9, 2017
631533d
tweak precision to make tests pass on CI w/ Chrome 54
etpinard Mar 9, 2017
dbc6ca1
lock uglify-js to 2.7.x
etpinard Mar 9, 2017
e52f020
add no_citest script
etpinard Mar 9, 2017
33ae963
use (plain) npm run test-jasmine on CI
etpinard Mar 9, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 9 additions & 14 deletions circle.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,21 +12,16 @@ machine:
- docker

dependencies:
pre:
- eval $(node tasks/docker.js pull)
post:
- eval $(node tasks/docker.js run)
- npm run cibuild
override:
- npm install && npm dedupe && npm prune && npm install
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This thing here is (a lot) more predictable than simply npm install

cc @bpostlethwaite @scjody

- npm ls || true
- npm run docker -- pull
- npm run pretest
- eval $(node tasks/docker.js setup)
- npm prune && npm ls
- npm run docker -- run
- npm run cibuild
- npm run docker -- setup
Copy link
Contributor Author

@etpinard etpinard Mar 9, 2017 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Notice the docker commands are split between other commands. This is reduce the risk of race conditions.


test:
override:
- npm run test-image
- npm run test-image-gl2d
- npm run test-export
- npm run citest-jasmine
- npm run test-bundle
- npm run test-syntax
- eslint .
- ./tasks/ci_test.sh:
parallel: true
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More info on https://circleci.com/docs/1.0/parallel-manual-setup/#simple-example

4 changes: 2 additions & 2 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,8 @@
"build": "npm run preprocess && npm run bundle && npm run header && npm run stats",
"cibuild": "npm run preprocess && node tasks/cibundle.js",
"watch": "node tasks/watch.js",
"lint": "eslint --version && eslint . || true",
"lint-fix": "eslint . --fix",
"lint": "eslint --version && eslint .",
"lint-fix": "eslint . --fix || true",
"docker": "node tasks/docker.js",
"pretest": "node tasks/pretest.js",
"test-jasmine": "karma start test/jasmine/karma.conf.js",
Expand Down
22 changes: 22 additions & 0 deletions tasks/ci_test.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
#!/bin/bash

EXIT_STATE=0

case $CIRCLE_NODE_INDEX in

0)
npm run test-image || EXIT_STATE=$?
npm run test-image-gl2d || EXIT_STATE=$?
npm run test-export || EXIT_STATE=$?
npm run test-syntax || EXIT_STATE=$?
npm run lint || EXIT_STATE=$?
exit $EXIT_STATE
Copy link
Contributor Author

@etpinard etpinard Mar 9, 2017 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important: I chose this || EXIT_STATE=$? pattern over #!/bin/bash -e because I wanted all tests commands to run even if one of them fails. Note that $? is the exit code of the previously command. Stuff to the right of || is only executed if in the command to the left exits with a non-zero code.

Does anyone know a better way to do this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. Bash scripting is always a bit weird.

;;

1)
npm run citest-jasmine || EXIT_STATE=$?
npm run test-bundle || EXIT_STATE=$?
exit $EXIT_STATE
;;

esac
11 changes: 2 additions & 9 deletions tasks/docker.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,12 +46,5 @@ switch(arg) {
break;
}

// Log command string on CircleCI, to then `eval` them,
// which appears to be more reliable then calling `child_process.exec()`
if(isCI) {
console.log(cmd);
}
else {
console.log(msg);
common.execCmd(cmd, cb, errorCb);
}
console.log(msg);
common.execCmd(cmd, cb, errorCb);
4 changes: 3 additions & 1 deletion tasks/test_export.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,4 +14,6 @@ var cmd = containerCommands.getRunCmd(
);

console.log(msg);
common.execCmd(cmd);
common.execCmd(containerCommands.ping, function() {
common.execCmd(cmd);
});
4 changes: 3 additions & 1 deletion tasks/test_image.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,4 +14,6 @@ var cmd = containerCommands.getRunCmd(
);

console.log(msg);
common.execCmd(cmd);
common.execCmd(containerCommands.ping, function() {
common.execCmd(cmd);
});
2 changes: 0 additions & 2 deletions tasks/util/container_commands.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,6 @@ containerCommands.setup = [
containerCommands.injectEnv,
containerCommands.restart,
'sleep 1',
containerCommands.ping,
'echo '
].join(' && ');

containerCommands.dockerRun = [
Expand Down