aboutsummaryrefslogtreecommitdiff
path: root/mesontest.py
AgeCommit message (Collapse)AuthorFilesLines
2017-01-01style: fix E225 violationsIgor Gnatenko1-2/+2
E225: missing whitespace around operator Signed-off-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>
2016-12-31Fix space before :.Jussi Pakkanen1-7/+7
2016-12-20Minimal fixes to make tests pass when cross compiling.Jussi Pakkanen1-1/+5
2016-12-20Fix cross test and run them if a cross compiler is available.Jussi Pakkanen1-1/+1
2016-12-11If/elif fix so running just mesontest actually runs the tests after doing a ↵Jussi Pakkanen1-2/+2
rebuild.
2016-12-11Use a big timeout when running gdb interactively and a typo fix.Jussi Pakkanen1-2/+7
2016-12-07mesontest: Fix exceptionPatrick Griffis1-0/+1
2016-12-03mesontest: Rebuild all before running testsThibault Saunier1-6/+42
Only supporting ninja backend for now.
2016-12-03Typo fix.Jussi Pakkanen1-4/+4
2016-12-03Merge pull request #1128 from thiblahute/mesontest_misc_fixesJussi Pakkanen1-24/+57
mesontest misc fixes
2016-12-03Stray debug print removal.Jussi Pakkanen1-1/+0
2016-12-02mesontest: Properly let user know when a test timeout out in verbose modeThibault Saunier1-0/+2
2016-12-02tests: Allow user to change timeout timeThibault Saunier1-1/+5
For example if we know the tests takes more time because, for example we are tracing it, or running with very high debug log level we might not want the test to timeout.
2016-12-02mesontest: Do not timeout when running inside GDBThibault Saunier1-1/+2
2016-12-02mesontest: Let user work with gdb when not running in a loopThibault Saunier1-1/+3
In the normal case the user probably wants to set break point or anything when running an app in gdb, we should let him a chance to do so. In the case he is running in a loop, it probably means he want to reproduce a crash or a race inside gdb so we should just go and run in gdb. We probably miss a few options to give him more control.
2016-12-02mesontest: Respect repeat argument even when running testsuitesThibault Saunier1-22/+46
2016-12-01mesontest: Error out even in verbose mode when running repeatidlyThibault Saunier1-6/+6
2016-11-29Support skipped testsDaniel Stone1-1/+8
Knowing whether a test failed to run as its prerequisites were not available, or whether those prerequisites were available and produced unexpected/incorrect results, is a useful differentiation. Add support for skipped tests by testing for exit code 77, used through autotools/piglit/etc to denote a test which detected this and decided to skip.
2016-11-23mesontest: Add a 'verbose' mode which does not capture stdout/errThibault Saunier1-44/+55
And reuse that mode when running inside gdb instead of reimplementing running test for that particular use case.
2016-11-22mesontest: Fix usage of test.env as it can be a build.EnvironmentVariablesThibault Saunier1-0/+4
2016-11-22mesontest: Fix the --wd option and rename it to -C to be coherent with ninjaThibault Saunier1-4/+5
2016-11-22mesontest: Fix --list optionThibault Saunier1-1/+3
The listing code path could not be hit when running mesontest --list
2016-11-18Can run special tests with the new tool.Jussi Pakkanen1-42/+46
2016-11-18All testing is now in mesontest.py, which simplifies a lot of stuff.Jussi Pakkanen1-9/+285
2016-11-18Made Meson test into a class rather than abusing global variables and as ↵Jussi Pakkanen1-1/+7
preparation for moving it elsewhere.
2016-11-18Can run benchmarks.Jussi Pakkanen1-1/+3
2016-11-18Run all tests if none are specified.Jussi Pakkanen1-0/+3
2016-11-18Removed Valgrind from core.Jussi Pakkanen1-1/+1
2016-11-18Can run tests under gdb.Jussi Pakkanen1-14/+29
2016-11-18Add option to run under gdb.Jussi Pakkanen1-0/+6
2016-11-18New test runner.Jussi Pakkanen1-0/+63