Add 32-bit environments

[staticfloat]

Hello! It appears that Travis has recently (relatively speaking) upgraded to 64-bit OS and CPU. This is great, but it also is breaking some of our software. We can fix it, and get everything working on 64-bit, but I wanted to check to see if it is possible to:

• Restrict a build to run on 32-bit or 64-bit only
• Run on both, a la via the environment block

Thank you!

(Edited by @henrikhodne on 2013-07-16 to clarify title)

[joshk]

Hi @staticfloat

We are sorry for the lack of notice, we have some news planned for this week to make it official.

I am looking at providing some 32bit vms, and a way to select 64 or 32 bit. To select both (matrix build) we will need to feature flip repos.

I will keep this issue open so I can update it when 32bit VMs are ready.

Thanks

Josh

[staticfloat]

Great, thanks joshk!

[wez]

any news on this? I can't find anything in the docs about it

[roidrage]

@wez sorry, no news yet.

[wez]

also: this page says the vms are 32-bit http://about.travis-ci.org/docs/user/languages/c/ ;-)

[dergachev]

At the moment, all the vagrant boxes on files.travis-ci.org are still 32-bit. (I personally just verified this for travis-ruby.box and travis-php.box).

I tried to work-around this by building my own box via https://github.com/travis-ci/travis-boxes but got stuck because it seemingly requires vagrant 1.0.2 and Virtualbox 4.0 or 4.1, which at the moment I'm not able to downgrade to.

Anyone have ideas on how to easily get a 64 bit travis base box?

[joshk]

Sorry but we are currently not maintaining the Vagrant boxes at the moment. That said, I am interested in creating new ones for download, or EC2 AMIs for easy spin up, but haven't had time to attack this yet.

Travis Boxes is actually old and deprecated. The template definitions are in travis-ci/travis-images now, but that doesn't really solve your issue, that is just an FYI.

If you need a VM for debug purposes, please email support and we can spin a VM which you can ssh into for you. Other than that, I am sorry but we don't have anything readily available at the moment.

[dergachev]

OK I'll make do with debugging on the old boxes for now, and keep checking on the status of travis-ci/travis-images to see if anything useful pops up.

Cheers,

Alex Dergachev
Evolving Web, co-founder and lead developer
http://evolvingweb.ca :: web design & development
phone 514.844.4930 :: fax 514.807.7499
114-300 rue du Saint-Sacrement, Montréal, QC
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

On Friday, 28 June, 2013 at 4:25 PM, Josh Kalderimis wrote:

Travis Boxes is actually old and deprecated. The template definitions are in travis-ci/travis-images now, but that doesn't really solve your issue, that is just an FYI.

[alanjds]

Any news on 32 bit builds?

[mloskot]

@alanjds +1

[calid]

Any update on this? zeromq/perlzmq#1 could have been caught and prevented if there was an easy way to test 32bit Perls.

[roidrage]

Sorry, no news yet on this front.

[jtratner]

+1 for 32bit Python here.

[jfoote]

Just in case this might help someone: if you're in a pinch you can add basic 32-bit runtime support by installing gcc-multilib via apt-get or similar.

[iedemam]

+1 for 32-bit c, c++

[McNetic]

I'm also in dire need (:-P) of a 32 bit test environment, but for php. In fact, as my small lib (https://github.com/McNetic/PHPZipStreamer) has a compatibility layer for php on 32 bit machines, I need my tests to run on both 32 bit and 64 bit virtual machines.

[BenMorel]

Same need for 32-bit PHP here, for WKB Geometry tests in brick/geo.
Is it still in the works?

[edgarsilva]

Same need for 32bit boxes to provide pre-compiled binaries.

[probonopd]

Same here, need 32bit x86

[roidrage]

Closing this issue for now, as we have no immediate plans to add this feature.

Should we add it to the roadmap eventually, we'll make sure to update this ticket.