KGpg tests in FreeBSD seems to be failing due to gpg-agent error.
https://build.kde.org/job/Applications%20kgpg%20kf5-qt5%20FreeBSDQt5.10/10/console
Killing already running gpg-agent may help.
Description
I've checked and there is no running gpg-agent processes on all of the FreeBSD nodes.
Could something else be causing this issue?
Which gpg version is installed on the FreeBSD machine? GnuPG >=2.1 will automatically start the gpg-agent, while older versions need a running gpg-agent. So the problem could be that the agent is actually _not_ running.
root@freebsd-node1:~ # gpg --version gpg (GnuPG) 2.2.6 libgcrypt 1.8.2 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Home: /root/.gnupg Supported algorithms: Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compression: Uncompressed, ZIP, ZLIB, BZIP2
Should be new enough to start an agent?
I've also confirmed that the gpg-agent binary is available, and running gpg-agent --daemon by hand works fine as far as I can tell.
Could you try running the tests interactively? This could give either new messages or it may suddenly work because a tty is available.
A coincidence was a discussion in the #gnupg channel about agent problems, which had this advise:
Reminder: "log-file socket://" in all conf file and running watchgnupg is the best way to track down such problems.
Maybe that reveals something of interest.
All the tests passed when run interactively.
[jenkins@freebsd-node2 /usr/home/jenkins/workspace/Applications ark kf5-qt5 FreeBSDQt5.10]$ python3.5 -u ci-tooling/helpers/run-tests.py --product Applications --project ark --branchGroup kf5-qt5 --platform FreeBSDQt5.10 --usingInstall /home/jenkins/install-prefix/ kdeinit5: preparing to launch '/home/jenkins/install-prefix/lib/libexec/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 16981, result = 0 qt.qpa.screen: Failed to parse EDID data for output "screen" qt.qpa.screen: adding QXcbScreen(0x611000019b80, name="screen", geometry=1600x1200+0+0, availableGeometry=1600x1200+0+0, devicePixelRatio=1.0, logicalDpi=QPair(100.1,99.9), physicalSize=406.0x305.0mm, screenNumber=0, virtualSize=1600x1200 (1600.0x1200.0mm), orientation=Qt::ScreenOrientation(LandscapeOrientation), depth=24, refreshRate=0.0, root=2d4, windowManagerName="Openbox") (Primary: true ) qt.qpa.screen: primary output is "screen" qt.qpa.input: Plugin build with support for XInput 2 version up to 2.2 qt.qpa.input: Using XInput version 2.2 qt.qpa.input.devices: input device Virtual core XTEST pointer ID 4 qt.qpa.input.devices: has 10 buttons qt.qpa.input.devices: has valuator "Rel X" recognized? true qt.qpa.input.devices: has valuator "Rel Y" recognized? true qt.qpa.input.devices: it's a scrolling device qt.qpa.input.devices: input device Xvfb mouse ID 6 qt.qpa.input.devices: has 3 buttons qt.qpa.input.devices: has valuator "Rel X" recognized? true qt.qpa.input.devices: has valuator "Rel Y" recognized? true qt.qpa.gl: Choosing xcb gl-integration based on following priority ("xcb_glx", "xcb_egl") qt.qpa.gl: Xcb GLX gl-integration created qt.qpa.gl: Xcb GLX gl-integration successfully initialized org.kde.kcrash: Could not find drkonqi in search paths: ("/usr/home/jenkins/install-prefix/lib/libexec/kf5", "/usr/local/libexec/qt5", "/home/jenkins/install-prefix/lib/libexec") Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeinit5: opened connection to :90 Cannot find file: /usr/home/jenkins/workspace/Applications ark kf5-qt5 FreeBSDQt5.10/build/DartConfiguration.tcl Site: Build name: (empty) Create new tag: 20180609-2233 - Experimental Cannot find file: /usr/home/jenkins/workspace/Applications ark kf5-qt5 FreeBSDQt5.10/build/DartConfiguration.tcl Test project /usr/home/jenkins/workspace/Applications ark kf5-qt5 FreeBSDQt5.10/build Start 1: app-batchextracttest kf5.kinit.klauncher: new app ":1.1" 1/17 Test #1: app-batchextracttest ............. Passed 0.48 sec Start 2: kerfuffle-addtoarchivetest kf5.kinit.klauncher: new app ":1.2" 2/17 Test #2: kerfuffle-addtoarchivetest ....... Passed 1.23 sec Start 3: kerfuffle-deletetest 3/17 Test #3: kerfuffle-deletetest ............. Passed 0.21 sec Start 4: kerfuffle-loadtest 4/17 Test #4: kerfuffle-loadtest ............... Passed 0.89 sec Start 5: kerfuffle-extracttest 5/17 Test #5: kerfuffle-extracttest ............ Passed 1.84 sec Start 6: kerfuffle-addtest 6/17 Test #6: kerfuffle-addtest ................ Passed 1.85 sec Start 7: kerfuffle-movetest 7/17 Test #7: kerfuffle-movetest ............... Passed 2.64 sec Start 8: kerfuffle-copytest 8/17 Test #8: kerfuffle-copytest ............... Passed 3.07 sec Start 9: kerfuffle-createdialogtest kf5.kinit.klauncher: new app ":1.3" 9/17 Test #9: kerfuffle-createdialogtest ....... Passed 3.62 sec Start 10: kerfuffle-metadatatest 10/17 Test #10: kerfuffle-metadatatest ........... Passed 0.07 sec Start 11: kerfuffle-mimetypetest 11/17 Test #11: kerfuffle-mimetypetest ........... Passed 0.08 sec Start 12: kerfuffle-adddialogtest kf5.kinit.klauncher: new app ":1.4" 12/17 Test #12: kerfuffle-adddialogtest .......... Passed 3.29 sec Start 13: kerfuffle-jobstest 13/17 Test #13: kerfuffle-jobstest ............... Passed 0.20 sec Start 14: plugins-cliziptest 14/17 Test #14: plugins-cliziptest ............... Passed 0.07 sec Start 15: plugins-cli7ztest 15/17 Test #15: plugins-cli7ztest ................ Passed 0.11 sec Start 16: plugins-clirartest 16/17 Test #16: plugins-clirartest ............... Passed 0.11 sec Start 17: plugins-cliunarchivertest 17/17 Test #17: plugins-cliunarchivertest ........ Passed 0.11 sec 100% tests passed, 0 tests failed out of 17 Total Test time (real) = 19.89 sec XIO: fatal IO error 4 (Interrupted system call) on X server ":90" after 13881 requests (13881 known processed) with 0 events remaining. The X11 connection broke (error 1). Did the X11 server die? kdeinit5: Fatal IO error: client killed kdeinit5: sending SIGHUP to children. klauncher: Exiting on signal 1 kdeinit5: sending SIGTERM to children. kdeinit5: Exit.
I have reworked the tests so every test creates it's own temporary directory as GnuPG homedir, which seems to have fixed the problems on FreeBSD. Similar problems now happen on the SUSE builder, but for fewer tests.
Okay. Is there any further assistance you need to diagnose why those tests are failing?
I did see the following in the logs in case it is relevant:
gpg: Note: '--status-fd=1' is not considered an option gpg: Note: '--import' is not considered an option gpg: Note: '--allow-secret-key-import' is not considered an option gpg: Note: '--command-fd=0' is not considered an option gpg: key BA7695F3C550DF14: "Test KGpg" not changed gpg: can't open '--status-fd=1': No such file or directory gpg: can't open '--import': No such file or directory gpg: can't open '--allow-secret-key-import': No such file or directory gpg: can't open '--command-fd=0': No such file or directory
From what I can see these tests are passing now? (Although there have been some regressions on Linux?)
Yes, seems to work. They are generally a bit flaky, but those looks like timeouts to me as they usually just work on next run.