[ 
https://issues.apache.org/jira/browse/LUCENE-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Drob resolved LUCENE-9412.
-------------------------------
    Resolution: Won't Fix

> Repro Jenkins jobs failing to fetch build output
> ------------------------------------------------
>
>                 Key: LUCENE-9412
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9412
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: general/build
>            Reporter: Mike Drob
>            Assignee: Mike Drob
>            Priority: Major
>
> We get a python SSL error when trying to fetch the output of a previous job, 
> https://builds.apache.org/job/Lucene-Solr-repro-Java11/1163/console
> It's an easy fix to not verify the certificate on the other end, but opening 
> this for two reasons:
> 1) maybe there is something INFRA can do w.r.t. fixing either the cert for 
> the Jenkins machines or the accepted CAs on the python install
> 2) document it here so that when somebody looks at the code later they'll 
> have a reference for why it looks like we're doing something insecure.
> {noformat}
> Traceback (most recent call last):
>   File "dev-tools/scripts/reproduceJenkinsFailures.py", line 309, in <module>
>     main()
>   File "dev-tools/scripts/reproduceJenkinsFailures.py", line 250, in main
>     tests = fetchAndParseJenkinsLog(config.url, numRetries = 2)
>   File "dev-tools/scripts/reproduceJenkinsFailures.py", line 132, in 
> fetchAndParseJenkinsLog
>     raise RuntimeError('ERROR: fetching %s : %s' % (url, e))
> RuntimeError: ERROR: fetching 
> https://builds.apache.org/job/Lucene-Solr-NightlyTests-master/2228/consoleText
>  : <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed 
> (_ssl.c:645)>
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to