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

Reland "Port another set of sticky tests to JS rather than reftests" #9881

Merged
merged 1 commit into from Mar 7, 2018

Conversation

Projects
None yet
4 participants
@chromium-wpt-export-bot
Copy link
Collaborator

chromium-wpt-export-bot commented Mar 6, 2018

This is a reland of 913109149534a732bdb5461d0ba2759f5d2f50f4

Now that the WPT test infra has been pulled from upstream, the hope is
that changing tests from reftest to jsharness won't cause the bots to
fail horribly.

Original change's description:

Port another set of sticky tests to JS rather than reftests

Change-Id: Idf6dd882d2d50b1ec349f245d76717553ee266b3
Reviewed-on: https://chromium-review.googlesource.com/882002
Reviewed-by: Robert Flack flackr@chromium.org
Commit-Queue: Stephen McGruer smcgruer@chromium.org
Cr-Commit-Position: refs/heads/master@{#532966}

Bug: 699244
Change-Id: Ib8c16d08f1327765e0bd322a708452373db8581c
Reviewed-on: https://chromium-review.googlesource.com/951662
Commit-Queue: Stephen McGruer smcgruer@chromium.org
Reviewed-by: Robert Flack flackr@chromium.org
Cr-Commit-Position: refs/heads/master@{#541437}

@wpt-pr-bot
Copy link
Collaborator

wpt-pr-bot left a comment

Already reviewed downstream.

@w3c-bots

This comment has been minimized.

Copy link

w3c-bots commented Mar 6, 2018

Build PASSED

Started: 2018-03-07 15:34:57
Finished: 2018-03-07 15:43:42

View more information about this build on:

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-951662 branch from 9df1a5b to 7100df7 Mar 6, 2018

Reland "Port another set of sticky tests to JS rather than reftests"
This is a reland of 913109149534a732bdb5461d0ba2759f5d2f50f4

Now that the WPT test infra has been pulled from upstream, the hope is
that changing tests from reftest to jsharness won't cause the bots to
fail horribly.

Original change's description:
> Port another set of sticky tests to JS rather than reftests
>
> Change-Id: Idf6dd882d2d50b1ec349f245d76717553ee266b3
> Reviewed-on: https://chromium-review.googlesource.com/882002
> Reviewed-by: Robert Flack <flackr@chromium.org>
> Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#532966}

Bug: 699244
Change-Id: Ib8c16d08f1327765e0bd322a708452373db8581c
Reviewed-on: https://chromium-review.googlesource.com/951662
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541437}

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-951662 branch from 7100df7 to dbf7922 Mar 7, 2018

@chromium-wpt-export-bot chromium-wpt-export-bot merged commit 0070589 into master Mar 7, 2018

1 check passed

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

@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-951662 branch Mar 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.