1458853 - [wpt-sync] Sync PR 10819 - [css-flex][spec-rec] Test for flex only alignment modes with writing modes (vertical-lr)

Status: RESOLVED INVALID

(Core :: CSS Parsing and Computation, enhancement, P4)

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Sync web-platform-tests PR 10819 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/w3c/web-platform-tests/pull/10819
Details from upstream follow.

Andela Developer <[e-mail]> wrote:
>  [css-flex][spec-rec] Test for flex only alignment modes with writing modes (vertical-lr)
>  
>  #### What does this PR do? 
>  These tests ensure that flex only alignment modes work as expected in different
>  writing modes. 
>  The tests use the writing-mode: vertical-lr with the flex alignment modes 
>  (justify-content and align-items)
>  
>  #### How should this be manually tested?
>  Pull the current branch
>  Follow the Readme.md to run the tests
>  *Testharness.js has been used to write the test cases*
>  
>  #### Screenshots (if appropriate)
>  <img width="1280" alt="screen shot 2018-05-03 at 12 37 53 pm" src="https://user-images.githubusercontent.com/26222856/39574476-4cab6842-4ecf-11e8-8401-0c80e3fa3da1.png">
>

Comment 1

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=09eeb4d94516873bdc830a940525b17ad2e19722

Comment 2

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Try push failed: decision task returned error

Comment 3

[Daniel Holbert [:dholbert]]

(In reply to Web Platform Test Sync Bot from comment #2)
> Try push failed: decision task returned error

It looks like the "Try push failed"/ "decision task returned error" thing here was probably for the dark blue "D" shown in the Try run (dark blue = auto-restarted).

The second instance of this build was green, so I think all is well.  So I suspect we're good to proceed here? Needinfoing jgraham to be sure this isn't blocked due to that bogus "failed" status or something.

Comment 4

[James Graham [:jgraham]]

Nope, and we just landed some changes to handle broken decision tasks better (by auto-retrying).