Hi,
the second build succeeded. I really think it was another job running at
same time that also tried to communicate with GPG and used another home dir.
Log: https://jenkins.thetaphi.de/job/Lucene-Release-Tester/25/console
SUCCESS! [1:43:46.817984]
Finished: SUCCESS
After jenkins finished the job it killed all child processes and all
agents are gone.
In the meantime I also did some manual checks: Running Luke from windows
with whitespace in dir worked and I was able to open my test index. I
also started with Java 19 and --enable-preview and the Luke log showed
that it uses the new MMapDire impl.
I correct my previous vote: ++1 to release. 😁
Uwe
Am 18.11.2022 um 16:06 schrieb Uwe Schindler:
I had also seen this message. My guess: Another build was running in
Jenkins that also spawned an agent with different home dir! I think
Robert already talked about this. We should kill the agents
before/after we have used them.
Uwe
Am 18.11.2022 um 15:47 schrieb Adrien Grand:
Reading Uwe's error message more carefully, I had first assumed that
the GPG failure was due to the lack of an ultimately trusted
signature, but it seems like it's due to "can't connect to the agent:
IPC connect call failed" actually, which suggests an issue with the
GPG agent?
On Fri, Nov 18, 2022 at 3:00 PM Michael Sokolov <msoko...@gmail.com>
wrote:
I got this message when initially downloading the artifacts:
Downloading
https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db/lucene/lucene-9.4.2-src.tgz.asc
File:
/tmp/smoke_lucene_9.4.2_858d9b437047a577fa9457089afff43eefa461db/lucene.lucene-9.4.2-src.tgz.gpg.verify.log
verify trust
GPG: gpg: WARNING: This key is not certified with a trusted
signature!
is it related?
On Fri, Nov 18, 2022 at 8:43 AM Uwe Schindler <u...@thetaphi.de>
wrote:
>
> The problem is: it is working like this since years - the 9.4.1
release worked fine. No change!
>
> And I can't configure this because GPG uses its own home
directory setup by smoke tester (see paths below). So it should
not look anywhere else? In addition "gpg: no ultimately trusted
keys found" is just a warning, it should not cause gpg to exit.
>
> Also why does it only happens at the time of Maven? It checks
signatures before, too. This is why I restarted the build:
https://jenkins.thetaphi.de/job/Lucene-Release-Tester/25/console
(still running)
>
> Uwe
>
> Am 18.11.2022 um 14:21 schrieb Adrien Grand:
>
> Uwe, the error message suggests that Policeman Jenkins is not
ultimately trusting any of the keys. Does it work if you
configure it to ultimately trust your "Uwe Schindler (CODE
SIGNING KEY) <uschind...@apache.org>" key (which I assume you
would be ok with)?
>
> On Fri, Nov 18, 2022 at 2:18 PM Uwe Schindler <u...@thetaphi.de>
wrote:
>>
>> I am restarting the build, maybe it was some hickup.
Interestingly it only failed for the Maven dependencies. P.S.:
Why does it import the key file over and over? It would be enough
to do this once at beginning of smoker.
>>
>> Uwe
>>
>> Am 18.11.2022 um 14:12 schrieb Uwe Schindler:
>>
>> Hi,
>>
>> I get a failure because your key is somehow rejected by GPG
(Ubuntu 22.04):
>>
>> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/24/console
>>
>> verify maven artifact sigs command "gpg --homedir
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg
--import
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/KEYS"
failed: gpg: keybox
'/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/pubring.kbx'
created gpg:
/home/jenkins/workspace/Lucene-Release-Tester/smoketmp/lucene.gpg/trustdb.gpg:
trustdb created gpg: key B83EA82A0AFCEE7C: public key "Yonik
Seeley <yo...@apache.org>" imported gpg: can't connect to the
agent: IPC connect call failed gpg: key E48025ED13E57FFC: public
key "Upayavira <u...@odoko.co.uk>" imported [...] gpg: key
051A0FAF76BC6507: public key "Adrien Grand (CODE SIGNING KEY)
<jpou...@apache.org>" imported [...] gpg: key 32423B0E264B5CBA:
public key "Julie Tibshirani (New code signing key)
<juliet...@apache.org>" imported gpg: Total number processed: 62
gpg: imported: 62 gpg: no ultimately trusted keys found
>> It looks like for others it succeeds? No idea why. Maybe
Ubuntu 22.04 has a too-new GPG or it needs to use gpg2?
>>
>> -1 to release until this is sorted out.
>>
>> Uwe
>>
>> Am 17.11.2022 um 15:18 schrieb Adrien Grand:
>>
>> Please vote for release candidate 1 for Lucene 9.4.2
>>
>> The artifacts can be downloaded from:
>>
https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>>
>> You can run the smoke tester directly with this command:
>>
>> python3 -u dev-tools/scripts/smokeTestRelease.py \
>>
https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>>
>> The vote will be open for at least 72 hours i.e. until
2022-11-20 15:00 UTC.
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>> Here is my +1.
>>
>> --
>> Adrien
>>
>> --
>> Uwe Schindler
>> Achterdiek 19, D-28357 Bremen
>> https://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>> --
>> Uwe Schindler
>> Achterdiek 19, D-28357 Bremen
>> https://www.thetaphi.de
>> eMail: u...@thetaphi.de
>
>
>
> --
> Adrien
>
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
--
Adrien
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:u...@thetaphi.de
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:u...@thetaphi.de
