aboutsummaryrefslogtreecommitdiff
path: root/mesonbuild/compilers/compilers.py
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2023-01-04 16:49:19 -0500
committerDylan Baker <dylan@pnwbakers.com>2023-01-22 18:45:35 -0800
commit8d39c9273b58a7a9ba3c4c34125d5f37e5684a99 (patch)
treef78ee94eaefb9401f7fa3df3731f3db789084817 /mesonbuild/compilers/compilers.py
parent2df484176ff63763c47406701f2cbcbea2b66679 (diff)
downloadmeson-8d39c9273b58a7a9ba3c4c34125d5f37e5684a99.zip
meson-8d39c9273b58a7a9ba3c4c34125d5f37e5684a99.tar.gz
meson-8d39c9273b58a7a9ba3c4c34125d5f37e5684a99.tar.bz2
mtest: do not warn when the TAP stream version is 12
Partial rollback of commit b7a5c384a1f1ba80c09904e7ef4f5160bdae3345. The rationale was based on a confusing wording of the TAP14 spec, which is under discussion for clarification / amendment. TAP14 doesn't (shouldn't) really say that missing a version line is potentially an error. Rather, this is the correct way to denote TAP12, which a TAP14 harness may not understand or try to parse. The intention was never to suggest that harnesses "should" take exception to the missing version line on the grounds that one should really add a version line. So, stop emitting an annoying warning for something that's valid usage. Meson understands TAP12 and that's okay. However, we do need to keep the part of that commit which set the version to 12 if it was otherwise unspecified. But instead of distinguishing between None and a version, just default to 12.
Diffstat (limited to 'mesonbuild/compilers/compilers.py')
0 files changed, 0 insertions, 0 deletions