[opensource-dev] Remaining build issues for 64bit linux standalone out-of-source (without unit tests)

[WolfPup Lowenhar]

For some of us disabling of the tests means less time actually compiling the
code. Especially if the system the code is being compiled on is an older
system. As an example below is my system specs taken directly from the
current dev build I did over the weekend.

 

CPU: Intel(R) Pentium(R) D CPU 2.80GHz (2800.13 MHz)

Memory: 2046 MB

OS Version: Microsoft Windows 7 32-bit  (Build 7600)

Graphics Card Vendor: NVIDIA Corporation

Graphics Card: GeForce 8500 GT/PCI/SSE2

 

On the above system if I build and run everything from a clean checkout it
will take ~3hrs to do a complete build all the way to packaging. Now if I
turn off the building and running of those test but compile time is cut in
half which means more time for me to test any changes I have made in the
code. I know there are some out there that talk about doing incremental
builds when your testing something and that might be ok for if you make a
minor change the same day you have done a build but if you're making changes
over multiple days it is best to me for the date of the build in about
SecdondLife to be set to the new date each time so you can keep track of
those changes.

 

From: opensource-dev-bounces at lists.secondlife.com
[mailto:opensource-dev-bounces at lists.secondlife.com] On Behalf Of Oz Linden
(Scott Lawrence)
Sent: Monday, October 11, 2010 9:05 AM
To: Boroondas Gupte
Cc: Second Life Open Source Developer Mailing List
Subject: Re: [opensource-dev] Remaining build issues for 64bit linux
standalone out-of-source (without unit tests)

 


VWR-23296 <https://jira.secondlife.com/browse/VWR-23296> : missing LL_TEST
conditions (i.e. SNOW-651 <https://jira.secondlife.com/browse/SNOW-651>  +
SNOW-654 <https://jira.secondlife.com/browse/SNOW-654> )

*	The ability to turn off building and executing of all unit tests is
needed to work around other issues (which we'll have to fix later)
*	Fixed at http://bitbucket.org/boroondas/vwr-23296
*	Should be easy to review (but note there are several changesets)


I'm hesitant to move this to the main development branch, because I'd rather
not make it easy to not do tests.  If they're broken, we should instead
invest in fixing them (or the means of running them).

I'd like to hear more discussion on this... specifically, what are the
problems that are causeing the tests not to be useful?

  _____  

No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1136 / Virus Database: 422/3190 - Release Date: 10/11/10

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/opensource-dev/attachments/20101011/677e5c0e/attachment.htm