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.

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

Jump to bottom

split CI matrix on browser #2592

Closed
boneskull opened this issue Nov 23, 2016 · 3 comments
Closed

split CI matrix on browser #2592

boneskull opened this issue Nov 23, 2016 · 3 comments
Labels
status: wontfix typically a feature which won't be added, or a "bug" which is actually intended behavior

Comments

@boneskull
Copy link
Contributor

Currently we're running all browsers in a single build; let's split that up.
@boneskull boneskull added status: accepting prs Mocha can use your help with this one! qa labels Nov 23, 2016
boneskull added a commit that referenced this issue Nov 24, 2016
@boneskull
split build matrix; add more browsers; closes #2592
9129740
boneskull added a commit to boneskull/mocha that referenced this issue Nov 24, 2016
@boneskull
split build matrix; add more browsers; closes mochajs#2592
b9358e7
boneskull added a commit that referenced this issue Nov 24, 2016
@boneskull
split build matrix; add more browsers; closes #2592
ad62d76
boneskull added a commit that referenced this issue Nov 24, 2016
@boneskull
split build matrix; add more browsers; closes #2592
a261fb6
boneskull added a commit that referenced this issue Nov 25, 2016
@boneskull
split build matrix; add more browsers; closes #2592
d46224f
boneskull added a commit that referenced this issue Nov 26, 2016
@boneskull
split build matrix; add more browsers; closes #2592
7449319
boneskull added a commit that referenced this issue Nov 26, 2016
@boneskull
split build matrix; add more browsers; closes #2592
b724c28
@boneskull boneskull removed the status: accepting prs Mocha can use your help with this one! label Nov 27, 2016
@boneskull
Copy link
Contributor Author

I think the Sauce failures (#2478) are due to opening a Sauce Connect tunnel, running tests, closing the tunnel, then immediately thereafter re-opening the tunnel with a new Karma run. The test-browser target launches Karma four (4) times.

To get around this, we'll need to manually open the Sauce Connect tunnel before running Karma, then tell Karma not to open it, and use the existing tunnel.

@boneskull
Copy link
Contributor Author

Example job: https://travis-ci.org/mochajs/mocha/jobs/179153053

catdad added a commit to catdad/mocha that referenced this issue Jul 14, 2017
@catdad
adding a "retryable fail" event for a test that fails but can be retried
4586186 
Addresses issue mochajs#2592 by allowing reporters to take action on tests that have failed but can be retried
@catdad catdad mentioned this issue Jul 14, 2017
Closed
boneskull pushed a commit that referenced this issue Jun 6, 2018
@catdad @boneskull
adding a "retryable fail" event for a test that fails but can be retried
db0ace5 
Addresses issue #2592 by allowing reporters to take action on tests that have failed but can be retried
@boneskull boneskull mentioned this issue Jun 6, 2018
Merged
boneskull pushed a commit that referenced this issue Dec 10, 2018
@catdad @boneskull
adding a "retryable fail" event for a test that fails but can be retried
852960a 
Addresses issue #2592 by allowing reporters to take action on tests that have failed but can be retried
@juergba juergba added the status: wontfix typically a feature which won't be added, or a "bug" which is actually intended behavior label Sep 28, 2021
@juergba
Copy link
Contributor

juergba commented Sep 28, 2021

This issue has been inactive for several years.

@juergba juergba closed this as completed Sep 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: wontfix typically a feature which won't be added, or a "bug" which is actually intended behavior
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@boneskull @juergba