b2g_ubuntu64_vm mozilla-inbound opt test gaia-ui-test-accessibility https://treeherder.mozilla.org/ui/logviewer.html#?job_id=4318630&repo=mozilla-inbound 04:26:58 ERROR - TEST-UNEXPECTED-ERROR | test_a11y_calendar_month_view_select_day.py TestCalendarMonthViewSelectDayAccessibility.test_a11y_calen
Yura, can you look at this please?
At least, I hope it's only permaorange on the *first* of the month.
(In reply to Phil Ringnalda (:philor) from comment #45) > At least, I hope it's only permaorange on the *first* of the month. Possibly.. let me test that theory.
It does seem related to the date, but you have to go all the way forward to the 7th of December before it will start to pass. I have to defer to yzen for a solution though.
Despite having shown entirely too much tolerance for this test being permaorange all day Saturday after Saturday... a *week*? I've hidden gaia-ui-test-accessibility on every trunk tree, feel free to ping me (or any other sheriff, if you can find them) to unhide it when this test is either fixed or disabled and that's merged around.
Created attachment 8531145 [details] [review] Github pull request. Turns out the .present day selector is not unique and needs to be scoped to .active.month
Comment on attachment 8531145 [details] [review] Github pull request. I will take this review
Comment on attachment 8531145 [details] [review] Github pull request. merged in https://github.com/mozilla-b2g/gaia/commit/28ab77cfc9144ca7f3523116b796a91aee762765
Phil this should be fixed now can we unhide the test run
Unfortunately, although things are fixed for you when they land in github, for releng automation they are not. Five minutes after that comment, "B2G Bumper Bot" noticed that you had pushed to github, and pushed a commit to https://hg.mozilla.org/integration/b2g-inbound/ saying to run automation with that new version of gaia. 61 and 78 minutes later, the two builds had finished and the two test suites were successful. Then comes the wait for someone to merge that hg commit to mozilla-central, and from mozilla-central to the other trunk trees, and given that there's a noworkweek going on, none of the paid sheriffs did that today, so while it was true that it was fixed on one tree an hour or so after your comment, it's still not yet true that it's fixed anywhere else.