HowTo: debug the quality control : Différence entre versions
| (2 révisions intermédiaires par le même utilisateur non affichées) | |||
| Ligne 3 : | Ligne 3 : | ||
This note explains what to do if those regular tests reveal that the code is broken. | This note explains what to do if those regular tests reveal that the code is broken. | ||
| − | The checks are launched by the script [https:// | + | The checks are launched by the script [https://web.lmd.jussieu.fr/~lmdz/Distrib/creation_modipsl.sh creation_modipsl.sh] which prepares the distribution version of the code and then lauches [https://web.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh check_version.sh], which actually launches the quality checks. The results of the tests are synthesized in one line and recorded in the file [https://web.lmd.jussieu.fr/~lmdz/pub/src_archives/Readme Readme]. 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 page [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite Contrôle qualité]). |
=== How to debug a failed quality check === | === How to debug a failed quality check === | ||
| − | Once a failed quality check is established, one should look in the file [https:// | + | Once a failed quality check is established, one should look in the file [https://web.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk 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 directory: |
| − | lmdz-cq:/ | + | lmdz-cq:/home/lmdz/tmp/LMDZ[version_number] |
with the actual output file of the check_version.sh script in | with the actual output file of the check_version.sh script in | ||
| Ligne 18 : | Ligne 18 : | ||
One can then go through the script [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh 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 script [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh 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:/ | + | lmdz-cq:/home/lmdz/tmp/LMDZ[version_number] |
directory. | directory. | ||
[[Category:HowTo]] | [[Category:HowTo]] | ||
[[Category:ExpertDev]] | [[Category:ExpertDev]] | ||
Version actuelle en date du 12 juillet 2023 à 11:58
As explained on the page Contrôle qualité, 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 script creation_modipsl.sh which prepares the distribution version of the code and then lauches check_version.sh, which actually launches the quality checks. The results of the tests are synthesized in one line and recorded in the file Readme. 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 page Contrôle qualité).
How to debug a failed quality check
Once a failed quality check is established, one should look in the file 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 directory:
lmdz-cq:/home/lmdz/tmp/LMDZ[version_number]
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). This output file is also accessible on internet.
One can then go through the script 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:/home/lmdz/tmp/LMDZ[version_number]
directory.
