I know we have discussed this in person, but I'll just flag here that obviously in building our check-meson CI testing usage around parsing the human readable stdout, we expose ourselves to a slight risk in that someone could change what the script prints without realizing it is being read in CI. But, this is unlikely to happen - there are not so many devtools scripts and I think developers understand these are in use in CI testing. If we want, we can offer to add a flag for the script which would produce a standard output (some json perhaps). But, we don't need to do this now. 

Aaron (the ci project maintainer) is out of office this week, but we can touch base with him next week to get this merged. And I'll add it to the CI minutes for Thursday.