I have a full try run of windows 10 so far, it all ran in > a day with merely 1 machine. There is obviously more Graphics Work on our side, so not filing bugs for those ones yet, but this will track actionable work as it comes. https://treeherder.mozilla.org/#/jobs?repo=try&revision=d4b5af30bd85 Please do not push to try targeting windows 10 without a coordination with me, or follow on support to do so.
Touchpoint, progress has been made so far. Pushed a new full-run with https://treeherder.mozilla.org/#/jobs?repo=try&revision=55ecdb02f01a based on latest inbound merge from m-c ( https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=cb6c34882e41 ) That push had a red on w8 JIT debug which was fixed by a later commit (but JIT was passing on my last all-run) This run has the patches for Bug 1195499, Bug 1194763, and Bug 1196206 applied. I'll file new bugs (not already filed) based on the results of this run.
I tried running the plugin suite locally in the 64-bit build and received 55 failures. :/
oops, sorry, wrong bug.
I'm no longer tracking this unit of work. Once relops completes the work for getting windows 10 at a useable-on-try capacity we plan to have buildduty folks (currently softvision) drive this effort.
Assignee: bugspam.Callek → nobody
Not sure if this is still accurate since we moved to TC. In any case, at a second thought, I think this is out of Buildduty scope and goes under General Automation. Please move back if any Buildduty involment is needed further.
Component: Buildduty → General Automation
This bug was from 2015 and has been superseeded by the migration we've already done for talos tests to w10 and the taskcluster work that's ongoing.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.