User Details
- User Since
- Mar 19 2019, 10:30 PM (80 w, 18 h)
- Availability
- Available
Jul 16 2020
Today when I've been trying with -j48 test suite was locked and was not able to finish.
When I've presses ctrol-c I found:
PASS: t-eventloop Decrypt B 0 Encrypt A 0 Decrypt B 1 Encrypt A 1 Decrypt B 2 Encrypt A 2 Decrypt B 3 Encrypt A 3 Decrypt B 4 Decrypt B 5 Encrypt A 4 Decrypt B 6 Encrypt A 5 Decrypt B 7 Encrypt A 6 Decrypt B 8 Encrypt A 7 Decrypt B 9 Encrypt A 8 Decrypt B 10 Encrypt A 9 Decrypt B 11 Encrypt A 10 Decrypt B 12 Encrypt A 11 Decrypt B 13 Encrypt A 12 Decrypt B 14 Encrypt A 13 Decrypt B 15 Encrypt A 14 Decrypt B 16 Decrypt B 17 Encrypt A 15 Decrypt B 18 Encrypt A 16 Decrypt B 19 Encrypt A 17 Encrypt A 18 Encrypt A 19 PASS: t-thread1 make[4]: *** [Makefile:882: check-TESTS] Interrupt make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/gpgme-1.13.1/tests/gpg' [tkloczko@barrel SPECS]$ make[3]: *** [Makefile:1008: check-am] Interrupt make[2]: *** [Makefile:1010: check] Interrupt make[1]: *** [Makefile:736: check-recursive] Interrupt make: *** [Makefile:535: check-recursive] Interrupt ^C
+ GPGME_DEBUG=8:gpgme.trc + /usr/bin/make -O -j1 V=1 VERBOSE=1 check Making check in src make[1]: Entering directory '/home/tkloczko/rpmbuild/BUILD/gpgme-1.13.1/src' make[1]: Nothing to be done for 'check'. make[1]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/gpgme-1.13.1/src' Making check in tests make[1]: Entering directory '/home/tkloczko/rpmbuild/BUILD/gpgme-1.13.1/tests' Making check in gpg make[2]: Entering directory '/home/tkloczko/rpmbuild/BUILD/gpgme-1.13.1/tests/gpg' /usr/bin/make check-am make[3]: Entering directory '/home/tkloczko/rpmbuild/BUILD/gpgme-1.13.1/tests/gpg' /usr/bin/make check-TESTS make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/gpgme-1.13.1/tests/gpg' gpg-agent already running PASS: initial.test -----BEGIN PGP MESSAGE-----
Jul 15 2020
Feb 25 2020
Latest one (gnupg 2.2.19)
Sorry but that really strange.
I need to regenerate those files.
Could you please describe what needs to be done to have proper version?
Aug 26 2019
Please do not force me subscribe to yet another mailing list to see the answer.
So do you have any plans to make new release? :)
Aug 24 2019
Jul 2 2019
I cannot do that because all listed above packages are my own products.
Fedora is not execution test suites in more than 90% of all packages so they are not aware of most of the issues exposed by test suites.
Please focus on possible causes of above tests.
I'm opened on any suggestions to make additional diagnostics.
[tkloczko@barrel SPECS]$ uname -a Linux barrel 5.1.5-300.fc30.x86_64 #1 SMP Sat May 25 18:00:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux [tkloczko@barrel SPECS]$ rpm -q libassuan-devel libcurl-devel libgcrypt-devel libgpg-error-devel libksba-devel libusb-devel npth-devel openldap-devel pcsc-lite-libs gnutls-devel sqlite-devel libassuan-devel-2.5.3-2.1.fc31.x86_64 libcurl-devel-7.65.1-2.fc31.x86_64 libgcrypt-devel-1.8.4-4.1.fc31.x86_64 libgpg-error-devel-1.36-2.fc31.x86_64 libksba-devel-1.3.5-10.1.fc31.x86_64 libusb-devel-0.1.5-14.fc30.x86_64 npth-devel-1.6-3.fc31.x86_64 openldap-devel-2.4.47-2.2.fc31.x86_64 pcsc-lite-libs-1.8.25-2.1.fc31.x86_64 gnutls-devel-3.6.8-2.fc31.x86_64 sqlite-devel-3.28.0-2.fc31.x86_64
Still about half of the packages are from Fedora rawhide but rest are mine.
Just checked and the test suite fails exactly the same way even started without palatalisation.
Apr 7 2019
Which one version gcc 9 you've been using?
May I see gcc -v ?
Apr 6 2019
BTW: fedora corp provides already free access to build envs with gcc 9 which can be easily integrated with CIs.
What you mean " it is not reproducible for u"?
Did you try to use gcc 9 and you had no problems compiling gnupg or you don't have access to build env with gcc 9?
Try to google to "gcc 9 pragma" and you will find several discussions and patches done by people fixing similar issues.
Apr 5 2019
Why do you think that it is gcc bug?