Stuck in "Create witness files..."

[sy6sy2]

Hi,

I don't understand why but the script is stuck on "Create witness files..." even after many hours. Is this bug can be due to mu check_process file?

Thanks!

Install Package linter.

Loads functions from launcher.sh
Loads functions from testing_process.sh
Loads functions from log_extractor.sh
grep: /var/lib/lxcsnaps/pchecker_lxc/snap0/rootfs/etc/hosts: Aucun fichier ou dossier de ce type
grep: /var/lib/lxcsnaps/pchecker_lxc/snap0/rootfs/etc/hosts: Aucun fichier ou dossier de ce type
tee: /var/lib/lxcsnaps/pchecker_lxc/snap0/rootfs/etc/hosts: Aucun fichier ou dossier de ce type
Restore the previous snapshot.
Working time: .
Disable iptables rules.
Disable the network bridge.
Pick up the package which will be tested.
Initialize network for LXC.
Sending network state change signal to nslcd...done.
Activate iptables rules.
Parsing of check_process file

Tests serie: Test complet

>> Package linter... [Test 1/10]
YUNOHOST APP PACKAGE LINTER
  App packaging documentation: https://yunohost.org/#/packaging_apps
 App package example: https://github.com/YunoHost/example_ynh
 Checking /home/admin/package_check/kodi_ynh_check package

>>>> MISSING FILES <<<<

>>>> SOURCES MANAGEMENT <<<<

>>>> MANIFEST <<<<
! [YEP-1.2] This app is not registered in official or community applications

>>>> INSTALL SCRIPT <<<<

>>>> REMOVE SCRIPT <<<<

>>>> UPGRADE SCRIPT <<<<

>>>> BACKUP SCRIPT <<<<

>>>> RESTORE SCRIPT <<<<
? [YEP-2.4] 'ynh_die' or 'exit' command is executed with system modification before (cmd 'cp').
This system modification is an issue if a verification exit the script.
You should move this verification before any system modification.

>>>> _COMMON.SH SCRIPT <<<<
--- SUCCESS ---

>> Installation in a sub path... [Test 2/10]
Start the LXC container.
Create witness files...

[JimboJoe]

Hi, You can have a look at the container logs with ssh -t pchecker_lxc then look in /var/log/yunohost/yunohost-cli.log.

[sy6sy2]

Thank you very munch for this informations! Now I know why this bug, and it's due to my package ;-)