Hi, I have below issue after updating to latest git and I was wondering how I can fix it. On the machine I build, I do not have GUI and dcop. In fact it is a chrooted environment.
For now I disable the debian check target in the debian/rules file.
Thank you in advance
Scanning dependencies of target check make[4]: Leaving directory '/mnt/DEVELOPMENT/TDE/repo-master/tde/2_build/tdelibs/obj-x86_64-linux-gnu' /usr/bin/make -f dcop/tests/CMakeFiles/check.dir/build.make dcop/tests/CMakeFiles/check.dir/build make[4]: Entering directory '/mnt/DEVELOPMENT/TDE/repo-master/tde/2_build/tdelibs/obj-x86_64-linux-gnu' [100%] Running tests... /usr/bin/ctest Test project /mnt/DEVELOPMENT/TDE/repo-master/tde/2_build/tdelibs/obj-x86_64-linux-gnu Start 1: dcop/dcop-tests 1/40 Test #1: dcop/dcop-tests ...................................***Failed 1.05 sec Start 2: tdecore/tdeconfig_compiler/test1-cpp
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2019/03/07 05:31 PM, deloptes wrote:
Hi, I have below issue after updating to latest git and I was wondering how I can fix it. On the machine I build, I do not have GUI and dcop. In fact it is a chrooted environment.
For now I disable the debian check target in the debian/rules file.
Thank you in advance
Scanning dependencies of target check make[4]: Leaving directory '/mnt/DEVELOPMENT/TDE/repo-master/tde/2_build/tdelibs/obj-x86_64-linux-gnu' /usr/bin/make -f dcop/tests/CMakeFiles/check.dir/build.make dcop/tests/CMakeFiles/check.dir/build make[4]: Entering directory '/mnt/DEVELOPMENT/TDE/repo-master/tde/2_build/tdelibs/obj-x86_64-linux-gnu' [100%] Running tests... /usr/bin/ctest Test project /mnt/DEVELOPMENT/TDE/repo-master/tde/2_build/tdelibs/obj-x86_64-linux-gnu Start 1: dcop/dcop-tests 1/40 Test #1: dcop/dcop-tests ...................................***Failed 1.05 sec Start 2: tdecore/tdeconfig_compiler/test1-cpp
Hi Emanoil, I may be wrong since I have never tried that, but I am not sure what would happen if you try to run TDE without DCOP. It has been an integral part of KDE/TDE since KDE 2 AFAICR. Any particular reason to not having dcop?
Cheers Michele
Michele Calgaro via trinity-devel wrote:
Hi Emanoil, I may be wrong since I have never tried that, but I am not sure what would happen if you try to run TDE without DCOP. It has been an integral part of KDE/TDE since KDE 2 AFAICR. Any particular reason to not having dcop?
Hi Michele, I do not build on TDE. I build in chroot - headless environment. Similar problem I had when testing iCal - cause there is ticket open that tests fail. BTW I know what dcop is, but thank you for the attention.
Unfortunately I was not expecting that February and March will be so busy and I was thinking I could do more, but reality wins, so after there were so many changes on TDE recently I tried updating the repositories and build again - with that and probably some other issues.
So what would be a possible solution to this problem - how do I start/stop dcop in chroot? Is it possible at all?
regards
On Thursday 07 of March 2019 09:31:30 deloptes wrote:
Hi, I have below issue after updating to latest git and I was wondering how I can fix it. On the machine I build, I do not have GUI and dcop. In fact it is a chrooted environment.
For now I disable the debian check target in the debian/rules file.
Thank you in advance
Scanning dependencies of target check make[4]: Leaving directory '/mnt/DEVELOPMENT/TDE/repo-master/tde/2_build/tdelibs/obj-x86_64-linux- gnu' /usr/bin/make -f dcop/tests/CMakeFiles/check.dir/build.make dcop/tests/CMakeFiles/check.dir/build make[4]: Entering directory '/mnt/DEVELOPMENT/TDE/repo-master/tde/2_build/tdelibs/obj-x86_64-linux- gnu' [100%] Running tests... /usr/bin/ctest Test project /mnt/DEVELOPMENT/TDE/repo-master/tde/2_build/tdelibs/obj-x86_64-linux-g nu Start 1: dcop/dcop-tests 1/40 Test #1: dcop/dcop-tests ...................................***Failed 1.05 sec Start 2: tdecore/tdeconfig_compiler/test1-cpp
Hi Emanoil,
this is not a new bug. This test fails from time to time. So far I have not analyzed it in more detail. Usually, you just have to run the build again. By the way, on my builders in the recent 110 tdelibs builds, this test failed once. Because the failure of this test is rare, that's why we did not make much effort.
Cheers
Slávek Banko wrote:
this is not a new bug. This test fails from time to time. So far I have not analyzed it in more detail. Usually, you just have to run the build again. By the way, on my builders in the recent 110 tdelibs builds, this test failed once. Because the failure of this test is rare, that's why we did not make much effort.
Thanks Slavek! I am not sure as well - I just wanted to know what you know about it, because I was thinking I have to have dcop running to pass the test. Perhaps I look into it for the fun of it and try to find out what is the reason for failing, but first I need confirmation that it is legitimate to run the test in chroot without dcop service
regards
Slávek Banko wrote:
Hi Emanoil,
this is not a new bug. This test fails from time to time. So far I have not analyzed it in more detail. Usually, you just have to run the build again. By the way, on my builders in the recent 110 tdelibs builds, this test failed once. Because the failure of this test is rare, that's why we did not make much effort.
Just tested again and indeed first build failed, but next build succeeded. there must be something related to first run of tests.
-
deloptes -
Michele Calgaro via trinity-devel -
Slávek Banko