Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
In #4013 I forgot to add a unit test for meson.
However, when I tried to add it now (naming the test file meson.build), I got the following in meson.build.log:
Unknown filetype extension for "/tmp/tmp.XJrc9S8Suo/test.build.tags".
The reason is that unlike other filetypes, the Meson configuration in filetype_extensions.conf doesn't start with *. but instead the whole filename is used:
Meson=meson.build;meson.options;meson_options.txt;
The unit test runner creates test files starting with test, followed by the filetype extension and this doesn't match what's in filetype_extensions.conf.
What should we do about it?
A simple (but ugly) way would be to add some *.meson_unittest extension to filetype_extensions.conf which we would use for the unit test but which wouldn't be used in real life.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.