HowTo: debug the quality control - Historique des versions

Lguez le 28 octobre 2025 à 15:58

2025-10-28T15:58:58Z

Lfairhead le 12 juillet 2023 à 10:58

2023-07-12T10:58:28Z

Lfairhead le 12 juillet 2023 à 10:56

2023-07-12T10:56:40Z

Lfairhead le 7 février 2023 à 14:27

2023-02-07T14:27:39Z

Lguez le 16 décembre 2022 à 11:17

2022-12-16T11:17:10Z

Lguez le 16 décembre 2022 à 11:15

2022-12-16T11:15:16Z

Lguez le 16 décembre 2022 à 11:13

2022-12-16T11:13:44Z

Lguez le 12 décembre 2022 à 17:42

2022-12-12T17:42:58Z

Lguez le 12 décembre 2022 à 17:40

2022-12-12T17:40:45Z

Lfairhead le 16 novembre 2021 à 14:36

2021-11-16T14:36:07Z

@@ Ligne 3 : / Ligne 3 : @@
 This note explains what to do if those regular tests reveal that the code is broken.
-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é]).
+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é]). The results are in:
 === How to debug a failed quality check ===

@@ Ligne 3 : / Ligne 3 : @@
 This note explains what to do if those regular tests reveal that the code is broken.
-The checks are launched by the script [https://www.lmd.jussieu.fr/~lmdz/Distrib/creation_modipsl.sh creation_modipsl.sh] which prepares the distribution version of the code and then lauches [https://www.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é]).
+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 ===
-Once a failed quality check is established, one should look in the file [https://www.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:
+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:/home/lmdz/tmp/LMDZ[version_number]

@@ Ligne 9 : / Ligne 9 : @@
 Once a failed quality check is established, one should look in the file [https://www.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:/tmp/lmdz/LMDZ[version_number]
+  lmdz-cq:/home/lmdz/tmp/LMDZ[version_number]
 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
-   lmdz-cq:/tmp/lmdz/LMDZ[version_number]
+   lmdz-cq:/home/lmdz/tmp/LMDZ[version_number]
 directory.
 [[Category:HowTo]]
 [[Category:ExpertDev]]

@@ Ligne 3 : / Ligne 3 : @@
 This note explains what to do if those regular tests reveal that the code is broken.
-The checks are launched by the script [https://www.lmd.jussieu.fr/~lmdz/Distrib/creation_modipsl.sh creation_modipsl.sh] which prepares the distribution version of the code and then lauches [https://www.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://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk 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 page [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite Contrôle qualité]).
+The checks are launched by the script [https://www.lmd.jussieu.fr/~lmdz/Distrib/creation_modipsl.sh creation_modipsl.sh] which prepares the distribution version of the code and then lauches [https://www.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 ===

@@ Ligne 7 : / Ligne 7 : @@
 === How to debug a failed quality check ===
-Once a failed quality check is established, one should look in the file [https://www.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
+Once a failed quality check is established, one should look in the file [https://www.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:/tmp/lmdz/LMDZ[version_number]
-directory with the actual output file of the check_version.sh script in
+with the actual output file of the check_version.sh script in
   lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.[version_number]

@@ Ligne 1 : / Ligne 1 : @@
-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).
+As explained on the page [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite 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 [https://www.lmd.jussieu.fr/~lmdz/Distrib/creation_modipsl.sh following script] which prepares the distribution version of the code and then lauches the [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh 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 [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite]
+The checks are launched by the script [https://www.lmd.jussieu.fr/~lmdz/Distrib/creation_modipsl.sh creation_modipsl.sh] which prepares the distribution version of the code and then lauches [https://www.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://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk 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 [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite]
 === How to debug a failed quality check ===
-Once a failed quality check is established, one should look in the [https://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk LISMOI.trunk file] 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 file [https://www.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
   lmdz-cq:/tmp/lmdz/LMDZ[version_number]
@@ Ligne 17 : / Ligne 17 : @@
 ('''''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 [https://lmdz.lmd.jussieu.fr/Distrib/WORK accessible on internet].
-One can then go through the [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh check_version.sh script] 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:/tmp/lmdz/LMDZ[version_number]
 directory.

← Version précédente		Version du 16 novembre 2021 à 14:36
Ligne 20 :		Ligne 20 :
	lmdz-cq:/tmp/lmdz/LMDZ[version_number]		lmdz-cq:/tmp/lmdz/LMDZ[version_number]
	directory.		directory.
		+
		+	[[Category:HowTo]]
		+	[[Category:ExpertDev]]