7 Mar
2019
7 Mar
'19
12:31 a.m.
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
7 Mar
7 Mar
5:12 a.m.
New subject: [trinity-devel] tdelibs: Scanning dependencies of target check fails at dcop
-----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
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAlyBGLsACgkQKnW3yore
1c/x7w//UEA46blAPQcQrhocyf6Pw/j6VezOAamP0LdM1FpNIin6JaIJu2IbofOd
onAE4kINvBWaD+zfqP50JhDIO7Nq2kAe20KE5tXLkTliUy1T3CrCTBSh64/hLk08
Qczjwz9AFUZpZP1g6ld5obnXZDNtmPeHlPWPQFd5n1ftH/n4r8gnS1USK2DRJZoC
K7kOrGfj6zC9sNjN/aQOemZVZM1BEVPPLAARoPqk411U1WnLaegAKK7BzJNOFTmr
p/fiy7DSVihdqfCKBp45xmZH/mxW0q1xhKaYnYa1qaNxo5p5fdup/egsTAhbebhG
Apdi/rOIPJVqorCerfcFFP5y4EKvWbgM1ZLWv9YDIqH1MXZGzpHEBgD8unFEwjQV
inIvVMJlkG41JCUkTQ/7ev1auDugq2+/m5H4WXrPU9Xjtgvf61MN+1nnqP7Zgf7z
/d2cqSTwfHkH1E2snIoLm0sKyHgOlQyW6SO8FBQrb3xKyyIpcMiZwV3ATPidNmRU
hTlAhY4EoZxngutrdQYk/LsumKv3cKDFkIYiSZbMPNK6xtJwHPfp0LfvkkAc00Au
W4OxG/5PPhkJlOcB0LYXN1WVFcd+Ghzofl+1Y6/jgLbHp4/Gr9fcD+PH5JTKWlCc
tTMEj4LIcRD2sf0Lc/FAP1aZItm8RyXkXBSxbqlpT4Q3RRBLQ80=
=N8Gu
-----END PGP SIGNATURE-----
10:50 a.m.
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
4:44 p.m.
New subject: [trinity-devel] tdelibs: Scanning dependencies of target check fails at dcop
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
8 Mar
8 Mar
10:37 a.m.
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
2 Apr
2 Apr
2:18 p.m.
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.
2063
days inactive
2089
days old
5 comments
3 participants
participants (3)
-
deloptes -
Michele Calgaro via trinity-devel -
Slávek Banko