Logs available at https://issues.apache.org/jira/browse/SOLR-15473

On Thu, Jun 10, 2021 at 11:54 PM Robert Muir <[email protected]> wrote:
>
> Thank you Mayya for working on the release!
>
> I'm sorry, but I have a -1 as the smoke tester fails on my machine:
>
> TLDR:
>    [junit4] Tests with failures [seed: FB8461777F8A9E7D] (first 10 out of 26):
>    [junit4]   -
> org.apache.solr.cloud.api.collections.TestHdfsCloudBackupRestore
> (suite)
>    [junit4]   - org.apache.solr.update.TestHdfsUpdateLog (suite)
>    [junit4]   - org.apache.solr.store.hdfs.HdfsDirectoryTest (suite)
>    [junit4]   - org.apache.solr.cloud.SolrCLIZkUtilsTest.testDownconfig
>    [junit4]   - org.apache.solr.cloud.SolrCLIZkUtilsTest.testLs
>    [junit4]   - org.apache.solr.cloud.SolrCLIZkUtilsTest.testRm
>    [junit4]   - org.apache.solr.cloud.SolrCLIZkUtilsTest.testCp
>    [junit4]   - org.apache.solr.cloud.SolrCLIZkUtilsTest.testMv
>    [junit4]   - org.apache.solr.cloud.SolrCLIZkUtilsTest.testUpconfig
>    [junit4]   -
> org.apache.solr.cloud.api.collections.HdfsCloudIncrementalBackupTest
> (suite)
>
> A few notes below, commands, repos, branches, etc I used to get the
> smoker to run on my machine, maybe it helps others with reproduction:
>
> think:lucene-solr[branch_8_9]$
> JAVA_HOME=/home/rmuir/Downloads/jdk8u282-b08 python3 -u
> dev-tools/scripts/smokeTestRelease.py
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.9.0-RC1-rev05c8a6f0163fe4c330e93775e8e91f3ab66a3f80
> Revision: 05c8a6f0163fe4c330e93775e8e91f3ab66a3f80
> Java 1.8 JAVA_HOME=/home/rmuir/Downloads/jdk8u282-b08
> NOTE: output encoding is utf-8
>
> ...
>
> I got a few warnings related to GPG signing, such as:
>
>  verify trust
>       GPG: gpg: WARNING: This key is not certified with a trusted signature!
>
> FWIW I think the issue is, Only Jim has signed your key, but JIm's key
> is only signed by Martijn's expired key, so there's no good web of
> trust (sorry in advance, if i debugged the gpg shit wrong here). Let's
> consider a followup improvement to beef up the trust amongst
> committers, so that users have improved confidence in the artifacts:
> we can probably plan this on slack or whatever is trendy now. I think
> the TLDR is, we all confirm we are the people we think we are. Happy
> to hold up my driver's license to the screen or whatever is needed,
> I'm already fully compromised :)
>
> https://www.cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html
>
> ...
>
> As far as solr tests, they ran for hours and hours. I checked with
> tools such as 'top' and 'jstack' to try to confirm they were still
> doing stuff. But even on my 2-core laptop, I monitored CPU usage of ~
> 30% while tests were being run, seems they were sleeping... and
> honestly most of that cpu usage was my pandora window playing reggae,
> attempt to drown out all the cicadas...
>
> I don't have much to offer here. I guess they pass on someone's
> machine, but they don't pass here. They print so many MB of output
> that they overflow my terminal's scrollback buffer... so I'm not even
> sure what I can do to help debug the situation. If there are text
> files created by the smoketester that I could upload to help out, will
> be happy to do so.
>
> On Thu, Jun 10, 2021 at 10:14 PM Mayya Sharipova
> <[email protected]> wrote:
> >
> > Please vote for release candidate 1 for Lucene/Solr 8.9.0
> >
> > The artifacts can be downloaded from:
> > https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.9.0-RC1-rev05c8a6f0163fe4c330e93775e8e91f3ab66a3f80
> >
> > 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-solr-8.9.0-RC1-rev05c8a6f0163fe4c330e93775e8e91f3ab66a3f80
> >
> > The vote will be open for at least 72 hours i.e. until 2021-06-16 02:00 UTC.
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Here is my +1
> > SUCCESS! [0:01:43.815224]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to