tools/test: silence alsatplg in tlpg-build.sh unless VERBOSE=1

[marc-hb]

With this commit:

 ./scripts/build-tools.sh -t -f | wc -l
525
VERBOSE=anything ./scripts/build-tools.sh -t -f | wc -l
137030

This a followup to commit aa6c0f2 ("topology: cmake: silence super
chatty alsatplg unless VERBOSE=1")

Signed-off-by: Marc Herbert marc.herbert@intel.com

[jajanusz]

I think that when you make changes like this, you should also update CI scripts in the same PR, so for CI it stays verbose and just default behaviour for user whie building locally changes.

[lgirdwood]

SOFCI TEST

[lgirdwood]

@jajanusz I think the issue was that it was flooding CI logs ? @xiulipan@zrombel please clarify your logging restrictions for CI builds,

[marc-hb]

I would also like to know how useful or useless is the alsatplg output when running ./scripts/build-tools.sh -t -f now before this PR? I'd like everyone who's been fixing issues with it to try to remember these issues and if these 137,000 lines would have been useful to address them. Please add such a person to the review if you see one missing.

Note alsa-utils commit v1.2.2~15-gcbabe7a3f0cc accidentally broke alsatplg's --verbose option. So maybe it wasn't as bad as 137,000 lines before that alsa-utils commit.

[xiulipan]

@lgirdwood I think this will also benefit manual build. With multi-thread enabled, it is almost impossible to find the real error in tons of logs.

[zrombel]

I don't see any changes in CI logs with this PR. Commit aa6c0f2 introduces smaller log from building tools, line count dropped from ~10000 to ~500. This longer log was pretty heavy as for log file - 800KB, but it is not a problem for CI storage which is periodically cleaned. The question is what developers want to see in this log?

[lgirdwood]

Developers only need to see the build breakage - the alsa tooling is PC based so easy for developers to reproduce for fixing.