Doing development on the test slaves is a pain because they are so old. They are also not very representative of what are users are running.
We won't tackle this in the existing automation. This will be easier once we've switched over to Task Cluster.
It looks like we have a 16.04 test image now and are starting to transition tests over to it. See for example bug 1281179.
AFAIK there are now no 32-bit Linux tests running and so this is covered by bug 1290183.
Huh? There most certainly are Linux32 tests running. There are no Linux32 tests running on Taskcluster, yet, both because the people doing the moving hope that Linux32 will die before they have to move it and because they've stalled out trying to move Linux64 opt/PGO, but it's not currently the case that we've dropped Linux32 testing.
Thanks for correcting me, Phil, and for the helpful info. I must have looked at treeherder at the wrong time, and/or not looked hard enough.
So we still want to use 14.04 and not 16.04 (bug 1281179 and dependencies) which is already in place in Taskcluster for a couple of test suites on Linux64? I think it should be way lesser work to take the docker configs and adapt those for 32bit by keeping all the necessary modules our suites need. Joel should be able to tell more about it.
we really should plan on 16.04 if possible. There is work being done in bug 1287099 to get existing 12.04 tests running inside a docker image- then we can mirror the 16.04 image creation from 64 bit to 32 bit and repeat the greening up process.
16.04 is better than 14.04, yes.
Wontfix? Hasn't this been done already successfully for both Linux 32 and 64 TC workers? Or do I miss something?
this is specifically for the linux-ix (hardware) machines we have in the datacenter. They only run Talos and on the new hardware that we are currently testing and will get the first batch next month, that will have Ubuntu 16.04