This is the dashboard for all PETSc testing
Dashboard for daily testing of all source code
- next; run everyday 1:20am to 7:30am Chicago time
- maint; run weekends (sat-sun) 9:30am to 3:30pm
- next-tmp; run weekdays (mon-fri) 9:30am to 3:30pm
- master; run everyday 5:30pm to 11:30pm
Logs for tarball/documentation build
Continuous integration testing of updated branches
- github
- bitbucket
- When branches are pushed up to bitbucket some compile and build tests are automatically run on the branch (eventually it should email errors to the pusher)
Test Code Coverage (gcov): shows all code lines that are not tested in the test suites
- master; available after 4:30 am following each weekday
- The goal is to get nearly 100 percent coverage and insure that all important routines are fully tested
Results of Clang static analyser on the source code and examples
- Currently to access go to the Dashboard for daily testing and click on the orange [S] and [E]
- The goal is to only have issues that are due to incomplete information available to Clang
Results of valgrind on the test suite
- Currently to access go to the Dashboard for daily testing and click on lines with the word valgrind
- The goal is to only have valgrind errors due to external packages or system libraries
Include Graph for PETSc
- master
- next
- We should also have tools that detect inappropriate/unneeded includes in the source code such as kspimpl.h within PC code etc.
- The goal is to have include files only included where necessary. Faster compiles and code less likely to break encapsulation
Visible Private Functions for PETSc
- master
- next
- The goal is to have only properly name-spaced end user functions publically visible
External packages that use PETSc
- SLEPc
- The goal is to detect changes in PETSc that break other packages immediately when the changes are made instead of months later.
Reference info for petsc developers
- crontab location: /home/petsc/.crontab.rc
- dashboard location: /mcs/ftp/pub/petsc/nightlylogs/index.html