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

Update mozrunner to 7.0.1 #10721

Merged
merged 1 commit into from May 1, 2018

Conversation

Projects
None yet
3 participants
@pyup-bot
Contributor

pyup-bot commented Apr 30, 2018

This PR updates mozrunner from 7.0.0 to 7.0.1.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

This change is Reviewable

@wpt-pr-bot wpt-pr-bot added the infra label Apr 30, 2018

@wpt-pr-bot wpt-pr-bot requested review from gsnedders and jgraham Apr 30, 2018

@jgraham

jgraham approved these changes May 1, 2018

@jgraham jgraham merged commit 8b9f853 into master May 1, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@gsnedders gsnedders deleted the pyup-update-mozrunner-7.0.0-to-7.0.1 branch May 1, 2018

@jgraham jgraham restored the pyup-update-mozrunner-7.0.0-to-7.0.1 branch May 1, 2018

@jgraham jgraham deleted the pyup-update-mozrunner-7.0.0-to-7.0.1 branch May 1, 2018

jugglinmike added a commit to bocoup/wpt that referenced this pull request May 1, 2018

[wptrunner] Re-enable return code
In a previous commit [1] the WPT CLI was modified to ignore the return
value of the `wptrunner.start` method. Although this behavior is
convenient in cases where there is no expectation data, it obscures
errors that are relevant in any context.

Specifically, the `start` method returns a non-zero value when no tests
are run, and this is a reliable indicator of an erroneous configuration.
Because the `wpt run` command is used to validate the infrastructure of
the web-platform-tests project, ignoring this case allows
mis-configurations to go unnoticed [2].

Re-enable observance of the value returned by `wptrunner.start` and
update the code generated for the TaskCluster service to ignore this
value.

[1] 5a1b036
[2] web-platform-tests#10721

jugglinmike added a commit to bocoup/wpt that referenced this pull request May 1, 2018

[wptrunner] Re-enable return code
In a previous commit [1] the WPT CLI was modified to ignore the return
value of the `wptrunner.start` method. Although this behavior is
convenient in cases where there is no expectation data, it obscures
errors that are relevant in any context.

Specifically, the `start` method returns a non-zero value when no tests
are run, but this is a reliable indicator of an erroneous configuration.
Because the `wpt run` command is used to validate the infrastructure of
the web-platform-tests project, ignoring this case allows
mis-configurations to go unnoticed [2].

Re-enable observance of the value returned by `wptrunner.start` and
update the code generated for the TaskCluster service to ignore this
value.

[1] 5a1b036
[2] web-platform-tests#10721

jugglinmike added a commit to bocoup/wpt that referenced this pull request May 2, 2018

[wptrunner] Re-enable return code
In a previous commit [1] the WPT CLI was modified to ignore the return
value of the `wptrunner.start` method. Although this behavior is
convenient in cases where there is no expectation data, it obscures
errors that are relevant in any context.

Specifically, the `start` method returns a non-zero value when no tests
are run, but this is a reliable indicator of an erroneous configuration.
Because the `wpt run` command is used to validate the infrastructure of
the web-platform-tests project, ignoring this case allows
mis-configurations to go unnoticed [2].

Re-enable observance of the value returned by `wptrunner.start` and
update the code generated for the TaskCluster service to ignore this
value.

[1] 5a1b036
[2] web-platform-tests#10721

jugglinmike added a commit to bocoup/wpt that referenced this pull request May 5, 2018

[wptrunner] Allow test failures to be ignored
In a previous commit [1] the WPT CLI was modified to unconditionally
ignore the return value of the `wptrunner.start` method. Although this
behavior is convenient in cases where there is no expectation data, it
obscures errors that are relevant in any context.

Specifically, the `start` method returns a non-zero value when no tests
are run, but this is a reliable indicator of an erroneous configuration.
Because the `wpt run` command is used to validate the infrastructure of
the web-platform-tests project, ignoring this case allows faulty
configurations to go unnoticed [2].

Implement a new CLI option named `--no-fail-on-unexpected` to allow
users to allow test failure while still being alerted to errors that
cause zero tests to be executed. Update the script designed for the
TaskCluster service to enable this option.

[1] 5a1b036
[2] web-platform-tests#10721

jugglinmike added a commit to bocoup/wpt that referenced this pull request May 5, 2018

[wptrunner] Allow test failures to be ignored
In a previous commit [1] the WPT CLI was modified to unconditionally
ignore the return value of the `wptrunner.start` method. Although this
behavior is convenient in cases where there is no expectation data, it
obscures errors that are relevant in any context.

Specifically, the `start` method returns a non-zero value when no tests
are run, but this is a reliable indicator of an erroneous configuration.
Because the `wpt run` command is used to validate the infrastructure of
the web-platform-tests project, ignoring this case allows faulty
configurations to go unnoticed [2].

Implement a new CLI option named `--no-fail-on-unexpected` to allow
users to allow test failure while still being alerted to errors that
cause zero tests to be executed. Update the script designed for the
TaskCluster service to enable this option.

[1] 5a1b036
[2] web-platform-tests#10721

jugglinmike added a commit to bocoup/wpt that referenced this pull request May 9, 2018

[wptrunner] Allow test failures to be ignored
In a previous commit [1] the WPT CLI was modified to unconditionally
ignore the return value of the `wptrunner.start` method. Although this
behavior is convenient in cases where there is no expectation data, it
obscures errors that are relevant in any context.

Specifically, the `start` method returns a non-zero value when no tests
are run, but this is a reliable indicator of an erroneous configuration.
Because the `wpt run` command is used to validate the infrastructure of
the web-platform-tests project, ignoring this case allows faulty
configurations to go unnoticed [2].

Implement a new CLI option named `--no-fail-on-unexpected` to allow
users to allow test failure while still being alerted to errors that
cause zero tests to be executed. Update the script designed for the
TaskCluster service to enable this option.

[1] 5a1b036
[2] web-platform-tests#10721

jgraham added a commit that referenced this pull request May 9, 2018

[wptrunner] Allow test failures to be ignored
In a previous commit [1] the WPT CLI was modified to unconditionally
ignore the return value of the `wptrunner.start` method. Although this
behavior is convenient in cases where there is no expectation data, it
obscures errors that are relevant in any context.

Specifically, the `start` method returns a non-zero value when no tests
are run, but this is a reliable indicator of an erroneous configuration.
Because the `wpt run` command is used to validate the infrastructure of
the web-platform-tests project, ignoring this case allows faulty
configurations to go unnoticed [2].

Implement a new CLI option named `--no-fail-on-unexpected` to allow
users to allow test failure while still being alerted to errors that
cause zero tests to be executed. Update the script designed for the
TaskCluster service to enable this option.

[1] 5a1b036
[2] #10721

moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this pull request May 18, 2018

Bug 1458341 [wpt PR 10742] - [wptrunner] Re-enable return code, a=tes…
…tonly

Automatic update from web-platform-tests[infra] Correct integration test

By default, "single-page tests" must include an explicit call to the
global `done` function [1]. Insert this invocation to signal completion
and avoid a test timeout when the test's expectation is satisfied.

[1] http://web-platform-tests.org/writing-tests/testharness-api.html

--
[ci] Correct syntax in build script

--
[wptrunner] Allow test failures to be ignored

In a previous commit [1] the WPT CLI was modified to unconditionally
ignore the return value of the `wptrunner.start` method. Although this
behavior is convenient in cases where there is no expectation data, it
obscures errors that are relevant in any context.

Specifically, the `start` method returns a non-zero value when no tests
are run, but this is a reliable indicator of an erroneous configuration.
Because the `wpt run` command is used to validate the infrastructure of
the web-platform-tests project, ignoring this case allows faulty
configurations to go unnoticed [2].

Implement a new CLI option named `--no-fail-on-unexpected` to allow
users to allow test failure while still being alerted to errors that
cause zero tests to be executed. Update the script designed for the
TaskCluster service to enable this option.

[1] 5a1b0365267b540c7f4feac3e0a85e9146997fcd
[2] web-platform-tests/wpt#10721

--

wpt-commits: 28e519569775b44a600ce09bd50320e0d9679db1, 8412dad42a7ca4c963aaa6dba771772dbe8d8c5c, f7a0aa07816a2f5a9af6c569f61a5d877baa3a08
wpt-pr: 10742

sole pushed a commit to sole/gecko that referenced this pull request May 21, 2018

Bug 1458341 [wpt PR 10742] - [wptrunner] Re-enable return code, a=tes…
…tonly

Automatic update from web-platform-tests[infra] Correct integration test

By default, "single-page tests" must include an explicit call to the
global `done` function [1]. Insert this invocation to signal completion
and avoid a test timeout when the test's expectation is satisfied.

[1] http://web-platform-tests.org/writing-tests/testharness-api.html

--
[ci] Correct syntax in build script

--
[wptrunner] Allow test failures to be ignored

In a previous commit [1] the WPT CLI was modified to unconditionally
ignore the return value of the `wptrunner.start` method. Although this
behavior is convenient in cases where there is no expectation data, it
obscures errors that are relevant in any context.

Specifically, the `start` method returns a non-zero value when no tests
are run, but this is a reliable indicator of an erroneous configuration.
Because the `wpt run` command is used to validate the infrastructure of
the web-platform-tests project, ignoring this case allows faulty
configurations to go unnoticed [2].

Implement a new CLI option named `--no-fail-on-unexpected` to allow
users to allow test failure while still being alerted to errors that
cause zero tests to be executed. Update the script designed for the
TaskCluster service to enable this option.

[1] 5a1b0365267b540c7f4feac3e0a85e9146997fcd
[2] web-platform-tests/wpt#10721

--

wpt-commits: 28e519569775b44a600ce09bd50320e0d9679db1, 8412dad42a7ca4c963aaa6dba771772dbe8d8c5c, f7a0aa07816a2f5a9af6c569f61a5d877baa3a08
wpt-pr: 10742
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment