CamiTK Community Edition issueshttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues2018-03-14T14:08:54+01:00https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/4ctest build name should be set before ctest start2018-03-14T14:08:54+01:00Emmanuel Promayonctest build name should be set before ctest startIf `CTEST_BUILD_NAME` is not set before `ctest_start` the build name that appears on the dashboard is `(empty)`.
The problem is to have the proper hash *before* `ctest_update` is called. As `ctest_update` is called *after* `ctest_start`,...If `CTEST_BUILD_NAME` is not set before `ctest_start` the build name that appears on the dashboard is `(empty)`.
The problem is to have the proper hash *before* `ctest_update` is called. As `ctest_update` is called *after* `ctest_start`, one need to get the hash from origin.Sprint 5Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/3Additional test fail in subproject independent build2023-03-30T21:37:57+02:00Emmanuel PromayonAdditional test fail in subproject independent buildThe dashboard shows that a lot of test currently fails.
The CI nightly and continuous scripts build and run test subproject by subproject.
Additional test are added by any component to any action. Therefore if a component subproject is ...The dashboard shows that a lot of test currently fails.
The CI nightly and continuous scripts build and run test subproject by subproject.
Additional test are added by any component to any action. Therefore if a component subproject is compiled after the action subproject, the action test is necessarily going to fail (as the component data will not be opened).
E.g.
- action `cropvolume` is part of the SDK CEP
- component `itkimage` is part of the imaging CEP
- component `itkimage` declares additional test for action `cropvolume`
- during CI script, subproject `cropvolume` is build and tested before subproject `itkimage`
- all additional test using an itk image fails
At the time of writing, I see only two possible fixes:
- either set a dependency between the additional test and the component subproject
- or find a way to declare test as part of the component subproject, not the actionSprint 5Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/2New test script2018-03-07T10:50:57+01:00Jean-Loup HaberbuschNew test scriptWrite new test script to simulate nightly continuous behavior
Steps
- [x] update gitlab
- [x] Copy nightly script
- [x] remove the git interaction
- [x] test sript on develop branch locallyWrite new test script to simulate nightly continuous behavior
Steps
- [x] update gitlab
- [x] Copy nightly script
- [x] remove the git interaction
- [x] test sript on develop branch locallySprint 5Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/33Save as STL2018-03-28T08:03:18+02:00Emmanuel PromayonSave as STLIt seems that `camitk-imp` does not show STL in save as dialog box.
`StlComponentExtension` should inherits from `MeshComponentExtension` not directly from `ComponentExtension`It seems that `camitk-imp` does not show STL in save as dialog box.
`StlComponentExtension` should inherits from `MeshComponentExtension` not directly from `ComponentExtension`Sprint 7Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/26CAMITK_WARNING: pop up message window, add Esc shortcut2018-03-14T14:09:21+01:00Arthur DeratheCAMITK_WARNING: pop up message window, add Esc shortcutAbout you:
Arthur Derathé
Product:
Surgery Evaluation Environment
Overview:
It's more for convenience as a user in camitk-imp
before, with QMessageBox::warning, the window displaying the message could...About you:
Arthur Derathé
Product:
Surgery Evaluation Environment
Overview:
It's more for convenience as a user in camitk-imp
before, with QMessageBox::warning, the window displaying the message could be closed with the "Enter" and the "Esc" buttons.
Now with the camitk logger, it's only possible to close it with "Enter".
As my interface requires already a lot of clicks, it would be much appreciated to regain this feature!Sprint 7Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/25Camitk Logger: Genaralize Log trace to component instanciation and action sta...2018-03-14T14:11:22+01:00Arthur DeratheCamitk Logger: Genaralize Log trace to component instanciation and action start/endAbout you:
Arthur Derathé
Product:
Surgical Evaluation Environment
Overview:
It would be interesting to generalize the writing of CAMITK_TRACE/CAMITK_INFO when instanciating/Destructing components as ...About you:
Arthur Derathé
Product:
Surgical Evaluation Environment
Overview:
It would be interesting to generalize the writing of CAMITK_TRACE/CAMITK_INFO when instanciating/Destructing components as well as when starting/ending actions.
With a method such as setInLog(bool enabled) this processed would be managed in the component/action constructorSprint 7https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/102INTERACTIVEVIEWER_API undefined in RenderWidget.h2020-06-26T08:52:48+02:00Theophile TiffetINTERACTIVEVIEWER_API undefined in RenderWidget.h## About you
PhD student
## Problem
'INTERACTIVEVIEWER_API' is not defined in 'sdk/libraries/core/viewer/RenderWidget.h line 102 and 105. A quick search through files showed that it is not defined anywhere.
## Possible solution
Should...## About you
PhD student
## Problem
'INTERACTIVEVIEWER_API' is not defined in 'sdk/libraries/core/viewer/RenderWidget.h line 102 and 105. A quick search through files showed that it is not defined anywhere.
## Possible solution
Should it be CAMITK_API ?
## CamiTK Version
As of 15/06/2020, last version in the develop branch.
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 1Jean-Loup HaberbuschJean-Loup Haberbuschhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/105Invisible VTK 3D widgets2020-07-09T21:29:06+02:00Emmanuel PromayonInvisible VTK 3D widgets## About you
CamiTK dev
## Overview
VTKWidgets not visible in 3D
## Steps to Reproduce
1. Open a mesh component file
2. Launch the Mesh Clipping action
3. Nothing vtk widget appears in 3D
## Actual VS Expected Result
There should...## About you
CamiTK dev
## Overview
VTKWidgets not visible in 3D
## Steps to Reproduce
1. Open a mesh component file
2. Launch the Mesh Clipping action
3. Nothing vtk widget appears in 3D
## Actual VS Expected Result
There should be a vtk widget to change the cutting plane
## Interpretation & Possible fixes
Check the action code, is the widget properly initialized
## CamiTK Version
CamiTK 4.2.dev.develop.04a1c024
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 2Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/104Update CI for packaging2020-07-06T22:48:00+02:00Emmanuel PromayonUpdate CI for packaging| | |
|--|--|
| **As a** | CamiTK developer |
| **I would like to** | test debian sid compilation of develop |
| **So that** | quickly be able to produce an official debian packaging |
| **Epic/Topics** | /label ~"Track Continuous Integ...| | |
|--|--|
| **As a** | CamiTK developer |
| **I would like to** | test debian sid compilation of develop |
| **So that** | quickly be able to produce an official debian packaging |
| **Epic/Topics** | /label ~"Track Continuous Integration" |
## Description / Overview
Considering:
- the change in the VM server at TIMC (note: domain is now `u-ga.fr` not `imag.fr`)
- the update policy for supported dependencies and toolchain (see #96)
The packaging should work on the current develop branch
## Hints
- Check packaging pipeline logs
- Update code or CMake accordingly
## Acceptance tests
- [x] `camitk-ci-linux-packaging` host the updated packaging CI gitlab runner
- [x] the packaging pipeline is back working
## Track
/label ~"Track Continuous Integration" CamiTK 4.2 Sprint # 2Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/111Camitk-imp crash when "Application-Close" on a component.2020-08-28T18:24:28+02:00Sylvain GuyCamitk-imp crash when "Application-Close" on a component.## About you
Developer of a CEP
## Overview
Applying "Application-Close" on a camitk component results sometimes in a crash. It doesn't seem to be deterministic. It may crash on the load or close.
## Steps to Reproduce
File- Open - "...## About you
Developer of a CEP
## Overview
Applying "Application-Close" on a camitk component results sometimes in a crash. It doesn't seem to be deterministic. It may crash on the load or close.
## Steps to Reproduce
File- Open - "brain.mha". Right click on "brain" -Application - Close.
If it doesn't crash direclty, reload brain.mha and close again. It will end up crashing on the loading or the closing.
## Relevant logs and/or screenshots
**Crash on the loading (after 2 load close)**
```
*** Program received signal SIGSEGV (Segmentation fault) ***
#0 tcache_get (tc_idx=<optimized out>) at malloc.c:2937
#1 __GI___libc_malloc (bytes=24) at malloc.c:3051
#2 0x00007f63c3d21c29 in operator new(unsigned long) () at /lib/x86_64-linux-gnu/libstdc++.so.6
#3 0x00007f63c2c32604 in vtkTransformConcatenationStack::New() () at /tmp/dependencies/VTK-6.3.0/Common/Transforms/vtkAbstractTransform.h:402
#4 0x00007f63c2c3284f in vtkTransform::Push() (this=0x562eaca5c000) at /tmp/dependencies/VTK-6.3.0/Common/Transforms/vtkTransform.h:280
#5 0x00007f63c2d30923 in vtkAssemblyPath::AddNode(vtkAssemblyNode*) (this=0x562eacca10d0, n=0x562eadc89e90) at /tmp/dependencies/VTK-6.3.0/Rendering/Core/vtkAssemblyPath.cxx:55
#6 0x00007f63c2d308d5 in vtkAssemblyPath::AddNode(vtkProp*, vtkMatrix4x4*) (this=0x562eacca10d0, p=0x562eac88cc70, m=0x562eacca42f0) at /tmp/dependencies/VTK-6.3.0/Rendering/Core/vtkAssemblyPath.cxx:45
#7 0x00007f63c2ccb2d2 in vtkProp3D::InitPathTraversal() (this=0x562eac88cc70) at /tmp/dependencies/VTK-6.3.0/Rendering/Core/vtkProp3D.cxx:600
#8 0x00007f63c5d6e71d in camitk::RendererWidget::addProp(vtkSmartPointer<vtkProp>, bool) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#9 0x00007f63c5d55202 in camitk::InteractiveViewer::addActor(camitk::Component*, vtkSmartPointer<vtkProp>) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#10 0x00007f63c5d54913 in camitk::InteractiveViewer::refresh(camitk::Viewer*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#11 0x00007f63c5d685a8 in camitk::InteractiveViewerFrame::showEvent(QShowEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#12 0x00007f63c56552b6 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f63c5702d52 in QFrame::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f63c5612a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f63c561c0f0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f63c5cd9428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#17 0x00007f63c4bfa93a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f63c5651c17 in QWidgetPrivate::show_helper() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007f63c5654d6b in QWidgetPrivate::setVisible(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007f63c5d73ba9 in camitk::Viewer::setVisible(bool) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#21 0x00007f63c5bb7793 in MedicalImageViewer::updateLayout() () at /home/guys/.config/CamiTK/lib/camitk-4.2/viewers/libmedicalimageviewer.so.4
#22 0x00007f63c5bb6043 in MedicalImageViewer::refresh(camitk::Viewer*) () at /home/guys/.config/CamiTK/lib/camitk-4.2/viewers/libmedicalimageviewer.so.4
#23 0x00007f63c5ceda2f in camitk::MainWindow::refresh() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#24 0x0000562ea8d62f40 in ImpMainWindow::refresh() ()
#25 0x00007f63c5cd9c0b in camitk::Application::refresh() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#26 0x00007f63c5cda83b in camitk::Application::open(QString const&) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#27 0x00007f6373d0047f in OpenFile::apply() () at /home/guys/.config/CamiTK/lib/camitk-4.2/actions/libapplication.so.4.2.dev
#28 0x00007f63c5cd22b2 in camitk::Action::applyAndRegister() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#29 0x0000562ea8d6700f in ImpMainWindow::openRecentDocuments() ()
#30 0x0000562ea8d61e98 in ImpMainWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) ()
#31 0x00007f63c4c26300 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x00007f63c560c3e6 in QAction::triggered(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#33 0x00007f63c560eaa2 in QAction::activate(QAction::ActionEvent) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#34 0x00007f63c5794d12 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#35 0x00007f63c579c4ae in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#36 0x00007f63c579d4d2 in QMenu::mouseReleaseEvent(QMouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#37 0x00007f63c56552b6 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#38 0x00007f63c579fadb in QMenu::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#39 0x00007f63c5612a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#40 0x00007f63c561c343 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#41 0x00007f63c5cd9428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#42 0x00007f63c4bfa93a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#43 0x00007f63c561b457 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#44 0x00007f63c5671ce4 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#45 0x00007f63c56741ec in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#46 0x00007f63c5612a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#47 0x00007f63c561c0f0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#48 0x00007f63c5cd9428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#49 0x00007f63c4bfa93a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#50 0x00007f63c4fe37d3 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#51 0x00007f63c4fe510b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#52 0x00007f63c4fbf35b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#53 0x00007f63bcca432e in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#54 0x00007f63c0d80fbd in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#55 0x00007f63c0d81240 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#56 0x00007f63c0d812e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#57 0x00007f63c4c52565 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#58 0x00007f63c4bf94db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#59 0x00007f63c4c01246 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#60 0x00007f63c5cd9bbe in camitk::Application::exec() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#61 0x0000562ea8d6c6d4 in main ()
```
**Crash after closing (after 2 load close)**
```
malloc_consolidate(): invalid chunk size
*** Program received signal SIGABRT (Aborted) ***
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007f7908e07859 in __GI_abort () at abort.c:79
#2 0x00007f7908e723ee in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f7908f9c285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#3 0x00007f7908e7a47c in malloc_printerr (str=str@entry=0x7f7908f9e278 "malloc_consolidate(): invalid chunk size") at malloc.c:5347
#4 0x00007f7908e7ac58 in malloc_consolidate (av=av@entry=0x7f78fc000020) at malloc.c:4477
#5 0x00007f7908e7c160 in _int_free (av=0x7f78fc000020, p=0x7f78fc01a460, have_lock=<optimized out>) at malloc.c:4400
#6 0x00007f7909fa8637 in QObject::~QObject() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007f7909f2ff3d in QItemSelectionModel::~QItemSelectionModel() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007f7909f9e01e in QObjectPrivate::deleteChildren() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x00007f790a9cac29 in QWidget::~QWidget() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007f790ac4735d in QTableView::~QTableView() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f790b098f0e in camitk::ImageComponent::~ImageComponent() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#12 0x00007f78bb094048 in VtkImageComponent::~VtkImageComponent() () at /home/guys/.config/CamiTK/lib/camitk-4.2/components/libvtkimage.so.4
#13 0x00007f78bb09409c in VtkImageComponent::~VtkImageComponent() () at /home/guys/.config/CamiTK/lib/camitk-4.2/components/libvtkimage.so.4
#14 0x00007f790b055eb7 in camitk::Application::close(camitk::Component*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#15 0x00007f78b90721f8 in CloseAction::apply() () at /home/guys/.config/CamiTK/lib/camitk-4.2/actions/libapplication.so.4.2.dev
#16 0x00007f790b04c2b2 in camitk::Action::applyAndRegister() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#17 0x00007f790b04c068 in camitk::Action::trigger(QWidget*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#18 0x00007f790b02eac3 in camitk::Action::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#19 0x00007f7909fa0300 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f790a9863e6 in QAction::triggered(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x00007f790a988aa2 in QAction::activate(QAction::ActionEvent) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x00007f790ab0ed12 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x00007f790ab164ae in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x00007f790ab174d2 in QMenu::mouseReleaseEvent(QMouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x00007f790a9cf2b6 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x00007f790ab19adb in QMenu::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x00007f790a98ca66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x00007f790a996343 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#29 0x00007f790b053428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#30 0x00007f7909f7493a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x00007f790a995457 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#32 0x00007f790a9ebce4 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#33 0x00007f790a9ee1ec in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#34 0x00007f790a98ca66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#35 0x00007f790a9960f0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#36 0x00007f790b053428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#37 0x00007f7909f7493a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#38 0x00007f790a35d7d3 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#39 0x00007f790a35f10b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#40 0x00007f790a33935b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#41 0x00007f790201e32e in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#42 0x00007f79060fafbd in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#43 0x00007f79060fb240 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#44 0x00007f79060fb2e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#45 0x00007f7909fcc565 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#46 0x00007f7909f734db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#47 0x00007f790ab140b1 in QMenu::exec(QPoint const&, QAction*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#48 0x00007f790af190bf in Explorer::rightButtonPressed(QPoint const&) () at /home/guys/.config/CamiTK/lib/camitk-4.2/viewers/libexplorer.so.4
#49 0x00007f790af169cc in Explorer::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /home/guys/.config/CamiTK/lib/camitk-4.2/viewers/libexplorer.so.4
#50 0x00007f7909fa0300 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#51 0x00007f790a9b52d9 in QWidget::customContextMenuRequested(QPoint const&) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#52 0x00007f790a9cff85 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#53 0x00007f790aa7cd52 in QFrame::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#54 0x00007f790ac01482 in QAbstractItemView::viewportEvent(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#55 0x00007f790ac6f62f in QTreeView::viewportEvent(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#56 0x00007f7909f7464b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#57 0x00007f790a98ca55 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#58 0x00007f790a996b93 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#59 0x00007f790b053428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#60 0x00007f7909f7493a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#61 0x00007f790a9eb94a in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#62 0x00007f790a9ee1ec in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#63 0x00007f790a98ca66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#64 0x00007f790a9960f0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#65 0x00007f790b053428 in camitk::Application::notify(QObject*, QEvent*) () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#66 0x00007f7909f7493a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#67 0x00007f790a35d7d3 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#68 0x00007f790a35f10b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#69 0x00007f790a33935b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#70 0x00007f790201e32e in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#71 0x00007f79060fafbd in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#72 0x00007f79060fb240 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#73 0x00007f79060fb2e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#74 0x00007f7909fcc565 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#75 0x00007f7909f734db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#76 0x00007f7909f7b246 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#77 0x00007f790b053bbe in camitk::Application::exec() () at /home/guys/.config/CamiTK/lib/libcamitkcore.so.4
#78 0x000055ad5179f6d4 in main ()
```
## Interpretation & Possible fixes
At the beginning I thought it was the fault of the destructors of my component, but since the bug also appears with the basic component of CamiTK, I have no idea where the issue could come from.
## CamiTK Version
CamiTK 4.2.dev.develop.32c2e525
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/110Outdated documentation2021-01-18T17:29:51+01:00Theophile TiffetOutdated documentation## About you
Tiffet Théophile PhD student
## Product
Documentation for CamiTK
## Overview
Following the modification of the viewers, their doxygen documentation was not updated. Classes like PropertyExplorer, MedicalImageViewer and o...## About you
Tiffet Théophile PhD student
## Product
Documentation for CamiTK
## Overview
Following the modification of the viewers, their doxygen documentation was not updated. Classes like PropertyExplorer, MedicalImageViewer and others still are considered singleton with a getInstance static method in the documentation. This should be with the new way of refreshing them, getting access to them with the string you have to use.
A migration guide would also be welcome.
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/98CMake code generation over viewer's extension targets2020-09-28T20:36:22+02:00Emmanuel PromayonCMake code generation over viewer's extension targets## About you
CamiTK dev
## Overview
If a component or action declares a dependency to a viewer extension, CMake generates an error during generation.
```bash
CMake Error in actions/testactions/CMakeLists.txt:
The dependency target ...## About you
CamiTK dev
## Overview
If a component or action declares a dependency to a viewer extension, CMake generates an error during generation.
```bash
CMake Error in actions/testactions/CMakeLists.txt:
The dependency target "viewer-medicalimageviewer" of target
"action-testactions_autogen" does not exist.
```
→ The viewer's extension targets are not exported properly and generate an error
## Steps to Reproduce
In an action `CMakeLists.txt`, add the following line inside the `camitk_extension` parameters:
```cmake
camitk_extension(ACTION_EXTENSION
...
NEEDS_VIEWER_EXTENSION medicalimageviewer
...
)
```
## Actual VS Expected Result
When running the CMake generation on the project, the following error is generated
```bash
CMake Error in actions/testactions/CMakeLists.txt:
The dependency target "viewer-medicalimageviewer" of target
"action-testactions_autogen" does not exist.
```
The target is not known by the CEP as it is not exported by CamiTK CE.
The expected result is a error free CMake generation
I created a specific branch and MR (see !147) with cepgenerator test files.
This can be considered as fixed when the test `application-cepgenerator-bash-test` in MR !147 returns no error.
To run the test :
- checkout branch `bug/target-export`
- configure and build
- run the corresponding test:
```bash
ctest -VV -R application-cepgenerator-bash-test
```
## Interpretation & Possible fixes
Two possible fixes:
- ~~either fix CamiTK CMake files so that extensions are exported~~
- ~~tweak the cepgenerator to add the following lines in the generated action `CMakeLists.txt` AND document the manual fix in the wiki.~~
```cmake
# Add this line in the action or component CMakeLists.txt, before the call to the camitk_extension macro
add_library(viewer-medicalimageviewer INTERFACE IMPORTED)
```
- ~~FindCamiTK.cmake includes these export lines~~
Note that a similar line has to be added from each added NEEDS_VIEWER_EXTENSION dependencies
## CamiTK Version
`CamiTK version........................... CamiTK 4.2.dev.bug-target-export.0cf6a8fa`
~"Track Debugging"CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/83Remove console on windows version of all GUI CamiTK application (camitk-imp, ...2020-07-30T16:03:34+02:00Emmanuel PromayonRemove console on windows version of all GUI CamiTK application (camitk-imp, camitk-actionstatemachine, camitk-wizard)| | |
|--|--|
| **As a** | camitk-imp user and CamiTK developer |
| **I would like to** | optimize the application performance and not have a visible (1990's) dark console when I launch imp |
| **So that** | I am not disturbed by another...| | |
|--|--|
| **As a** | camitk-imp user and CamiTK developer |
| **I would like to** | optimize the application performance and not have a visible (1990's) dark console when I launch imp |
| **So that** | I am not disturbed by another window on the screen, and therefore I focus on the task I need to do in the main window of camitk-imp |
| **Epic/Topics** | ] |
## Description / Overview
By default, MSVC compile camitk-imp and all other GUI-based CamiTK programs as a console program.
As stated [here](https://blog.rubenwardy.com/2019/02/15/porting-cpp-to-windows-vcpkg/), this mode results in Windows allocating and showing a console for you when starting the program up (e.g. CamiTK-imp). This console will require a redraw on every std::cerr or std::cout print, resulting in massive performance issues.
The best would be have a specific option in the `camitk_application` macro to declare the application as a console application (by default, and considering the CAMI domain, I suppose it is better to say that an application has a GUI by default, only specific CamiTK application are console only).
E.g.:
```cmake
camitk_application(...
NO_GUI
...
)
```
## Hints
As stated [here](https://blog.rubenwardy.com/2019/02/15/porting-cpp-to-windows-vcpkg/):
> If you program shows a graphical window, then you should change it to a Windows program. There are three methods to do this.
> The first option is to set the executable type to WIN32 in CMake:
```cmake
if(WIN32)
add_executable(${EXECUTABLE_NAME} WIN32 ${SRC})
else()
add_executable(${EXECUTABLE_NAME} ${SRC})
endif()
```
This is confirmed to work in [this answer on stackoverflow](https://stackoverflow.com/a/36528717/9890401).
The [second proposed option](https://blog.rubenwardy.com/2019/02/15/porting-cpp-to-windows-vcpkg/) seems a bit to windowesque and rely on the MSVC compiler. The third proposed option should not be considered here as it won't be a nice way considering the CamiTK objectives (it make use of a `#pragma`)
See also the [CMake documentation for add_executable](https://cmake.org/cmake/help/latest/command/add_executable.html) and [WIN32_EXECUTABLE property/flag](https://cmake.org/cmake/help/latest/prop_tgt/WIN32_EXECUTABLE.html#prop_tgt:WIN32_EXECUTABLE)
## Acceptance tests
- [x] When run camitk-imp, camitk-actionstatemachine, and camitk-wizard do not show any console
- [x] All other CamiTK CE application seem to work as before (e.g. the config and cepgenerator test pass)
- [x] The `camitk_application` macro has a new option for console application
- [x] The `camitk_application` macro documents this new option (so that generated doxygen talks about it)
## Track
~"Track Prototyping Experience" CamiTK 4.2 Sprint # 3Jean-Loup HaberbuschJean-Loup Haberbuschhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/57Launcher wizard for Action State Machine interface2020-08-25T21:56:49+02:00Emmanuel PromayonLauncher wizard for Action State Machine interface## About you
Submitted on bugzilla by Antoine Tacheau @tacheaua, 2017-09-11
## Product
Action state machine
## Overview
> Currently, we need to open a terminal and type this kind of command to start asm:
>
> camitk-actionstatemachi...## About you
Submitted on bugzilla by Antoine Tacheau @tacheaua, 2017-09-11
## Product
Action state machine
## Overview
> Currently, we need to open a terminal and type this kind of command to start asm:
>
> camitk-actionstatemachine -f <ProtocolFile> -o <LogFolder>
>
> Since Action State Machine can be used by 'basic user' to run new protocol, it would be easier if a launcher or an interface were available.
>
> ~~For instance:~~
> a gui interface in order to select which protocol should be started
> ~~or~~
> ~~- a specific protocol file (only changing extension by .asm, .prot, .protocolASM ...) to be associated to asm executable. Thus, users only have to double click to start application~~ (moved to issue #67)
>
> ~~It is also required to set a default behavior for log file argument~~
>
> -- Antoine Tacheau
As of 4 July 2018, this issue was split in two. Current issue is about showing a dialog if no command line argument is given.
The other issue (issue #67) is about defining a specific "protocol" file that contains the SCXML file as well as the log folder and adding a `-protocol` option to provide this file.
## Hints
I think the best would be to:
- detect the case when the user launches `camitk-actionstatemachine` without any command line arguments (not even `--help`)
- in this case, offer a mini Qt Wizard with:
- 1 page with explanation why the user is asked for more
- 1 page to choose the `scxml`
- 1 page to choose the output directory
- launch the normal processCamiTK 4.2 Sprint # 3Jean-Loup HaberbuschJean-Loup Haberbuschhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/121Debian packaging failed2021-02-01T22:22:38+01:00Emmanuel PromayonDebian packaging failedJob [#197871](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/197871) failed for 45108ed033f366a2c065e14aae61c1fd7c83255b:
The package was not generated, please check the artifacts and fix the problem:
- summary: https...Job [#197871](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/197871) failed for 45108ed033f366a2c065e14aae61c1fd7c83255b:
The package was not generated, please check the artifacts and fix the problem:
- summary: https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/197871/artifacts/raw/debian-unstable-develop/log/summary.log
- check environment: https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/197871/artifacts/raw/debian-unstable-develop/log/check-environment.log
- build package: https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/197871/artifacts/raw/debian-unstable-develop/log/build-package.log
- prepare package environment: https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/197871/artifacts/raw/debian-unstable-develop/log/prepare-package-environment.logCamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/119CMake error when trying to install a CEP dependent on another CEP2021-01-14T14:13:23+01:00Emmanuel PromayonCMake error when trying to install a CEP dependent on another CEP## About you
CamiTK developer/maintainer
## Overview
In CamiTK community edition, the cep-generator test allows us to check that everything works when compiling a CEP that depends on CamiTK SDK
There is no test that check the third-le...## About you
CamiTK developer/maintainer
## Overview
In CamiTK community edition, the cep-generator test allows us to check that everything works when compiling a CEP that depends on CamiTK SDK
There is no test that check the third-level dependency, i.e., when trying to compile and install a CEP that depends on another CEP that depends on CamiTK SDK.
With recent version of CMake, warnings about missing autogen target became errors.
Now it is not possible to install a CEP that depends on another already installed CEP without a CMake error (although it is possible to build it...).
## Steps to Reproduce
This is quite long to reproduce:
1. build and install the latest develop version of CamiTK CE
2. create a CEP called level2cep that has dependencies to CamiTK SDK, e.g. that have a component that depends on medicalimageviewer or vtkmesh. This CEP should create a new component, lets call it level2comp
3. build an install level2cep
4. create a CEP called level3cep that has dependencies to level2Cp, e.g. that have a component that depends on level2comp
5. build level3cep
At configure time you should see an error:
```cmake
CMake Error in components/level2comp/CMakeLists.txt:
The dependency target "component-level2comp" of target
"component-level2comp_autogen" does not exist.
```
BUT the build will finish and everything will work
6. try to install level3cep, you you will get the same error but the install will fail.
## Actual VS Expected Result
There should be no error and the the install should work.
## Interpretation & Possible fixes
CMake camitk_extension macro should take into account the fact that if a target is not found, it should be declared as imported.
Possible fix: add a test in camitk_extension to check if a target exist or not using `if (NOT TARGET ...)`
**Caveat:** using `if (NOT TARGET ...)` will not be able to distinguish between external targets and local targets that are not yet declared in the configuration process.
## CamiTK Version
CamiTK 4.2.dev.develop.ae2812e8
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/118Replace Copyright text by a more discrete watermark.2021-01-19T06:51:09+01:00Emmanuel PromayonReplace Copyright text by a more discrete watermark.## About you
CamiTK developer/maintainer
## Product
CamiTK interactive viewers
## Overview
Since the update to support VTK 7, the copyright text disappeared from the right corner of the Interactive Viewer instances.
Although the copy...## About you
CamiTK developer/maintainer
## Product
CamiTK interactive viewers
## Overview
Since the update to support VTK 7, the copyright text disappeared from the right corner of the Interactive Viewer instances.
Although the copyright text was a bit 1980's it was nice to have something that was a bit like a watermark.
It was quite intrusive though (but it was possible to remove it by Right-Clicking on an interactive viewer).
The best would be to replace it by a more discrete watermark.
I suggest using a smallish CamiTK logo with some transparency in the very bottom very right corner of the viewer.
The advantage will be to encourage people to leave the logo (it is too small to be annoying in most of the case), and therefore be able to promote nice projects that use CamiTK.
→ May be have a little dialog to promote citing the article as well/instead of the logo, when the user decide to disable the logo?
---CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/116More coherent MISR tutorial actions GUI2021-01-05T07:31:05+01:00Emmanuel PromayonMore coherent MISR tutorial actions GUI## About you
CamiTK developer
## Product
Mainly camitk-imp
## Overview
During the http://misr.free.fr tutorial, there are three different things that could be improved in order to make discovering medical image analysis easier and fac...## About you
CamiTK developer
## Product
Mainly camitk-imp
## Overview
During the http://misr.free.fr tutorial, there are three different things that could be improved in order to make discovering medical image analysis easier and facilitate knowledge acquisitions:
- (easy) the action menu are not coherent (the "Display" family has "Volume Rendering" but not "Lookup Table" action, Save, Close, Save As are in a menu called "Application", which is not the same as the menu name in the menu bar
- (time consuming) the Volume Rendering action is not really easy to use (complex to setup) and appears in a separate window (and is not managed like any other actions)
- (hard) the Lookup Table action has a lot of bugs and does not allow a proper visualization/interaction with the values in the images
## What can be done
- [x] Rename the "Application" menu to "File"
- [X] Rewrite "Volume Rendering" so that it can be used like any other actions
- [X] Debug Lookup Table and improve the GUI so that it has a true pedagogical usage
- [x] Rename "Display" to "View" and move "Lookup Table", "Arbitrary Slice" to this family.
- [x] Move "Visibility" to "View"
- [X] Computed output in Otsu and Connected component should be updated automatically, visible once the action is performed, and reset at each select and should also appear in the log
- [X] Visibility toggle should be visible for the View actions
- [X] Manual filter should take the voxel range value, not the type min/max (and therefore be updated at each select
- [X] Try to fix opening file with space/special character in path on windows
- [X] better handling of mha/mhd when type is not unsigned char
- [X] Frame editor manages precision (when value <1e-6, just display 0.0)
- [x] Separate frame editor in three actions: show/hide frame, set parent frame, show/edit frame
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/115Pipeline does not detect failed tests2020-11-22T10:07:31+01:00Emmanuel PromayonPipeline does not detect failed tests## About you
CamiTK developer
## Overview
The action state machine tests failed, tests are sometimes reran, but the errors are not detected by the test script.
The pipeline does not fail although it should clearly fail. We are lull to ...## About you
CamiTK developer
## Overview
The action state machine tests failed, tests are sometimes reran, but the errors are not detected by the test script.
The pipeline does not fail although it should clearly fail. We are lull to a false sense of security, while there is a bug!
The two Linux configuration shows different logs but both do not detect the error
## Steps to Reproduce
- For linux stable: check [Job #177308](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/177308)
- For linux LTS: check [Job #177309](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/177309)
## Actual VS Expected Result
The pipeline should fail when there is a failed test, independently of the type of failure.
## Relevant logs and/or screenshots
### On Linux stable
In the [Job #177308](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/177308) log,
the initial tests failed with:
```
4/5 Test #132: application-actionstatemachine-5 .........Child aborted***Exception: 2.81 sec
5/5 Test #131: application-actionstatemachine-4 .........***Timeout 1800.13 sec
```
But then at the end of the job log we have:
```
===== Fatal errors =====
Found fatal error in /builds/CamiTK/CamiTK/debian-stable-develop/log/ci-test.log
===== Failed tests =====
===== Re-running failed tests =====
Re-ran tests OK
```
The relevant lines in the test.log show:
```
132: X Error of failed request: BadWindow (invalid Window parameter)
132: Major opcode of failed request: 2 (X_ChangeWindowAttributes)
132: Resource id in failed request: 0x2
132: Serial number of failed request: 7
132: Current serial number in output stream: 9
132: terminate called after throwing an instance of 'std::bad_array_new_length'
132: what(): std::bad_array_new_length
4/5 Test #132: application-actionstatemachine-5 .........Child aborted***Exception: 2.81 sec
5/5 Test #131: application-actionstatemachine-4 .........***Timeout 1800.13 sec
```
The rerun-test.log contains only one line:
```
Checking /builds/CamiTK/CamiTK/debian-stable-develop/log/test.log for failed test
```
### On Linux LTS
In the [Job #177309](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/177309) log,
the initial tests failed with:
```
4/5 Test #131: application-actionstatemachine-4 .........Child aborted***Exception: 0.71 sec
5/5 Test #132: application-actionstatemachine-5 .........***Timeout 1800.13 sec
```
But then at the end of the job log we have:
```
===== Fatal errors =====
Found fatal error in /builds/CamiTK/CamiTK/ubuntu-lts-develop/log/ci-test.log
===== Failed tests =====
===== Re-running failed tests =====
Re-ran tests OK
```
The relevant lines in the test.log show:
```
131: ...
131: X Error of failed request: BadWindow (invalid Window parameter)
131: Major opcode of failed request: 2 (X_ChangeWindowAttributes)
131: Resource id in failed request: 0x2
131: Serial number of failed request: 7
131: Current serial number in output stream: 9
131: terminate called after throwing an instance of 'std::bad_alloc'
131: what(): std::bad_alloc
4/5 Test #131: application-actionstatemachine-4 .........Child aborted***Exception: 0.71 sec
5/5 Test #132: application-actionstatemachine-5 .........***Timeout 1800.13 sec
```
The rerun-test.log contains only one line:
```
Checking /builds/CamiTK/CamiTK/ubuntu-lts-develop/log/test.log for failed test
```
## Interpretation & Possible fixes
The test script is faulty, see `.gitlab/test.sh`.
It should be better at parsing the log to detect problems
## CamiTK Version
CamiTK 4.2.dev.develop.92087062
Compiled using git Hash: 92087062bc6533f58297c18826f5256436b37807, Date: Tue Oct 20 00:24:15 2020 +0200.CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayonhttps://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/issues/114Failed test in action state machine2020-11-25T01:00:51+01:00Emmanuel PromayonFailed test in action state machine## About you
CamiTK developer
## Overview
Job [#178103](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/178103) failed for 92087062bc6533f58297c18826f5256436b37807
- The new action state machine test generates a bug, ...## About you
CamiTK developer
## Overview
Job [#178103](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/178103) failed for 92087062bc6533f58297c18826f5256436b37807
- The new action state machine test generates a bug, see
## Steps to Reproduce
Just check the pipeline.
On Linux (Job [#178103](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/178103)):
```
132: X Error of failed request: BadWindow (invalid Window parameter)
132: Major opcode of failed request: 2 (X_ChangeWindowAttributes)
132: Resource id in failed request: 0x2
132: Serial number of failed request: 7
132: Current serial number in output stream: 9
132: QObject::disconnect: Unexpected null parameter
```
On Windows (Job [#175675](https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK/-/jobs/175675)):
```
131: 2020-11-10 05:27:09.600 [TRACE ] Application "camitk-actionstatemachine" - Logging in C:/builds/win10-develop/sdk/applications/actionstatemachine/2020-11-10T05-27-09
131: 2020-11-10 05:27:10.760 [ERROR ] Application "camitk-actionstatemachine" - Caught an unknown exception
131: C:/builds/win10-develop/bin/camitk-actionstatemachine-debug.exe aborted...
131: Unknown Exception
1/1 Test #131: application-actionstatemachine-4 ...***Exception: SegFault 6.90 sec
```
(there is also another bug in this job, as the error is not considered failed by the pipeline)
## Actual VS Expected Result
Should not failed
## Relevant logs and/or screenshots
See related jobs
## CamiTK Version
CamiTK 4.2.dev.develop.92087062
Compiled using git Hash: 92087062bc6533f58297c18826f5256436b37807, Date: Tue Oct 20 00:24:15 2020 +0200.
---
**please do not remove anything below this line**CamiTK 4.2 Sprint # 3Emmanuel PromayonEmmanuel Promayon