I don't think more testing is the answer. Really, the problems boil down to
a) OSX users running outdated and usupported OSX versions (i.e. anything < 10.10); Do you want to run a buildbot with an OS version that has major unfixed security issues and that has been EOL'ed by the manufacturer? Apple's valuation is 7x the cost of the Apollo program and they don't do it; How many resources do we have at our disposal? b) random crap installed in /usr/local thanks to homebrew. That nothing imports / links from /usr/local could be automatically tested using strace, a compiler wrapper, or poisoned headers like the fake /usr/local/include/gmp.h on my osx buildslave. But more machines won't help unless you want to install random crap on them. c) no windows support d) abuse of LD_LIBRARY_PATH makes Sage impossible to build/use on some Linux distros, e.g. if Sage readline clashes with the version that bash needs then you are SOL. On Sunday, June 14, 2015 at 12:08:03 AM UTC+2, Jeroen Demeyer wrote: > > On 2015-06-13 01:26, William Stein wrote: > > suggestions about how to address this > > problem using new ideas. > More testing? More and different buildbot machines testing more > operating systems? Perhaps using VM's? > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
