Skip to content
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.

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

Incorrect labels for tests when running in parallel mode #123

Open
AC-TimRourke opened this issue Dec 6, 2017 · 2 comments
Open

Incorrect labels for tests when running in parallel mode #123

AC-TimRourke opened this issue Dec 6, 2017 · 2 comments

Comments

@AC-TimRourke
Copy link

I am seeing incorrect labels on my tests when I run them in parallel mode with randomization on. I run my tests using this command:

ember exam --random=$CIRCLE_SHA1 --split=4 --partition=n

...where n is the partition I want to run in a given CircleCI 2.0 container. Note that $CIRCLE_SHA1 is the git sha for the commit - seemed like a reasonable choice for a randomization seed.

In any event, the effect I am seeing is that the log output that appears in CircleCI doesn't match the actual tests I'm running. Whereas the CircleCI output looks something like this:

not ok 139 Chrome 60.0 - Exam Partition 1 - JSHint | components/cool-component/component.js: it should do the thing right

...the actual test that matches the string should do the thing right lives under something like:

Acceptance | components/other-thing-entirely/sub-thing/component.js

Can you think of a reason this might be happening? Naturally it makes it a bit difficult to interpret what CircleCI is telling me, as the failing test, from what I can tell, is not a JSHint error, but the misdirection makes me less confident that I can find the right test by the label.

Thanks!

@AC-TimRourke
Copy link
Author

Upon closer inspection, I see many many examples of output in my CircleCI console that reuse that same erroneous label, components/cool-component/component.js. What would cause this? Any idea as to a solution?

@AC-TimRourke
Copy link
Author

AC-TimRourke commented Dec 7, 2017

It looks like this issue might have been caused by the randomization feature. Turning off randomization eliminated the symptom.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant