- 09 Oct, 2019 16 commits
-
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
#1490 Put sonar on a separate stage. Comment out cppcheck entirely as a consequence (just for the test phase).
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
#1490 Add a new stage and use in in a specific Yaml file. This is of course temporary: the goal is to put hat in the normal Yaml and to run it on specific branches (analysis is way too long to be run in each CI run).
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
- 08 Oct, 2019 1 commit
-
-
GILLES Sebastien authored
-
- 03 Oct, 2019 4 commits
-
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
-
GILLES Sebastien authored
-
- 02 Oct, 2019 1 commit
-
-
GILLES Sebastien authored
-
- 12 Sep, 2019 1 commit
-
-
GILLES Sebastien authored
-
- 11 Sep, 2019 5 commits
-
-
GILLES Sebastien authored
-
GILLES Sebastien authored
#1485 Robustify LuaState internal class so that tests about move assignment and construction pass properly.
-
GILLES Sebastien authored
#1485 LuaFunction: handle properly the internal Lua state, which was leaked previously whenever copies where involved (i.e. all the time due to the hoops we use to enable functions are a variant among others in the inpur data file). Comments will be added to underline the copy of the internal object introduced here is all but trivial: we do not in fact copy the state of the source object but generate a new one (which is completely correct for our use case, but is clearly not the natural behaviour of any class...).
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
- 05 Sep, 2019 1 commit
-
-
GILLES Sebastien authored
-
- 04 Sep, 2019 11 commits
-
-
GILLES Sebastien authored
-
GILLES Sebastien authored
#1471 I was wrong assuming I could remove the workaround in the script that filter Doxygen messages (and that is related to Doxygen run under Linux).
-
GILLES Sebastien authored
#1484 Rename CI targets to keep the match between build and chack warnings (otherwise two Doxygen targets were there first on the build_and_test but still at the end in check_warning stage).
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
#1484 Move two Doxygen files outside of Internal directories... and shave off this way 3/4 of the warnings I got in the first place!
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
-
GILLES Sebastien authored
#1483 Script for the warning of Doxygen: add one item to ignore (warning about too much nodes) and remove the one we had to introduce for #1471: new version of Doxygen removed the need for that.
-
GILLES Sebastien authored
#1303 Complete Doxygen documentation for non linear membrane operator (pretension wasn't documented).
-