On Mon, Feb 20, 2012 at 10:35:31AM -0600, Bruno Wolff III wrote: > On Sun, Feb 19, 2012 at 10:24:51 +0100, > Mark de Wever <[email protected]> wrote: > > > > I'm not entirely sure whether this is a good idea. The gcc-4.7 and > > gcc-snapshot are experimental compilers. Gcc adds new default warnings > > with newer compiler versions and since warnings are errors with our > > default switches the compilation will fail. This mean the CI tests fail > > after a random compiler update (especially gcc-snapshot; it's a gcc > > development snapshot). I rather see the CI tests use released compilers > > instead of their development snapshots. > > Fedora is using gcc 4.7 for F17 which will be released in May. So testing > that compiler is probably worth doing.
I agree it's worth testing, only not sure whether the CI environment is the best place to test it. I want to avoid some random commit just after a compiler update result in people blaming that commit for the breakage. Gcc-4.7 might be finished enough to try in the CI, but Oleg also wanted to run gcc-snapshot, which is a lot more volatile. Like I said later in the email I also run tests at my own box, where I test gcc development snapshots and gcc 4.7, so gcc 4.7 is being tested. -- Regards, Mark de Wever aka Mordante/SkeletonCrew _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
