summaryrefslogtreecommitdiff
path: root/mesonbuild/dependencies/python.py
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz93@gmail.com>2025-01-27 16:40:19 -0500
committerEli Schwartz <eschwartz93@gmail.com>2025-01-28 11:26:47 -0500
commitd51e20288853f376e9244671604176913f2e4e79 (patch)
treebce5d750ce115e507f8d2c1dc614458b7ef375e8 /mesonbuild/dependencies/python.py
parentc31963ca80997006347619fb07ee28ee9dd1de49 (diff)
downloadmeson-d51e20288853f376e9244671604176913f2e4e79.tar.gz
fix edge case in testcase expect_error() if error is printed using mlog
It catches the exception message itself, but for multi-line exceptions it may be worth print an error() as well as raising, to communicate multiple bits of information. When using the VS backend, this means that we get an actual `ERROR: ...` printed during a successful run, which then breaks msbuild as msbuild parses stdout of successful commands, regexes them for the word "error:" and interprets that as... an error. So a meson project tests example that uses testcase expect_error() and then successfully configures and builds, fails to successfully `meson --internal regenerate`. Sneak around this by doing our own pattern replace to evade msbuild. There is probably a way to tell msbuild to stop doing this, but that would require me understanding the vs backend well enough to patch the xml it generates. No thanks...
Diffstat (limited to 'mesonbuild/dependencies/python.py')
0 files changed, 0 insertions, 0 deletions