Skip to content
This repository has been archived by the owner on Nov 3, 2021. It is now read-only.

Bug 972160 - Run specific marionette tests for multiple times on Travis. #16244

Merged
merged 1 commit into from Feb 17, 2014

Conversation

evanxd
Copy link
Contributor

@evanxd evanxd commented Feb 13, 2014

You could check-pick the it and change any marionette test file to trigger 30 times running in CI_ACTION=marionette_js_check on Travis.

@@ -603,7 +603,6 @@ define run-js-command
endef

define run-node-command
echo "run-node-command $1";
Copy link
Contributor

Choose a reason for hiding this comment

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

please keep this line.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Could I ask why we must keep this line?
If we keep this line, we could not get a "clear" return value of a node command.

For example, if we would like to store the return value of doing @$(call run-node-command, pull-request-marionette-test) in a variable in a bash script, we will get run-node-command pull-request-marionette-test path/to/a_test.js path/to/b_test.js.

It might be not good to reuse. How do you think?

@evanxd
Copy link
Contributor Author

evanxd commented Feb 15, 2014

Main commit: evanxd@acedca6

@@ -28,6 +29,7 @@ matrix:
allow_failures:
- env: CI_ACTION=unit-tests-in-b2g
- env: CI_ACTION=unit-tests-coverage
- env: CI_ACTION=marionette_js_check
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think we could let it in allow_failures area first.
Make sure this action is stable, then we could move to must pass area.
How do you think?

evanxd added a commit that referenced this pull request Feb 17, 2014
Bug 972160 - Run specific marionette tests for multiple times on Travis.
@evanxd evanxd merged commit 9ea16d7 into mozilla-b2g:master Feb 17, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants