TriBITS
TriBITS copied to clipboard
TriBITSPub
Non-English localization test suite errors
Description
I followed the steps described in the README of TriBITS and had errors. This is the CDASH report.
@mperrinel, it looks like the errors are due to non-English localization. It is looking for words like "Error" and "Only in" but instead is printing "Erreur" and "Seulement dans", respectively. You can see this by running this query and clicking "Show Matching Output".
Is it possible for you to run the test suite on a machine and CMake installation that uses English? It would be too much work to update the test suite to work with any arbitrary language.
NOTE: I currently can't get to https://testing.sandia.gov/cdash/ from Chrome. It says "Your connection is not private" and provides no way to get to the site. Does that happen for you as well? But MS Edge does let me get to that site so I can see the results there.
Note that these tests pass with the GitHub Actions run tests (which use an English localization). See TriBITS CDash Dashboard.
@mperrinel, actually, one thing that you could do that would help with this effort would be to improve the portability of the test suite and replace commands like diff -qr <dir1> <dir2> and ls <filename> with portable cmake -E commands or cmake -P scripts. That will help to get a native Windows invocation of this test suite working as well.
@bartlettroscoe Thanks for the comment. I'm checking that. About the CDASH and chrome, I have the same problem. It is also the case with firefox. I think we can have a look on the portability improvement.
@mperrinel, the challenge that I have found with replacing commands like ls and diff with cmake -E commands in these tests is that you don't get useful output other than 0 or non-0 return codes. For the purpose of these tests, we need to see the STDOUT and STDERR that lists the files involved. That is the core of those checks. An alternative to the cmake -E commands is to write custom cmake -P scripts and make them print whatever you want. Those scripts are portable and you have complete control over what they do and what they print out (unlike cmake -E commands). But it take more work to write those cmake -P scripts which is why I did not do it the first time around.