CI Tests Phase Details¶
This web page will show the history of the time (in seconds) spent by the system to execute all the CI tests declared.
The Basic Information¶The rectangle on the top,list some useful information,in the following order:
- Version of OS of the machine (EL6=Scientific Linux 6,EL7=Scientific Linux 7,Darwin=MacOS)
- Name of the CI project/Build number
- Trigger,so how the Build have been launched on the CI System
"trigger script" means that the build has been launched manually,"git push on develop branch" mean that the build has been launched automatically after a push on a develop branch.
- Name of the user or name of the machine that launched the build
- Status of the phase
The graph displays the time spent by the CI System to execute all the CI tests.
Each point in the graph is a clickable link that redirects to an overview of the build.
In the bottom of the page there's a link to the log file for the whole process and also a list of all the CI test executed.
The name of the link is the name of the test defined into the ci_tests.cfg file.
Every test from the list is a clickable link that points to a detailed view of the specific CI Test
The previous image is the graph of a Calibration CI Test on a near detector root file.
The value shown by the graph are:
- Scaled CPU
This is the hypothetical time that the CI Test need if ran on a single CPU with a 100% load.
- Max RSS
This is the Maximum resident memory used by the CI Test.
- Elapsed Time
This is the time spent to complete the test
At the bottom of the page there are also two links to the standard error log ( stderr ) and to the standard output log ( stdout ),and a table with useful statistics