CamiTK Community Edition merge requestshttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests2018-06-01T18:43:07+02:00https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/86Feature/gitlab runner on win72018-06-01T18:43:07+02:00Emmanuel PromayonFeature/gitlab runner on win7https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/87FIXED do not interrupt all testing process if one test failed2018-06-04T14:15:57+02:00Emmanuel PromayonFIXED do not interrupt all testing process if one test failedFATAL_ERROR option in cmake generated a cmake error and stopped ci-test.sh, which returned with
exit value 1. The report to the dashboard was not submitted, resulting in a green dashboard but with
reduced number of tests pass.
The test j...FATAL_ERROR option in cmake generated a cmake error and stopped ci-test.sh, which returned with
exit value 1. The report to the dashboard was not submitted, resulting in a green dashboard but with
reduced number of tests pass.
The test job should not be interrupted by the first failed test and the dashboard should
show wichh test have failed.https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/84BUG #48: Add '.lib' to 'optimized ' in cmake files2018-06-04T16:56:48+02:00Antoine TacheauBUG #48: Add '.lib' to 'optimized ' in cmake files
closes #48
closes #48
Antoine TacheauAntoine Tacheauhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/88FIXED (tentative) run one XVFB server on which all tests are done2018-06-05T16:45:28+02:00Emmanuel PromayonFIXED (tentative) run one XVFB server on which all tests are doneThis is to try avoid some random "QXcbConnection: Could not connect to display :99" error
(that seems to occur especially during nightly build...)This is to try avoid some random "QXcbConnection: Could not connect to display :99" error
(that seems to occur especially during nightly build...)https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/22Feature/asm for regression test2018-06-08T14:46:10+02:00Emmanuel PromayonFeature/asm for regression testThis branch improves the homonym previous one to add more coherence and better usage for integration testThis branch improves the homonym previous one to add more coherence and better usage for integration testSprint 2018.04Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/90Feature/dont crash if extlib exceptions2018-07-10T15:37:20+02:00Emmanuel PromayonFeature/dont crash if extlib exceptionsSprint 2018.05https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/92Feature/modernize c++2018-07-11T17:13:10+02:00Emmanuel PromayonFeature/modernize c++closes #46closes #46Sprint 2018.05https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/93Release/4.1.0 on develop2018-07-13T15:29:28+02:00Jean-Loup HaberbuschRelease/4.1.0 on developSprint 2018.06Jean-Loup HaberbuschJean-Loup Haberbuschhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/96UPDATED separate test data array (easier to maintain and understand)2018-07-17T16:55:34+02:00Emmanuel PromayonUPDATED separate test data array (easier to maintain and understand)https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/97Bug/cherrypick debian packaging2018-07-25T12:45:20+02:00Emmanuel PromayonBug/cherrypick debian packagingThis are patches generated during the packaging of 4.1.2 for debian
And more checks using lintian.This are patches generated during the packaging of 4.1.2 for debian
And more checks using lintian.Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/98Debian Packaging Continuous Integration2018-08-02T16:46:49+02:00Emmanuel PromayonDebian Packaging Continuous IntegrationAdd debian packaging as a stage of the continuous integration. Should be run regularly (once a week?), not for each commit/push Add debian packaging as a stage of the continuous integration. Should be run regularly (once a week?), not for each commit/push https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/99UPDATED improve output of packaging summary2018-09-26T16:25:13+02:00Emmanuel PromayonUPDATED improve output of packaging summaryhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/100FIXED continous integration2018-10-06T16:09:58+02:00Emmanuel PromayonFIXED continous integrationTrying to fix a strange/unexpected regression introduced
since branch feature/improve-CI-packaging-log
(or introduced by a side effect of the debian machine
configuration?)Trying to fix a strange/unexpected regression introduced
since branch feature/improve-CI-packaging-log
(or introduced by a side effect of the debian machine
configuration?)https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/101Resolve "change the Q_PLUGIN_METADATA(IID ... string in cep wizzard"2019-01-25T13:51:15+01:00Jean-Loup HaberbuschResolve "change the Q_PLUGIN_METADATA(IID ... string in cep wizzard"Closes #76Closes #76https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/103Bug/gitlab runner breaks ci2019-01-30T12:45:53+01:00Emmanuel PromayonBug/gitlab runner breaks ciCloses #79Closes #79https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/104Bug/xvfb erratic access2019-01-30T23:23:29+01:00Emmanuel PromayonBug/xvfb erratic accessCloses #80 (and hopefully closes the bug with it...)Closes #80 (and hopefully closes the bug with it...)https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/105bug/xvfb-erratic-access2019-01-31T13:51:51+01:00Emmanuel Promayonbug/xvfb-erratic-accessEmmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/107Feature/vtk7 compatibility2019-03-01T08:08:37+01:00Emmanuel PromayonFeature/vtk7 compatibilityThe aim of this branch is to provide transparent VTK7 support for the develop branch:
- if you have VTK6 installed on your machine, everything should work like before
- if you have VTK7 installed on your machine, everything should work t...The aim of this branch is to provide transparent VTK7 support for the develop branch:
- if you have VTK6 installed on your machine, everything should work like before
- if you have VTK7 installed on your machine, everything should work too, with a few more disabled test
Some tests need to be disabled when using VTK7 because as for now we cannot manage multiple version of expected output files (and therefore files that are saved using VTK7 differ from the expected files that were saved using VTK6)
Directory `sdk/cmake/ctest/testdatavtk7` contains the expected files that were saved using VTK7.
When CamiTK develop move to VTK7, just move the files of this directory to their respective location. All tests will
then pass.
ThisEmmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/109FIXED separating gitlab runner2019-04-15T21:02:04+02:00Emmanuel PromayonFIXED separating gitlab runnerdebian stable and packaging now have their own runners on two different
VM hosts
What happened :
At one stage, the VM supervisor duplicated the debian stable VM (that had all the gitlab runner installed, registered and running) onto the...debian stable and packaging now have their own runners on two different
VM hosts
What happened :
At one stage, the VM supervisor duplicated the debian stable VM (that had all the gitlab runner installed, registered and running) onto the new debian packaging VM.
After that event there was two gitlab runners, registered using the same token, up and running. Sometimes the debian stable VM gitlab runner took the jobs, and sometimes the new debian packaging VM gitlab runner took the job. If all the jobs of the same pipeline were taken by the same runner, there was no issue and the pipeline succeeded fine. But if, for instance, the debian packaging runner took the check, configure and build jobs, but then the debian stable runner took the test job, then that produced an error.
I deleted the gitlab runner registered on the new debian packaging VM and created a new token and new tag "debian:packaging", just for the packaging.
This branch was created to update the .gitlab-ci.yml file so that the packaging stage/job is exclusively going to run on the new debian packaging VM.
Hopefully that was the last of our pipeline problem to solve!Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/merge_requests/110Bug/#622019-05-08T17:03:47+02:00Theophile TiffetBug/#62Should close [issue 62](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/issues/62).Should close [issue 62](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/issues/62).Emmanuel PromayonEmmanuel Promayon