diff options
| author | Jon Turney <jon.turney@dronecode.org.uk> | 2018-02-12 20:00:26 +0000 |
|---|---|---|
| committer | Jussi Pakkanen <jpakkane@gmail.com> | 2018-02-14 19:15:30 +0200 |
| commit | c027bb2c42e54b7e89de605c671abd165d379bbc (patch) | |
| tree | caf55483d7b78c85cd91a7c6ffb202c0e0e8e070 /mesonbuild/interpreter.py | |
| parent | e2b5ac29d6ce52faaa5daa214a07f3b76501ca98 (diff) | |
| download | meson-c027bb2c42e54b7e89de605c671abd165d379bbc.zip meson-c027bb2c42e54b7e89de605c671abd165d379bbc.tar.gz meson-c027bb2c42e54b7e89de605c671abd165d379bbc.tar.bz2 | |
Ensure any generation error appears in the logfile and thus in CI output
Since c2a5ac39, MesonApp.generate() closes the logfile before returning,
which means that when invoked by mesonmain.run(), any MesonException is not
logged there.
MesonApp.generate() does not appear to have any other users I can find.
This somewhat reduces the diagnostic value of the logfile.
This also interacts badly with running project tests in CI, as _run_tests
chooses to report the logfile contents, rather than stdout, for the
configure step, and it thus doesn't report any configure error which caused
a test failure.
Diffstat (limited to 'mesonbuild/interpreter.py')
0 files changed, 0 insertions, 0 deletions