Bug 139271 - css3/viewport-percentage-lengths tests are flakey on WK1 Mavericks
Summary: css3/viewport-percentage-lengths tests are flakey on WK1 Mavericks
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-04 15:20 PST by Dean Jackson
Modified: 2014-12-07 10:44 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dean Jackson 2014-12-04 15:20:10 PST
css3/viewport-percentage-lengths/viewport-percentage-lengths-anonymous-block.html
css3/viewport-percentage-lengths/viewport-percentage-lengths-percent-size-child.html
css3/viewport-percentage-lengths/viewport-percentage-lengths-relative-font-size.html
css3/viewport-percentage-lengths/viewport-percentage-lengths-resize.html

These are failing on WK1 Mavericks about 40% of the time.

e.g. http://webkit-test-results.appspot.com/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=css3%2Fviewport-percentage-lengths%2Fviewport-percentage-lengths-anonymous-block.html
Comment 1 Alexey Proskuryakov 2014-12-06 22:49:44 PST
Dean added expectations for these tests, but the syntax was not correct (it should be Failure, not Fail). Also, no expectations should ever be in platform/mac-mavericks/TestExpectations, it's just a wrong place for those. I think that these should be in platform/mac-wk1.

Strangely, this only happens on one of the two bots serving this queue - it always happens on s-bot-138, and never on s-bot-137. I tried rebooting s-bot-138, but that didn't help.
Comment 2 Alexey Proskuryakov 2014-12-06 22:57:28 PST
One difference between s-bot-137 and s-bot-138 is that the latter doesn't have a display dongle. I don't know if this would be the cause for something like this though.
Comment 3 Alexey Proskuryakov 2014-12-06 23:00:07 PST
I changed display preferences from "scaled" to "best for this display", let's see if that changes anything.
Comment 4 Alexey Proskuryakov 2014-12-07 00:28:59 PST
Looks like that helped!
Comment 5 Alexey Proskuryakov 2014-12-07 10:44:06 PST
I'll move things out of the wrong TestExpectations file.