HowTo: debug the quality control : Différence entre versions
(Page créée avec « As explained on https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite, a number of quality control checks of the code are run every night to ensure that no... ») |
|||
| Ligne 9 : | Ligne 9 : | ||
Once a failed quality check is established, one should look in the LISMOI.trunk file [https://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk] to find out which version of the code caused a problem (for example 20211105.trunk). One can then find the output of the quality control check in the | Once a failed quality check is established, one should look in the LISMOI.trunk file [https://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk] to find out which version of the code caused a problem (for example 20211105.trunk). One can then find the output of the quality control check in the | ||
| − | lmdz-cq:/tmp/lmdz/ | + | lmdz-cq:/tmp/lmdz/LMDZ[version_number] |
directory with the actual output file of the check_version.sh script in | directory with the actual output file of the check_version.sh script in | ||
| − | lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.20211105.trunk | + | lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.[version_number] |
| + | |||
| + | ('''''lmdz-cq:/tmp/lmdz/LMDZ20211105.trunk''''' and '''''lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.20211105.trunk''''' respectively in our example). | ||
One can then go through the check_version.sh script [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh] comparing with the different output to find out what went wrong. Tests of correction can actually be done in the | One can then go through the check_version.sh script [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh] comparing with the different output to find out what went wrong. Tests of correction can actually be done in the | ||
| − | lmdz-cq:/tmp/lmdz/ | + | lmdz-cq:/tmp/lmdz/LMDZ[version_number] |
directory. | directory. | ||
Version du 16 novembre 2021 à 15:33
As explained on https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite, a number of quality control checks of the code are run every night to ensure that nothing was broken by the most recent commits to the svn depository (note that only the trunk version of the code is tested by this procedure).
This note explains what to do if those regular tests reveal that the code is broken.
The checks are launched by the following script which prepares the distribution version of the code and then lauches the script that actually launches the quality checks. The results of the tests are synthesized in one line and recorded in the following file https://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk. Each line of this file (besides the comments) gives the version of the code being tested, its corresponding svn revision number and the results of the different checks (as explained in the file and the webpage given above [1]
How to debug a failed quality check
Once a failed quality check is established, one should look in the LISMOI.trunk file [2] to find out which version of the code caused a problem (for example 20211105.trunk). One can then find the output of the quality control check in the
lmdz-cq:/tmp/lmdz/LMDZ[version_number]
directory with the actual output file of the check_version.sh script in
lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.[version_number]
(lmdz-cq:/tmp/lmdz/LMDZ20211105.trunk and lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.20211105.trunk respectively in our example).
One can then go through the check_version.sh script [3] comparing with the different output to find out what went wrong. Tests of correction can actually be done in the
lmdz-cq:/tmp/lmdz/LMDZ[version_number]
directory.
