# Three questions about the Sage build farm

 1 I have some questions about the Sage "build farm" http://wiki.sagemath.org/devel/BuildFarm Would it be possible to include the build logs for the "good" builds. Even when my builds are successful, there are generally a lot of scary looking messages in them. It would be nice to be able to compare them to a build that one of the developers was satisfied with. How about putting the date/time at the very beginning and very end of each log -- so it's easy to get an idea of the build time on various machines. There are a number of Fedora 12 machines (skynet?) -- I'm curious if these are going to be upgraded when Fedora 12 reaches "end of life" (in November?) Thanks, Mike asked Sep 10 '10 Mike Witt 465 ● 4 ● 16 ● 26 For question 2, there is already timing information at the end of the log for each spkg, as well as for the main install.log file. Is that good enough? John Palmieri (Sep 10 '10) Well, in 4.5.2, in the build on my fastest machine, it takes 108 minutes. At the end of the log, there is a thing that says "real 89m" - my slowest machine (without ALTAS) takes over 660 minutes and the timer says "real 481m" -- am I missing something? I just do a 'date' at the start and end. Mike Witt (Sep 10 '10) If your last 'date' comes after building the docs, this makes sense to me: the 89 minutes is to build Sage proper, and then it's plausible that it would take 19 more for the docs. Are the modification times for install.log and dochtml.log about 19 minutes apart? John Palmieri (Sep 10 '10) For the build on the "fast" machine, yes the timestamps are exactly 19 minutes apart. I don't have access to the "slow" machine right now, but the time difference there is close to 200 mintues. But I guess the difference is roughly the same percentage of the build time. Mike Witt (Sep 10 '10)

 4 Would it be possible to include the build logs for the "good" builds. Even when my builds are successful, there are generally a lot of scary looking messages in them. It would be nice to be able to compare them to a build that one of the developers was satisfied with. Yes, it's possible. People who report build and test results need to be reminded of this. I have added a reminder in the build/test wiki page for Sage 4.5.3. How about putting the date/time at the very beginning and very end of each log -- so it's easy to get an idea of the build time on various machines. That's a good idea. I have implemented that in my custom build script. The relevant code block is: before="$(date +%s)" make after="$(date +%s)" elapsed_seconds="$(expr$after - $before)" echo Elapsed time:$(date -d "1970-01-01 \$elapsed_seconds sec" +%H:%M:%S) >> install.log  There are a number of Fedora 12 machines (skynet?) -- I'm curious if these are going to be upgraded when Fedora 12 reaches "end of life" (in November?) We, even William Stein, don't have control over the SkyNet build farm, nor do we have control over the GCC Compile Farm. Both are not owned by the Sage project. posted Sep 10 '10 mvngu 316 ● 7 Thank you! Mike Witt (Sep 11 '10)

[hide preview]