The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/34c9270bee35347f281a02597564fd6668025a32

commit 34c9270bee35347f281a02597564fd6668025a32
Author: Philip Jägenstedt <foolip@chromium.org>
Date: Mon Sep 24 09:30:39 2018

Skip new cssom-view scrolling tests to unblock wpt import

TBR=fwang@igalia.com

Bug: 888443
Change-Id: Ifdb189face0391bf54c63477aedc7c1bb7f78a22
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/1240293
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593494}
[modify] https://crrev.com/34c9270bee35347f281a02597564fd6668025a32/third_party/WebKit/LayoutTests/TestExpectations

The importer is not longer blocked on this and the tests should be imported before long. fwang@, can you take a look at enabling them, if they should be?

What does it mean they have different failures on "try bots and CQ". Are they are flaky? Or they use different configurations?

It could be because of flakiness, I didn't check, what I observed was that the results that rebaseline-cl produced did not pass CQ.

The practical way forward here would be to try reverting https://chromium-review.googlesource.com/c/chromium/src/+/1240293 in a CL and use rebaseline-cl on that. Then see if the resulting patch passes CQ. It probably doesn't, and at that point it will be possible to see exactly what the differences are.

Note that I may have disabled slightly too many tests, some of them might actually have the same results consistently.