2012-08-06 07:49:21.034427+00:00 https://api.launchpad.net/1.0/bugs/986261 https://api.launchpad.net/1.0/~elenst https://api.launchpad.net/1.0/maria/+milestone/5.1 https://api.launchpad.net/1.0/bugs/986261/linked_branches https://api.launchpad.net/1.0/bugs/986261/activity https://bugs.launchpad.net/bugs/986261 Elena Stepanova Michael Widenius Maria 5.1 New Low 2012-04-20 16:19:19.260940+00:00 bug Elena Stepanova added bug tags Elena Stepanova tags Elena Stepanova maria: importance Elena Stepanova maria: assignee Elena Stepanova maria: milestone Elena Stepanova bug watch added Brian Evans bug task added Brian Evans attachment added Brian Evans gentoo: importance Bug Watch Updater Elena Stepanova Brian Evans Paolo-pedroni Brian kripton Robin H. Johnson Paolo-pedroni Paolo-pedroni Brian With FEATURES="test -usersandbox" I get these errors: [snip] > > Test Summary Report > ------------------- > ../storage/maria/unittest/ma_test_all-t (Wstat: 256 Tests: > 830 Failed: 15) > Failed tests: 83, 85, 87, 242, 244, 246, 401, 403, 405 > 560, 562, 564, 719, 721, 723 > Non-zero exit status: 1 > Files=35, Tests=145284, 267 wallclock secs ( 8.93 usr 0.30 sys + 138.85 > cusr 56.43 csys = 204.51 CPU) > Result: FAIL > Failed 1/35 test programs. 15/145284 subtests failed. > > Could it be because I have /var/tmp/portage on a tmpfs? I've discovered that ma_test_all-t fails with -O2 or -Os in C(XX)FLAGS set. They work fine if -O1 is set. I've pointed this out on the MariaDB mailing list, but not sure if it's a MariaDB bug or gcc optimization issue. @Robin: Do we need to force -O1 for tests only or should we always do it?]]> kripton Brian Brian Brian Brian LPexportBug986261_20000_all_mariadb_fix_tests.patch