Continuous integration a walk-through. Dr Alin Marin Elena

Transcription

1 Continuous integration a walk-through Dr Alin Marin Elena Daresbury, 2017

2 Elena et al. Daresbury, vember Theory 2

3 Theory Elena et al. Daresbury, vember Theory 2

4 Elena et al. Daresbury, vember 2017 Continuous integration a walk-through Theory The theory Continuous Integration Maintain a single source repository Automate the build Make your build self-testing Every should build on an integration machine Keep the build fast Test in a clone of the production environment Everyone can see what s happening Automate deployment The practice Developers check out code into their private spaces. When done, the changes to the repository. The CI bot monitors the repository and runs unit and integration tests If the build or tests fail, the CI server alerts the team. The team the issue at the earliest opportunity. Continue to continually integrate and test throughout the project.

5 Elena et al. Daresbury, vember Theory 2

6 Elena et al. Daresbury, vember 2017 review& user/ user/

7 Elena et al. Daresbury, vember 2017 review& user/ user/

8 Elena et al. Daresbury, vember 2017 review& user/ user/

9 Elena et al. Daresbury, vember 2017 review& user/ user/

10 Elena et al. Daresbury, vember 2017 review& user/ user/

11 Elena et al. Daresbury, vember 2017 review& user/ user/

12 Elena et al. Daresbury, vember 2017 review& user/ user/

13 Elena et al. Daresbury, vember 2017 review& user/ user/

14 Elena et al. Daresbury, vember 2017 review& user/ user/

15 Elena et al. Daresbury, vember 2017 review& user/ user/

16 Elena et al. Daresbury, vember 2017 review& user/ user/

17 cont. Elena et al. Daresbury, vember 2017 Tools git, fortran, MPI GitLab cmake, python doxygen, L A TEX The Rules Check in frequently Don t check in broken code Don t check in untested code Don t check in when the build is broken Don t go home after checking in until the system builds

18 Testing Elena et al. Daresbury, vember 2017 custom testing frame in house python3 and xml automatized and integrated in build/gitlab test at different optimisation levels [08:42:32 cmake../ -DBUILD_TESTING=On [08:43:12 make test Running tests... /usr/bin/ctest --force-new-ctest-process Test project /home/drfaustroll/playground/dl-poly/build-gcc Start 1: TEST01 1/25 Test #1: TEST01... Passed 2.77 sec... Start 25: TEST25 25/25 Test #25: TEST25... Passed 3.08 sec 100% tests passed, 0 tests failed out of 25 Total Test time (real) = sec

19 Elena et al. Daresbury, vember 2017 Continuous integration a walk-through Code Compliance enforce Fortran standard and a basic set of runtime checks. via compilers flags: gcc: -g -O0 -std=f2008 -pedantic -fbacktrace -fcheck=all -finit-integer= finit-real=nan -finit-logical=true -finit-character=42 -ffpe-trap=invalid,zero,overflow,denormal intel: -g -O0 -stand f08 -traceback -C -fp-stack-check -ftrapuv -qopt-report=5 external tools, extra code corectness checks, FORCHECK: cmake../ -DWITH_FORCHECK=ON && make forcheck 2x[711 I] declared RECURSIVE but not recursively referenced 2x[786 I] type kind inconsistent with specification 1x[811 E] invalid argument value 1x[812 I] derived-type component not used 3x[813 I] derived-type component not referenced 52x[841 I] module object not used outside the module 48x[859 I] variable, used as actual argument, unreferenced 122x[877 I] INTENT(INOUT) dummy argument is defined before referenced 13x[887 I] array unreferenced 1x[888 I] array not used number of error messages: 54 number of informative messages: 2122

20 Code Coverage Elena et al. Daresbury, vember 2017 How much tested is your code? gcov - gcc only text mode only but html output possible rich statistics on which paths the code takes compiler flags: -g -O0 coverage -fprofile-arcs -ftest-coverage cmake../ -DWITH_COVERAGE=On -DBUILD_TESTING=On && make coverage Summary coverage rate: lines...: 25.4% (17753 of lines) functions..: 49.1% (280 of 570 functions) es...: no data found Reading tracefile coverage.info.cleaned Lines Functions Filename Rate Num Rate Num ======================================================================... source/z_density_module.f90 100% 6 100% 1 source/zero_k_optimise.f90 0.0% % 1 ====================================================================== Total: 25.4% % 570 [100%] Built target coverage

21 Policies Elena et al. Daresbury, vember 2017 coding standard ftp://ftp.dl.ac.uk/ccp5/dl_poly/dl_poly_ 4.0/DOCUMENTS/Coding_Style.pdf code of contribution API documentation & manual ( use -DDOCS=On ) examples and tests