Comments (8)
I don't have much familiarity with Circle. The number of nodes available to run your tests is variable per-run?
If so, I would recommend parallelizing within a given node instead of across the variable number of nodes. It will give you more consistent results and make debugging easier (less environmental variables).
from ember-exam.
I'm not super familiar with it either, but this is my understanding.
You pay for containers, and all of your projects share these. If one is used it waits until another opens up. You can set it on a per repo(project) setting to use more if available. I only have 2 containers available, if a different project uses one (and is only provisioned one) then my ember project only has one available and this will happen (I think)
I found this blog post so hopefully someone else will run into this with circle who is more familiar
If so, I would recommend parallelizing within a given node instead of across the variable number of nodes. It will give you more consistent results and make debugging easier (less environmental variables).
How would I go about this?
from ember-exam.
After working with the author of that blog post we confirmed that it is indeed working (once I switched to 2 containers for my project) and it is splitting the tests up correctly. To check this open the Artifacts
tab in circle and click on the xml files to verify they are running different tests
However the issue still arises, I think if split does get passed 1, it should just run it as if it wasn't split rather than failing the tests
from ember-exam.
I think if split does get passed 1, it should just run it as if it wasn't split rather than failing the tests
I suppose I can relax this to just be a warning. The intent was to make sure developers know when they're actually splitting/reducing the number of tests being run, but an exception may be a bit too disruptive.
How would I go about this?
Use the --parallel
option. In general I recommend this over trying to use multiple node/boxes/processes as it is overall less resource intensive.
from ember-exam.
@Frozenfire92 we haven't had any issues using exam on Circle. Here's our circle.yml
:
general:
branches:
only:
- master
- /.*_ci$/
machine:
node:
version: 4.7.0
dependencies:
cache_directories:
- "/opt/circleci/nodejs/v4.7.0/lib/node_modules"
- "/opt/circleci/nodejs/v4.7.0/bin"
- "node_modules"
- "bower_components"
pre:
- type ember || npm -g install ember-cli
- type bower || npm -g install bower
override:
- npm install
- bower install
test:
override:
- mkdir -p $CIRCLE_TEST_REPORTS/ember:
parallel: true
- node_modules/ember-cli/bin/ember exam ci --split=$CIRCLE_NODE_TOTAL --partition=$((CIRCLE_NODE_INDEX+1)) --reporter xunit --silent > $CIRCLE_TEST_REPORTS/ember/junit$CIRCLE_NODE_INDEX.xml:
parallel: true
timeout: 1200
from ember-exam.
Ah you're saying the error message is unhelpful? I think it's fine, as you'd configure the circle.yml
per project, and you'd add containers per project anyway based on your Circle plan?
Basically in the case of single containers you'd just use ember test ci
anyway?
from ember-exam.
👍 to make this a warning, so that we can do e.g.
ember exam --parallel --split=$NUMBER_OF_PROCESSORS
without extra conditional logic
from ember-exam.
This has been changed in 0.6.2
.
from ember-exam.
Related Issues (20)
- Passing the `--load-balance` flag changes partitions HOT 3
- Halts when waiting for a browser to exit after TestLoader Failure HOT 1
- Cut a new release HOT 1
- Embroider Support HOT 1
- How can I determine the max num in `parallel=<num>` based on my CPU limitations? HOT 2
- What version of ember cli is required to run with load balancing? HOT 2
- Ember serve not running full tests
- Usage documentation and options are extremely confusing HOT 4
- 'ember exam --server' doesn't work with ember-cli 3.19.0 to 3.20.0 update HOT 5
- Magic Number of Parallel HOT 2
- The link to the documentation website is broken HOT 2
- Does not work properly with [email protected]
- Could not find module `qunit` imported from `(require)` HOT 4
- usage of the --path option (and other valid ember test options) needs clarification
- Update documentation about load balancing prerequisites HOT 1
- App won't build with ember-exam 6.1.0 and ember-mocha HOT 4
- Reported test count is different when running exam than when running test HOT 1
- Ember Auto Import v2 issue with test-support HOT 1
- Dependency Dashboard
- environment test not set when configuring polly without --environment=test
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ember-exam.