Support the translation tests better outside of CI#51733
Support the translation tests better outside of CI#51733kevingranade merged 3 commits intoCleverRaven:masterfrom
Conversation
|
Both real production translations ( |
|
Test translations should be compiled only for tests but not for release distribution, so BTW what is |
It isn't used anywhere in the build script, it's the standard way to run the tests locally. See e.g. the GNU standard targets. |
845a499 to
680ac6f
Compare
|
Compiling |
|
While I'm cleaning things up, do we still need the English-related special cases in |
|
English |
0821656 to
b7f1eeb
Compare
|
Are there any of the "cleans" that should be removing |
b7f1eeb to
fcd9783
Compare
Good catch. Added. |
Some of the translation tests verify the existence of a path, but don't say what that path is on failure. Capture the path so that they do.
This related to a libintl bug and is no longer relevant now that we don't use libintl.
The new translation tests require a .mo file to be compiled related to the TEST_DATA mod. This was done for CI in the build.sh script, but that's not appropriate for local users. Move the commands from build.sh to Makefile and CMakeLists.txt. Also, add a stamp file so that the Makefile does not rebuild the .mo files unnecessarily.
fcd9783 to
ff4db05
Compare
|
CMake build passed this time, so marking ready for review. |
Summary
None
Purpose of change
The new translation tests require a
.mofile to be compiled related to the TEST_DATA mod. This was done for CI in the build.sh script, but that's not appropriate for local users.Describe the solution
Move the commands from
build.shtoMakefile.Describe alternatives you've considered
Running the build directly from within the unit test.
Testing
Works OK locally.
This is probably going to break the CMake CI, so opening as draft to see what happens.
Additional context
@BrettDong Based on my local testing it seems like the tests only require the one
TEST_DATA.mofile; you don't have to runcompile_mo.sh; is that right?