(I don't really believe the .asc files are broken; probably a local
gpg problem I don't understand)
SUCCESS! [0:44:08.338731]
+1 from me
On Fri, Nov 18, 2022 at 10:18 AM Uwe Schindler wrote:
>
> Hi,
>
> the second build succeeded. I really think it was another job running at same
> time that
What I have in mind would be to implement entirely in the
KnnVectorQuery. Since results are sorted by score, they can easily be
post-filtered there: no need to implement anything at the codec layer
I think.
On Thu, Nov 17, 2022 at 10:10 AM GitBox wrote:
>
>
> rmuir commented on PR #11946:
> URL:
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
I haven't looked at Lucene smoketester code but I would assume its
similar to Solr - SOLR-16132 (
https://github.com/apache/solr/commit/0cfef740617cc40585e3121e0b41e5cc8002471f)
fixed some of the gpg-agent stuff recently.
Kevin Risden
On Fri, Nov 18, 2022 at 10:07 AM Uwe Schindler wrote:
> I
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
I think he is running this from jenkins job. I suspect agents have
"stacked up" over time take a look with "ps". Every time i run the
smoketester, it "leaks" at least an agent or two.
On Fri, Nov 18, 2022 at 9:48 AM Adrien Grand wrote:
>
> Reading Uwe's error message more carefully, I had
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,
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:
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"
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) " key
(which I assume you would be ok with)?
On Fri, Nov 18, 2022 at 2:18 PM Uwe Schindler wrote:
> I am
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
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
Hi all,
there's a label on our Github 'vector-based-search' (
https://github.com/apache/lucene/issues?q=label%3Avector-based-search+is%3Aclosed
).
I just gave it a pass and tagged most of the issues I believe are related.
If we all do this little extra effort of tagging when creating the issue,
> I think, if smoke tester knows the version, it could just check the staging
> repo, too. It is just another URL!?
Yes, it's an URL.
> If the staging repository on nexus has a hash inside (I think they have),
> maybe the release wizard places some file with the URL of the actual staging
>
I think, if smoke tester knows the version, it could just check the
staging repo, too. It is just another URL!? If the staging repository on
nexus has a hash inside (I think they have), maybe the release wizard
places some file with the URL of the actual staging repo into the folder?
Uwe
Am
15 matches
Mail list logo
