On Thu, Jul 14, 2016 at 9:38 AM, Lars Schneider <larsxschneider@xxxxxxxxx> wrote: > > On 13 Jul 2016, at 22:43, Junio C Hamano <gitster@xxxxxxxxx> wrote: > >> Junio C Hamano <gitster@xxxxxxxxx> writes: >> >>> It is somewhat disturbing that nobody seems to be regularly building >>> on 32-bit platforms these days, which is the only reason I can think >>> of why this was never reported until it hit a maintenance track. >>> This should have been caught last week at f6a729f3 (Merge branch >>> 'jk/tzoffset-fix', 2016-07-06) when the topic hit 'master' at the >>> latest, and more preferrably it should have already been caught last >>> month at 08ec8c5e (Merge branch 'jk/tzoffset-fix' into next, >>> 2016-06-28). >>> >>> Those who care about 32-bit builds need to start building and >>> testing 'next' and 'master' regularly, or similar breakages are >>> bound to continue happening X-<. >>> >>> Volunteers? >> >> We might eventually see a volunteer or two but that hasn't happened >> yet, at least in the past few days. >> >> Does Travis CI testing have an option to run our tests on some >> 32-bit platforms? > > TravisCI does not support 32-bit platforms natively: > https://github.com/travis-ci/travis-ci/issues/986#issuecomment-124141683 > > However, there seems to be a way to enter a 32 bit Trusty chroot on > 64 bit Travis via Docker: > https://github.com/travis-ci/travis-ci/issues/5770 > > @Duy: > You mentioned that you compiled Git on Docker before ($gmane/297963). > What do you think the chroot approach? Could that work? Would that > be reliable? "Docker chroot" is a weird term because they are not the same. If you can launch a new docker process from travis-ci, I suppose you can use a docker image with multilib support, then just run 32-bit binaries and it should work (unless the host kernel is built to only support 64-bit). -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html