You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Joel Bernstein <jo...@gmail.com> on 2017/04/19 19:36:50 UTC
Issue with 6.5.1 RC2
I started working on 6.5.1 RC2. I ran the following:
python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
/tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
I believe this is same basic command I used for RC1. But this time I got a
new error. At first I thought it might be incorrect keystore password but I
changed it and it is correct. Any thoughts what the issue is?
Traceback (most recent call last):
File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
main()
File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
rev = prepare(c.root, c.version, c.key_id, c.key_password)
File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
checkDOAPfiles(version)
File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
checkDOAPfiles
distpage = load(url)
File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
content = urllib.request.urlopen(urlString).read().decode('utf-8')
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
line 223, in urlopen
return opener.open(url, data, timeout)
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
line 526, in open
response = self._open(req, data)
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
line 544, in _open
'_open', req)
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
line 504, in _call_chain
result = func(*args)
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
line 1361, in https_open
context=self._context, check_hostname=self._check_hostname)
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
line 1320, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
certificate verify failed (_ssl.c:749)>
Joel Bernstein
http://joelsolr.blogspot.com/
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
I'll pull and run precommit before creating the RC.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
> Interesting the entire release process completed without complaining.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
>
>> The unused import was the only problem; I’ve removed it on branch_6_5.
>>
>> Sorry, hope I didn’t cause a delay in the release process.
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>> > On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
>> >
>> > Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I
>> forgot to run precommit. Doing so now.
>> >
>> > --
>> > Steve
>> > www.lucidworks.com
>> >
>> >> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
>> >>
>> >> Done.
>> >>
>> >> --
>> >> Steve
>> >> www.lucidworks.com
>> >>
>> >>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
>> >>>
>> >>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>> >>>
>> >>> --
>> >>> Steve
>> >>> www.lucidworks.com
>> >>>
>> >>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>
>> >>>> I'm OK with restarting RC2. Let me know when you finish the back
>> port.
>> >>>>
>> >>>> Joel Bernstein
>> >>>> http://joelsolr.blogspot.com/
>> >>>>
>> >>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>> Joel,
>> >>>>
>> >>>> I know you’re in-process with RC2, but if you have to restart for
>> some reason, I’d like to include SOLR-10527.
>> >>>>
>> >>>> --
>> >>>> Steve
>> >>>> www.lucidworks.com
>> >>>>
>> >>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>>
>> >>>>> I also had to change the smoke tester because of the SSL issue.
>> Which in theory means everyone else will have to as well. I'm pushing out
>> my changes to branch_6_5, so people can just update their branch before
>> running the smoke tester.
>> >>>>>
>> >>>>> Joel Bernstein
>> >>>>> http://joelsolr.blogspot.com/
>> >>>>>
>> >>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>> Ok, I had to push out three changes to the branch but I seemed to
>> have moved passed this issue.
>> >>>>>
>> >>>>> Joel Bernstein
>> >>>>> http://joelsolr.blogspot.com/
>> >>>>>
>> >>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>> I'll push out the changes and then revert. Hopefully the changes
>> will do the trick after they've been pushed.
>> >>>>>
>> >>>>> Joel Bernstein
>> >>>>> http://joelsolr.blogspot.com/
>> >>>>>
>> >>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>>> Yeah, that is a sucky part of this: you want to make modifications
>> on the release branch, but you can’t test unless you commit (and push).
>> >>>>>
>> >>>>> Another alternative: make modifications in another checkout, then
>> invoke the script with from an unmodified source tree.
>> >>>>>
>> >>>>> e.g.:
>> >>>>>
>> >>>>> cd ..
>> >>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your
>> checkout dir
>> >>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>> >>>>> cd lucene-solr
>> >>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>> …
>> >>>>>
>> >>>>> (a shorter form of that is to make a copy the script alone and
>> invoke the modified version from your checkout)
>> >>>>>
>> >>>>> --
>> >>>>> Steve
>> >>>>> www.lucidworks.com
>> >>>>>
>> >>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>>>
>> >>>>>> Ha, that doesn't work either. Now I get this error:
>> >>>>>>
>> >>>>>> RuntimeError: There are unpushed commits - "git log
>> origin/branch_6_5.." output is:
>> >>>>>>
>> >>>>>> So, I'm going to have to push this out.
>> >>>>>>
>> >>>>>> Let's first decide if this makes sense as the way forward.
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> Joel Bernstein
>> >>>>>> http://joelsolr.blogspot.com/
>> >>>>>>
>> >>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>> Steve, when I change the script to turn off verification I get the
>> following error:
>> >>>>>> RuntimeError: git clone is dirty:
>> >>>>>>
>> >>>>>> So as part of the work around I think I'm going to have to commit
>> locally and then revert locally. Does that make sense to you as the way
>> forward?
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> Joel Bernstein
>> >>>>>> http://joelsolr.blogspot.com/
>> >>>>>>
>> >>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>> arafalov@gmail.com> wrote:
>> >>>>>> Could it be anything to do with the fact that the signer is
>> Semantic
>> >>>>>> and they are being actively distrusted by - at least - Google:
>> >>>>>> http://www.securityweek.com/google-stops-trusting-symantec-
>> issued-certificates
>> >>>>>>
>> >>>>>> Regards,
>> >>>>>> Alex.
>> >>>>>> ----
>> >>>>>> http://www.solr-start.com/ - Resources for Solr users, new and
>> experienced
>> >>>>>>
>> >>>>>>
>> >>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert
>> verification
>> >>>>>>> was something that was integral to the process.
>> >>>>>>>
>> >>>>>>> Joel Bernstein
>> >>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>
>> >>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>>>>>>
>> >>>>>>>> Hi Joel,
>> >>>>>>>>
>> >>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>> >>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been
>> enabled on
>> >>>>>>>> archive.apache.org?
>> >>>>>>>>
>> >>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
>> alternative to
>> >>>>>>>> urllib):
>> >>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#wh
>> at-are-hostname-doesn-t-match-errors>
>> >>>>>>>>
>> >>>>>>>> Short term, you could turn off certificate verification. The
>> bottom
>> >>>>>>>> answer here uses the same lib as the script (urllib instead of
>> urllib2,
>> >>>>>>>> which is assumed in the other answers on the page), to turn off
>> certificate
>> >>>>>>>> verification:
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-
>> certicate-validation-urllib2>
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>> Steve
>> >>>>>>>> www.lucidworks.com
>> >>>>>>>>
>> >>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>>>>>>
>> >>>>>>>>> It appears that it's failing on verifying the SSL cert for
>> >>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> Joel Bernstein
>> >>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>
>> >>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>> joelsolr@gmail.com>
>> >>>>>>>>> wrote:
>> >>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>> >>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>> --push-local
>> >>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>> >>>>>>>>>
>> >>>>>>>>> I believe this is same basic command I used for RC1. But this
>> time I got
>> >>>>>>>>> a new error. At first I thought it might be incorrect keystore
>> password but
>> >>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
>> >>>>>>>>>
>> >>>>>>>>> Traceback (most recent call last):
>> >>>>>>>>>
>> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in
>> <module>
>> >>>>>>>>>
>> >>>>>>>>> main()
>> >>>>>>>>>
>> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in
>> main
>> >>>>>>>>>
>> >>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
>> >>>>>>>>>
>> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in
>> prepare
>> >>>>>>>>>
>> >>>>>>>>> checkDOAPfiles(version)
>> >>>>>>>>>
>> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
>> >>>>>>>>> checkDOAPfiles
>> >>>>>>>>>
>> >>>>>>>>> distpage = load(url)
>> >>>>>>>>>
>> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in
>> load
>> >>>>>>>>>
>> >>>>>>>>> content = urllib.request.urlopen(urlStri
>> ng).read().decode('utf-8')
>> >>>>>>>>>
>> >>>>>>>>> File
>> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> >>>>>>>>> line 223, in urlopen
>> >>>>>>>>>
>> >>>>>>>>> return opener.open(url, data, timeout)
>> >>>>>>>>>
>> >>>>>>>>> File
>> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> >>>>>>>>> line 526, in open
>> >>>>>>>>>
>> >>>>>>>>> response = self._open(req, data)
>> >>>>>>>>>
>> >>>>>>>>> File
>> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> >>>>>>>>> line 544, in _open
>> >>>>>>>>>
>> >>>>>>>>> '_open', req)
>> >>>>>>>>>
>> >>>>>>>>> File
>> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> >>>>>>>>> line 504, in _call_chain
>> >>>>>>>>>
>> >>>>>>>>> result = func(*args)
>> >>>>>>>>>
>> >>>>>>>>> File
>> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> >>>>>>>>> line 1361, in https_open
>> >>>>>>>>>
>> >>>>>>>>> context=self._context, check_hostname=self._check_hostname)
>> >>>>>>>>>
>> >>>>>>>>> File
>> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> >>>>>>>>> line 1320, in do_open
>> >>>>>>>>>
>> >>>>>>>>> raise URLError(err)
>> >>>>>>>>>
>> >>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>> CERTIFICATE_VERIFY_FAILED]
>> >>>>>>>>> certificate verify failed (_ssl.c:749)>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> Joel Bernstein
>> >>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> ------------------------------------------------------------
>> ---------
>> >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>> ------------------------------------------------------------
>> ---------
>> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>> ------------------------------------------------------------
>> ---------
>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>> ------------------------------------------------------------
>> ---------
>> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>
>> >>>>
>> >>>
>> >>
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
OK, thanks.
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 2:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
>
> I've changed the files locally and will push them out.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 2:06 PM, Joel Bernstein <jo...@gmail.com> wrote:
> Steve,
>
> It looks like you haven't pushed out you changes yet, reverting my changes.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 2:03 PM, Joel Bernstein <jo...@gmail.com> wrote:
> I'm on 10.10.5 (Yosemite).
>
> It could be related to the platform or just something odd with python 3.6.1
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 2:00 PM, Steve Rowe <sa...@gmail.com> wrote:
> FYI I got SUCCESS! [0:36:33.390707] from my reverted-SSL-changes smokeTestRelease.py on Python 3.4.2 against the 6.5.1RC2 URL. (macOS/Python 3.5.1 reverted smoke tester is still running.)
>
> It may be the case that you’re missing root certificates that I have (on both Linux and macOS), and that’s the reason SSL validation is failing for you.
>
> What platform are you on? IIRC some Linux distros have ways of updating root certificate stores. (I’ve never had to do that myself though.)
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 1:54 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > I just ran the smoke tester and it failed in the part of code that I hadn't suppressed the SSL validation. So it's still an issue with my setup.
> >
> > I could try another version of python and see if that is the issue.
> >
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 1:47 PM, Steve Rowe <sa...@gmail.com> wrote:
> > AFAICT that error occurs very early in the smoke test process, with the first attempt to download the directory listing at the release URL. I’m running the reverted-SSL-changes smokeTestRelease.py on both Python 3.4.2 (Linux) and 3.5.1 (macOS), and both are way past that.
> >
> > Would you mind trying to run the smoke tester today after reverting your SSL changes? (Maybe it was a temporary problem for some reason.) AFAICT it will fail fast for you.
> >
> > I’m not sure if it makes sense to call the release vote yet, since the smoke tester as committed to branch_6_5 doesn’t work for you or for people with Python < 3.4.3. If the problem turns out to be a transient one for you, then I think we should revert your SSL changes to smokeTestRelease.py on branch_6_5 and respin.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 1:35 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >
> > > Here is the error from the smoke test:
> > >
> > > Traceback (most recent call last):
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 1483, in <module>
> > >
> > > main()
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 1427, in main
> > >
> > > smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir, c.is_signed, ' '.join(c.test_args))
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 1449, in smokeTest
> > >
> > > for text, subURL in getDirEntries(baseURL):
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 604, in getDirEntries
> > >
> > > links = getHREFs(urlString)
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 94, in getHREFs
> > >
> > > h.request('HEAD', url.path)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1239, in request
> > >
> > > self._send_request(method, url, body, headers, encode_chunked)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1285, in _send_request
> > >
> > > self.endheaders(body, encode_chunked=encode_chunked)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1234, in endheaders
> > >
> > > self._send_output(message_body, encode_chunked=encode_chunked)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1026, in _send_output
> > >
> > > self.send(msg)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 964, in send
> > >
> > > self.connect()
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1400, in connect
> > >
> > > server_hostname=server_hostname)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 401, in wrap_socket
> > >
> > > _context=self, _session=session)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 808, in __init__
> > >
> > > self.do_handshake()
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 1061, in do_handshake
> > >
> > > self._sslobj.do_handshake()
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 683, in do_handshake
> > >
> > > self._sslobj.do_handshake()
> > >
> > > ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)
> > >
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Thu, Apr 20, 2017 at 1:31 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > That’s the error you posted for buildAndPushRelease.py - are you saying that you got identical errors for both?
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > > > On Apr 20, 2017, at 1:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >
> > > > Python 3.6.1
> > > >
> > > >
> > > > Joel Bernstein
> > > > http://joelsolr.blogspot.com/
> > > >
> > > > On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > This was the error:
> > > >
> > > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 504, in _call_chain
> > > >
> > > > result = func(*args)
> > > >
> > > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 1361, in https_open
> > > >
> > > > context=self._context, check_hostname=self._check_hostname)
> > > >
> > > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 1320, in do_open
> > > >
> > > > raise URLError(err)
> > > >
> > > > urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)>
> > > >
> > > >
> > > >
> > > > Perhaps the error was only local to my machine. But I didn't have this error when building RC1
> > > >
> > > >
> > > >
> > > >
> > > > Joel Bernstein
> > > > http://joelsolr.blogspot.com/
> > > >
> > > > On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > Joel,
> > > >
> > > > I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t see any problems so far when I run it with my Python 3.4.2 with the 6.5.1RC2 URL. (Still in progress; Lucene distributions have downloaded so far.)
> > > >
> > > > What was the error that caused you to make the SSL changes to smokeTestRelease.py? And what version of Python are you using?
> > > >
> > > > --
> > > > Steve
> > > > www.lucidworks.com
> > > >
> > > > > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >
> > > > > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the first that supports the changes you made, so the smoke tester is failing for me:
> > > > >
> > > > > -----
> > > > > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
> > > > > content = urllib.request.urlopen(urlString, context=ctx).read().decode('utf-8')
> > > > > TypeError: urlopen() got an unexpected keyword argument ‘context’
> > > > > ------
> > > > >
> > > > > I’ll install a newer Python.
> > > > >
> > > > > --
> > > > > Steve
> > > > > www.lucidworks.com
> > > > >
> > > > >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>
> > > > >> thanks
> > > > >>
> > > > >> Joel Bernstein
> > > > >> http://joelsolr.blogspot.com/
> > > > >>
> > > > >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >> I’ll take a look.
> > > > >>
> > > > >> --
> > > > >> Steve
> > > > >> www.lucidworks.com
> > > > >>
> > > > >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>
> > > > >>> I've uploaded the RC2 here https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d88652952ec3e2b3e0070/.
> > > > >>>
> > > > >>> But the smoke test breaks with SSL error in different spot when you smoke test from this URL. It's failing with a different command this time so the fix I used in other sports of smoke tester doesn't work.
> > > > >>>
> > > > >>> Steve, would you mind taking a look at this and pushing out a fix?
> > > > >>>
> > > > >>> Joel Bernstein
> > > > >>> http://joelsolr.blogspot.com/
> > > > >>>
> > > > >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>> I was thinking that if buildAndPushRelease.py can identify problems early, the RM won’t have to later redo work when a problem is found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from auto-running precommit would be worth it.
> > > > >>>
> > > > >>> But I agree that the smoke tester should be heavy, since it’s possible that the RM had weird local conditions that weren’t caught by the release production tools.
> > > > >>>
> > > > >>> --
> > > > >>> Steve
> > > > >>> www.lucidworks.com
> > > > >>>
> > > > >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>
> > > > >>>> They are both quite long processes. Perhaps we should look at eliminating some of the overlap?
> > > > >>>>
> > > > >>>> Since the smokeTesters is run by those voting on the release maybe this should be the heavier of the two.
> > > > >>>>
> > > > >>>> Joel Bernstein
> > > > >>>> http://joelsolr.blogspot.com/
> > > > >>>>
> > > > >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>> Also, I think buildAndPushRelease.py should invoke “precommit" too, (near) where it runs 'ant clean test'.
> > > > >>>>
> > > > >>>> --
> > > > >>>> Steve
> > > > >>>> www.lucidworks.com
> > > > >>>>
> > > > >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>
> > > > >>>>> That’s bizarre.
> > > > >>>>>
> > > > >>>>> The smoke tester runs ‘ant validate’, which does *not* include "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused imports are looked for).
> > > > >>>>>
> > > > >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and “documentation-lint”.
> > > > >>>>>
> > > > >>>>> Jenkins caught this not because of the smoke tester, but rather because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like “precommit”, runs “check-working-copy”, “validate”, and “documentation-lint” (among others).
> > > > >>>>>
> > > > >>>>> I think we should change the smoke tester to look at the same things as precommit,
> > > > >>>>>
> > > > >>>>> --
> > > > >>>>> Steve
> > > > >>>>> www.lucidworks.com
> > > > >>>>>
> > > > >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>
> > > > >>>>>> Smoke testes passed as well
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> Joel Bernstein
> > > > >>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>
> > > > >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>> I guess precommit is only run as part of the smoke tester.
> > > > >>>>>>
> > > > >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>
> > > > >>>>>>> Interesting the entire release process completed without complaining.
> > > > >>>>>>>
> > > > >>>>>>> Joel Bernstein
> > > > >>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>
> > > > >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>> The unused import was the only problem; I’ve removed it on branch_6_5.
> > > > >>>>>>>
> > > > >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
> > > > >>>>>>>
> > > > >>>>>>> --
> > > > >>>>>>> Steve
> > > > >>>>>>> www.lucidworks.com
> > > > >>>>>>>
> > > > >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>>>
> > > > >>>>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
> > > > >>>>>>>>
> > > > >>>>>>>> --
> > > > >>>>>>>> Steve
> > > > >>>>>>>> www.lucidworks.com
> > > > >>>>>>>>
> > > > >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>>>>
> > > > >>>>>>>>> Done.
> > > > >>>>>>>>>
> > > > >>>>>>>>> --
> > > > >>>>>>>>> Steve
> > > > >>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>
> > > > >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>>>>>
> > > > >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > > > >>>>>>>>>>
> > > > >>>>>>>>>> --
> > > > >>>>>>>>>> Steve
> > > > >>>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the back port.
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>>>>>> Joel,
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> --
> > > > >>>>>>>>>>> Steve
> > > > >>>>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> e.g.:
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> cd ..
> > > > >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> > > > >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > > > >>>>>>>>>>>> cd lucene-solr
> > > > >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> --
> > > > >>>>>>>>>>>> Steve
> > > > >>>>>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> So, I'm going to have to push this out.
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Let's first decide if this makes sense as the way forward.
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>>> Steve, when I change the script to turn off verification I get the following error:
> > > > >>>>>>>>>>>>> RuntimeError: git clone is dirty:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> > > > >>>>>>>>>>>>> Could it be anything to do with the fact that the signer is Semantic
> > > > >>>>>>>>>>>>> and they are being actively distrusted by - at least - Google:
> > > > >>>>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Regards,
> > > > >>>>>>>>>>>>> Alex.
> > > > >>>>>>>>>>>>> ----
> > > > >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> > > > >>>>>>>>>>>>>> was something that was integral to the process.
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> Hi Joel,
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > > > >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> > > > >>>>>>>>>>>>>>> archive.apache.org?
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
> > > > >>>>>>>>>>>>>>> urllib):
> > > > >>>>>>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> Short term, you could turn off certificate verification. The bottom
> > > > >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
> > > > >>>>>>>>>>>>>>> which is assumed in the other answers on the page), to turn off certificate
> > > > >>>>>>>>>>>>>>> verification:
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> --
> > > > >>>>>>>>>>>>>>> Steve
> > > > >>>>>>>>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> > > > >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> > > > >>>>>>>>>>>>>>>> wrote:
> > > > >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > > > >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> > > > >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
> > > > >>>>>>>>>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
> > > > >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> Traceback (most recent call last):
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> main()
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> checkDOAPfiles(version)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> > > > >>>>>>>>>>>>>>>> checkDOAPfiles
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> distpage = load(url)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 223, in urlopen
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 526, in open
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> response = self._open(req, data)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 544, in _open
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> '_open', req)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 504, in _call_chain
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> result = func(*args)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 1361, in https_open
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 1320, in do_open
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> raise URLError(err)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> > > > >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> ---------------------------------------------------------------------
> > > > >>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> ---------------------------------------------------------------------
> > > > >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> ---------------------------------------------------------------------
> > > > >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> ---------------------------------------------------------------------
> > > > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>
> > > > >>>>>>>>>
> > > > >>>>>>>>
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>> ---------------------------------------------------------------------
> > > > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> ---------------------------------------------------------------------
> > > > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>> ---------------------------------------------------------------------
> > > > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>
> > > > >>>>
> > > > >>>
> > > > >>>
> > > > >>> ---------------------------------------------------------------------
> > > > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>
> > > > >>>
> > > > >>
> > > > >>
> > > > >> ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > For additional commands, e-mail: dev-help@lucene.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: dev-help@lucene.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
I've changed the files locally and will push them out.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 2:06 PM, Joel Bernstein <jo...@gmail.com> wrote:
> Steve,
>
> It looks like you haven't pushed out you changes yet, reverting my changes.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 2:03 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
>
>> I'm on 10.10.5 (Yosemite).
>>
>> It could be related to the platform or just something odd with python
>> 3.6.1
>>
>>
>>
>> Joel Bernstein
>> http://joelsolr.blogspot.com/
>>
>> On Thu, Apr 20, 2017 at 2:00 PM, Steve Rowe <sa...@gmail.com> wrote:
>>
>>> FYI I got SUCCESS! [0:36:33.390707] from my reverted-SSL-changes
>>> smokeTestRelease.py on Python 3.4.2 against the 6.5.1RC2 URL.
>>> (macOS/Python 3.5.1 reverted smoke tester is still running.)
>>>
>>> It may be the case that you’re missing root certificates that I have (on
>>> both Linux and macOS), and that’s the reason SSL validation is failing for
>>> you.
>>>
>>> What platform are you on? IIRC some Linux distros have ways of updating
>>> root certificate stores. (I’ve never had to do that myself though.)
>>>
>>> --
>>> Steve
>>> www.lucidworks.com
>>>
>>> > On Apr 20, 2017, at 1:54 PM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> >
>>> > I just ran the smoke tester and it failed in the part of code that I
>>> hadn't suppressed the SSL validation. So it's still an issue with my setup.
>>> >
>>> > I could try another version of python and see if that is the issue.
>>> >
>>> >
>>> >
>>> > Joel Bernstein
>>> > http://joelsolr.blogspot.com/
>>> >
>>> > On Thu, Apr 20, 2017 at 1:47 PM, Steve Rowe <sa...@gmail.com> wrote:
>>> > AFAICT that error occurs very early in the smoke test process, with
>>> the first attempt to download the directory listing at the release URL.
>>> I’m running the reverted-SSL-changes smokeTestRelease.py on both Python
>>> 3.4.2 (Linux) and 3.5.1 (macOS), and both are way past that.
>>> >
>>> > Would you mind trying to run the smoke tester today after reverting
>>> your SSL changes? (Maybe it was a temporary problem for some reason.)
>>> AFAICT it will fail fast for you.
>>> >
>>> > I’m not sure if it makes sense to call the release vote yet, since the
>>> smoke tester as committed to branch_6_5 doesn’t work for you or for people
>>> with Python < 3.4.3. If the problem turns out to be a transient one for
>>> you, then I think we should revert your SSL changes to smokeTestRelease.py
>>> on branch_6_5 and respin.
>>> >
>>> > --
>>> > Steve
>>> > www.lucidworks.com
>>> >
>>> > > On Apr 20, 2017, at 1:35 PM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> > >
>>> > > Here is the error from the smoke test:
>>> > >
>>> > > Traceback (most recent call last):
>>> > >
>>> > > File "dev-tools/scripts/smokeTestRelease.py", line 1483, in
>>> <module>
>>> > >
>>> > > main()
>>> > >
>>> > > File "dev-tools/scripts/smokeTestRelease.py", line 1427, in main
>>> > >
>>> > > smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir,
>>> c.is_signed, ' '.join(c.test_args))
>>> > >
>>> > > File "dev-tools/scripts/smokeTestRelease.py", line 1449, in
>>> smokeTest
>>> > >
>>> > > for text, subURL in getDirEntries(baseURL):
>>> > >
>>> > > File "dev-tools/scripts/smokeTestRelease.py", line 604, in
>>> getDirEntries
>>> > >
>>> > > links = getHREFs(urlString)
>>> > >
>>> > > File "dev-tools/scripts/smokeTestRelease.py", line 94, in getHREFs
>>> > >
>>> > > h.request('HEAD', url.path)
>>> > >
>>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>>> line 1239, in request
>>> > >
>>> > > self._send_request(method, url, body, headers, encode_chunked)
>>> > >
>>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>>> line 1285, in _send_request
>>> > >
>>> > > self.endheaders(body, encode_chunked=encode_chunked)
>>> > >
>>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>>> line 1234, in endheaders
>>> > >
>>> > > self._send_output(message_body, encode_chunked=encode_chunked)
>>> > >
>>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>>> line 1026, in _send_output
>>> > >
>>> > > self.send(msg)
>>> > >
>>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>>> line 964, in send
>>> > >
>>> > > self.connect()
>>> > >
>>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>>> line 1400, in connect
>>> > >
>>> > > server_hostname=server_hostname)
>>> > >
>>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
>>> line 401, in wrap_socket
>>> > >
>>> > > _context=self, _session=session)
>>> > >
>>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
>>> line 808, in __init__
>>> > >
>>> > > self.do_handshake()
>>> > >
>>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
>>> line 1061, in do_handshake
>>> > >
>>> > > self._sslobj.do_handshake()
>>> > >
>>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
>>> line 683, in do_handshake
>>> > >
>>> > > self._sslobj.do_handshake()
>>> > >
>>> > > ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
>>> failed (_ssl.c:749)
>>> > >
>>> > >
>>> > > Joel Bernstein
>>> > > http://joelsolr.blogspot.com/
>>> > >
>>> > > On Thu, Apr 20, 2017 at 1:31 PM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> > > That’s the error you posted for buildAndPushRelease.py - are you
>>> saying that you got identical errors for both?
>>> > >
>>> > > --
>>> > > Steve
>>> > > www.lucidworks.com
>>> > >
>>> > > > On Apr 20, 2017, at 1:28 PM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> > > >
>>> > > > Python 3.6.1
>>> > > >
>>> > > >
>>> > > > Joel Bernstein
>>> > > > http://joelsolr.blogspot.com/
>>> > > >
>>> > > > On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > This was the error:
>>> > > >
>>> > > > File "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py", line 504, in
>>> _call_chain
>>> > > >
>>> > > > result = func(*args)
>>> > > >
>>> > > > File "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py", line 1361, in
>>> https_open
>>> > > >
>>> > > > context=self._context, check_hostname=self._check_hostname)
>>> > > >
>>> > > > File "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py", line 1320, in
>>> do_open
>>> > > >
>>> > > > raise URLError(err)
>>> > > >
>>> > > > urllib.error.URLError: <urlopen error [SSL:
>>> CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)>
>>> > > >
>>> > > >
>>> > > >
>>> > > > Perhaps the error was only local to my machine. But I didn't have
>>> this error when building RC1
>>> > > >
>>> > > >
>>> > > >
>>> > > >
>>> > > > Joel Bernstein
>>> > > > http://joelsolr.blogspot.com/
>>> > > >
>>> > > > On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> > > > Joel,
>>> > > >
>>> > > > I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t
>>> see any problems so far when I run it with my Python 3.4.2 with the
>>> 6.5.1RC2 URL. (Still in progress; Lucene distributions have downloaded so
>>> far.)
>>> > > >
>>> > > > What was the error that caused you to make the SSL changes to
>>> smokeTestRelease.py? And what version of Python are you using?
>>> > > >
>>> > > > --
>>> > > > Steve
>>> > > > www.lucidworks.com
>>> > > >
>>> > > > > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> > > > >
>>> > > > > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the
>>> first that supports the changes you made, so the smoke tester is failing
>>> for me:
>>> > > > >
>>> > > > > -----
>>> > > > > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
>>> > > > > content = urllib.request.urlopen(urlString,
>>> context=ctx).read().decode('utf-8')
>>> > > > > TypeError: urlopen() got an unexpected keyword argument ‘context’
>>> > > > > ------
>>> > > > >
>>> > > > > I’ll install a newer Python.
>>> > > > >
>>> > > > > --
>>> > > > > Steve
>>> > > > > www.lucidworks.com
>>> > > > >
>>> > > > >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>
>>> > > > >> thanks
>>> > > > >>
>>> > > > >> Joel Bernstein
>>> > > > >> http://joelsolr.blogspot.com/
>>> > > > >>
>>> > > > >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> > > > >> I’ll take a look.
>>> > > > >>
>>> > > > >> --
>>> > > > >> Steve
>>> > > > >> www.lucidworks.com
>>> > > > >>
>>> > > > >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>>
>>> > > > >>> I've uploaded the RC2 here https://dist.apache.org/repos/
>>> dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62
>>> d88652952ec3e2b3e0070/.
>>> > > > >>>
>>> > > > >>> But the smoke test breaks with SSL error in different spot
>>> when you smoke test from this URL. It's failing with a different command
>>> this time so the fix I used in other sports of smoke tester doesn't work.
>>> > > > >>>
>>> > > > >>> Steve, would you mind taking a look at this and pushing out a
>>> fix?
>>> > > > >>>
>>> > > > >>> Joel Bernstein
>>> > > > >>> http://joelsolr.blogspot.com/
>>> > > > >>>
>>> > > > >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> > > > >>> I was thinking that if buildAndPushRelease.py can identify
>>> problems early, the RM won’t have to later redo work when a problem is
>>> found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop
>>> anyway) from auto-running precommit would be worth it.
>>> > > > >>>
>>> > > > >>> But I agree that the smoke tester should be heavy, since it’s
>>> possible that the RM had weird local conditions that weren’t caught by the
>>> release production tools.
>>> > > > >>>
>>> > > > >>> --
>>> > > > >>> Steve
>>> > > > >>> www.lucidworks.com
>>> > > > >>>
>>> > > > >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>>>
>>> > > > >>>> They are both quite long processes. Perhaps we should look at
>>> eliminating some of the overlap?
>>> > > > >>>>
>>> > > > >>>> Since the smokeTesters is run by those voting on the release
>>> maybe this should be the heavier of the two.
>>> > > > >>>>
>>> > > > >>>> Joel Bernstein
>>> > > > >>>> http://joelsolr.blogspot.com/
>>> > > > >>>>
>>> > > > >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <
>>> sarowe@gmail.com> wrote:
>>> > > > >>>> Also, I think buildAndPushRelease.py should invoke
>>> “precommit" too, (near) where it runs 'ant clean test'.
>>> > > > >>>>
>>> > > > >>>> --
>>> > > > >>>> Steve
>>> > > > >>>> www.lucidworks.com
>>> > > > >>>>
>>> > > > >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> > > > >>>>>
>>> > > > >>>>> That’s bizarre.
>>> > > > >>>>>
>>> > > > >>>>> The smoke tester runs ‘ant validate’, which does *not*
>>> include "documentation-lint” (which includes "-ecj-javadoc-lint”, where
>>> unused imports are looked for).
>>> > > > >>>>>
>>> > > > >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”,
>>> “validate”, and “documentation-lint”.
>>> > > > >>>>>
>>> > > > >>>>> Jenkins caught this not because of the smoke tester, but
>>> rather because the “nightly-smoke” task it uses runs “-jenkins-base”,
>>> which, like “precommit”, runs “check-working-copy”, “validate”, and
>>> “documentation-lint” (among others).
>>> > > > >>>>>
>>> > > > >>>>> I think we should change the smoke tester to look at the
>>> same things as precommit,
>>> > > > >>>>>
>>> > > > >>>>> --
>>> > > > >>>>> Steve
>>> > > > >>>>> www.lucidworks.com
>>> > > > >>>>>
>>> > > > >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>>>>>
>>> > > > >>>>>> Smoke testes passed as well
>>> > > > >>>>>>
>>> > > > >>>>>>
>>> > > > >>>>>> Joel Bernstein
>>> > > > >>>>>> http://joelsolr.blogspot.com/
>>> > > > >>>>>>
>>> > > > >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <
>>> sarowe@gmail.com> wrote:
>>> > > > >>>>>> I guess precommit is only run as part of the smoke tester.
>>> > > > >>>>>>
>>> > > > >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>>>>>>
>>> > > > >>>>>>> Interesting the entire release process completed without
>>> complaining.
>>> > > > >>>>>>>
>>> > > > >>>>>>> Joel Bernstein
>>> > > > >>>>>>> http://joelsolr.blogspot.com/
>>> > > > >>>>>>>
>>> > > > >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <
>>> sarowe@gmail.com> wrote:
>>> > > > >>>>>>> The unused import was the only problem; I’ve removed it on
>>> branch_6_5.
>>> > > > >>>>>>>
>>> > > > >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
>>> > > > >>>>>>>
>>> > > > >>>>>>> --
>>> > > > >>>>>>> Steve
>>> > > > >>>>>>> www.lucidworks.com
>>> > > > >>>>>>>
>>> > > > >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> > > > >>>>>>>>
>>> > > > >>>>>>>> Crap, Jenkins found an unused import in my commit on
>>> branch_6_5 :(. I forgot to run precommit. Doing so now.
>>> > > > >>>>>>>>
>>> > > > >>>>>>>> --
>>> > > > >>>>>>>> Steve
>>> > > > >>>>>>>> www.lucidworks.com
>>> > > > >>>>>>>>
>>> > > > >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <
>>> sarowe@gmail.com> wrote:
>>> > > > >>>>>>>>>
>>> > > > >>>>>>>>> Done.
>>> > > > >>>>>>>>>
>>> > > > >>>>>>>>> --
>>> > > > >>>>>>>>> Steve
>>> > > > >>>>>>>>> www.lucidworks.com
>>> > > > >>>>>>>>>
>>> > > > >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <
>>> sarowe@gmail.com> wrote:
>>> > > > >>>>>>>>>>
>>> > > > >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5
>>> now.
>>> > > > >>>>>>>>>>
>>> > > > >>>>>>>>>> --
>>> > > > >>>>>>>>>> Steve
>>> > > > >>>>>>>>>> www.lucidworks.com
>>> > > > >>>>>>>>>>
>>> > > > >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>>>>>>>>>>
>>> > > > >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you
>>> finish the back port.
>>> > > > >>>>>>>>>>>
>>> > > > >>>>>>>>>>> Joel Bernstein
>>> > > > >>>>>>>>>>> http://joelsolr.blogspot.com/
>>> > > > >>>>>>>>>>>
>>> > > > >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <
>>> sarowe@gmail.com> wrote:
>>> > > > >>>>>>>>>>> Joel,
>>> > > > >>>>>>>>>>>
>>> > > > >>>>>>>>>>> I know you’re in-process with RC2, but if you have to
>>> restart for some reason, I’d like to include SOLR-10527.
>>> > > > >>>>>>>>>>>
>>> > > > >>>>>>>>>>> --
>>> > > > >>>>>>>>>>> Steve
>>> > > > >>>>>>>>>>> www.lucidworks.com
>>> > > > >>>>>>>>>>>
>>> > > > >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> I also had to change the smoke tester because of the
>>> SSL issue. Which in theory means everyone else will have to as well. I'm
>>> pushing out my changes to branch_6_5, so people can just update their
>>> branch before running the smoke tester.
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> Joel Bernstein
>>> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>>>>>>>>>>> Ok, I had to push out three changes to the branch but
>>> I seemed to have moved passed this issue.
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> Joel Bernstein
>>> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully
>>> the changes will do the trick after they've been pushed.
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> Joel Bernstein
>>> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <
>>> sarowe@gmail.com> wrote:
>>> > > > >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make
>>> modifications on the release branch, but you can’t test unless you commit
>>> (and push).
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> Another alternative: make modifications in another
>>> checkout, then invoke the script with from an unmodified source tree.
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> e.g.:
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> cd ..
>>> > > > >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming
>>> lucene-solr is your checkout dir
>>> > > > >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/script
>>> s/buildAndPushRelease.py
>>> > > > >>>>>>>>>>>> cd lucene-solr
>>> > > > >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>> …
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> (a shorter form of that is to make a copy the script
>>> alone and invoke the modified version from your checkout)
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> --
>>> > > > >>>>>>>>>>>> Steve
>>> > > > >>>>>>>>>>>> www.lucidworks.com
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
>>> origin/branch_6_5.." output is:
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> So, I'm going to have to push this out.
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> Let's first decide if this makes sense as the way
>>> forward.
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> Joel Bernstein
>>> > > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>>>>>>>>>>>> Steve, when I change the script to turn off
>>> verification I get the following error:
>>> > > > >>>>>>>>>>>>> RuntimeError: git clone is dirty:
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> So as part of the work around I think I'm going to
>>> have to commit locally and then revert locally. Does that make sense to you
>>> as the way forward?
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> Joel Bernstein
>>> > > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre
>>> Rafalovitch <ar...@gmail.com> wrote:
>>> > > > >>>>>>>>>>>>> Could it be anything to do with the fact that the
>>> signer is Semantic
>>> > > > >>>>>>>>>>>>> and they are being actively distrusted by - at least
>>> - Google:
>>> > > > >>>>>>>>>>>>> http://www.securityweek.com/go
>>> ogle-stops-trusting-symantec-issued-certificates
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> Regards,
>>> > > > >>>>>>>>>>>>> Alex.
>>> > > > >>>>>>>>>>>>> ----
>>> > > > >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr
>>> users, new and experienced
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't
>>> sure if cert verification
>>> > > > >>>>>>>>>>>>>> was something that was integral to the process.
>>> > > > >>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>> Joel Bernstein
>>> > > > >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> > > > >>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
>>> sarowe@gmail.com> wrote:
>>> > > > >>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>> Hi Joel,
>>> > > > >>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess
>>> “SNI”
>>> > > > >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki
>>> /Server_Name_Indication> has been enabled on
>>> > > > >>>>>>>>>>>>>>> archive.apache.org?
>>> > > > >>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib,
>>> AFAICT an alternative to
>>> > > > >>>>>>>>>>>>>>> urllib):
>>> > > > >>>>>>>>>>>>>>> <http://docs.python-requests.o
>>> rg/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>> > > > >>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>> Short term, you could turn off certificate
>>> verification. The bottom
>>> > > > >>>>>>>>>>>>>>> answer here uses the same lib as the script
>>> (urllib instead of urllib2,
>>> > > > >>>>>>>>>>>>>>> which is assumed in the other answers on the
>>> page), to turn off certificate
>>> > > > >>>>>>>>>>>>>>> verification:
>>> > > > >>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>> <http://stackoverflow.com/ques
>>> tions/19268548/python-ignore-certicate-validation-urllib2>
>>> > > > >>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>> --
>>> > > > >>>>>>>>>>>>>>> Steve
>>> > > > >>>>>>>>>>>>>>> www.lucidworks.com
>>> > > > >>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL
>>> cert for
>>> > > > >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> Joel Bernstein
>>> > > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>>> joelsolr@gmail.com>
>>> > > > >>>>>>>>>>>>>>>> wrote:
>>> > > > >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the
>>> following:
>>> > > > >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>>> --push-local
>>> > > > >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> I believe this is same basic command I used for
>>> RC1. But this time I got
>>> > > > >>>>>>>>>>>>>>>> a new error. At first I thought it might be
>>> incorrect keystore password but
>>> > > > >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what
>>> the issue is?
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> Traceback (most recent call last):
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>>> line 313, in <module>
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> main()
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>>> line 294, in main
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id,
>>> c.key_password)
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>>> line 98, in prepare
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> checkDOAPfiles(version)
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>>> line 143, in
>>> > > > >>>>>>>>>>>>>>>> checkDOAPfiles
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> distpage = load(url)
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>>> line 67, in load
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> content = urllib.request.urlopen(urlStri
>>> ng).read().decode('utf-8')
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> File
>>> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> > > > >>>>>>>>>>>>>>>> line 223, in urlopen
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> File
>>> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> > > > >>>>>>>>>>>>>>>> line 526, in open
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> response = self._open(req, data)
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> File
>>> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> > > > >>>>>>>>>>>>>>>> line 544, in _open
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> '_open', req)
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> File
>>> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> > > > >>>>>>>>>>>>>>>> line 504, in _call_chain
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> result = func(*args)
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> File
>>> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> > > > >>>>>>>>>>>>>>>> line 1361, in https_open
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> context=self._context,
>>> check_hostname=self._check_hostname)
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> File
>>> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> > > > >>>>>>>>>>>>>>>> line 1320, in do_open
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> raise URLError(err)
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>>> CERTIFICATE_VERIFY_FAILED]
>>> > > > >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>> Joel Bernstein
>>> > > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> > > > >>>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>> ------------------------------
>>> ---------------------------------------
>>> > > > >>>>>>>>>>>>>>> To unsubscribe, e-mail:
>>> dev-unsubscribe@lucene.apache.org
>>> > > > >>>>>>>>>>>>>>> For additional commands, e-mail:
>>> dev-help@lucene.apache.org
>>> > > > >>>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>> ------------------------------
>>> ---------------------------------------
>>> > > > >>>>>>>>>>>>> To unsubscribe, e-mail:
>>> dev-unsubscribe@lucene.apache.org
>>> > > > >>>>>>>>>>>>> For additional commands, e-mail:
>>> dev-help@lucene.apache.org
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>> ------------------------------
>>> ---------------------------------------
>>> > > > >>>>>>>>>>>> To unsubscribe, e-mail:
>>> dev-unsubscribe@lucene.apache.org
>>> > > > >>>>>>>>>>>> For additional commands, e-mail:
>>> dev-help@lucene.apache.org
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>>
>>> > > > >>>>>>>>>>>
>>> > > > >>>>>>>>>>>
>>> > > > >>>>>>>>>>> ------------------------------
>>> ---------------------------------------
>>> > > > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
>>> org
>>> > > > >>>>>>>>>>> For additional commands, e-mail:
>>> dev-help@lucene.apache.org
>>> > > > >>>>>>>>>>>
>>> > > > >>>>>>>>>>>
>>> > > > >>>>>>>>>>
>>> > > > >>>>>>>>>
>>> > > > >>>>>>>>
>>> > > > >>>>>>>
>>> > > > >>>>>>>
>>> > > > >>>>>>> ------------------------------
>>> ---------------------------------------
>>> > > > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> > > > >>>>>>> For additional commands, e-mail:
>>> dev-help@lucene.apache.org
>>> > > > >>>>>>>
>>> > > > >>>>>>>
>>> > > > >>>>>>
>>> > > > >>>>>>
>>> > > > >>>>>> ------------------------------
>>> ---------------------------------------
>>> > > > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> > > > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> > > > >>>>>>
>>> > > > >>>>>>
>>> > > > >>>>>
>>> > > > >>>>
>>> > > > >>>>
>>> > > > >>>> ------------------------------------------------------------
>>> ---------
>>> > > > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> > > > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> > > > >>>>
>>> > > > >>>>
>>> > > > >>>
>>> > > > >>>
>>> > > > >>> ------------------------------------------------------------
>>> ---------
>>> > > > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> > > > >>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> > > > >>>
>>> > > > >>>
>>> > > > >>
>>> > > > >>
>>> > > > >> ------------------------------------------------------------
>>> ---------
>>> > > > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> > > > >> For additional commands, e-mail: dev-help@lucene.apache.org
>>> > > > >>
>>> > > > >>
>>> > > > >
>>> > > >
>>> > > >
>>> > > > ------------------------------------------------------------
>>> ---------
>>> > > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> > > > For additional commands, e-mail: dev-help@lucene.apache.org
>>> > > >
>>> > > >
>>> > > >
>>> > >
>>> > >
>>> > > ------------------------------------------------------------
>>> ---------
>>> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> > > For additional commands, e-mail: dev-help@lucene.apache.org
>>> > >
>>> > >
>>> >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> > For additional commands, e-mail: dev-help@lucene.apache.org
>>> >
>>> >
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
Steve,
It looks like you haven't pushed out you changes yet, reverting my changes.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 2:03 PM, Joel Bernstein <jo...@gmail.com> wrote:
> I'm on 10.10.5 (Yosemite).
>
> It could be related to the platform or just something odd with python 3.6.1
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 2:00 PM, Steve Rowe <sa...@gmail.com> wrote:
>
>> FYI I got SUCCESS! [0:36:33.390707] from my reverted-SSL-changes
>> smokeTestRelease.py on Python 3.4.2 against the 6.5.1RC2 URL.
>> (macOS/Python 3.5.1 reverted smoke tester is still running.)
>>
>> It may be the case that you’re missing root certificates that I have (on
>> both Linux and macOS), and that’s the reason SSL validation is failing for
>> you.
>>
>> What platform are you on? IIRC some Linux distros have ways of updating
>> root certificate stores. (I’ve never had to do that myself though.)
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>> > On Apr 20, 2017, at 1:54 PM, Joel Bernstein <jo...@gmail.com> wrote:
>> >
>> > I just ran the smoke tester and it failed in the part of code that I
>> hadn't suppressed the SSL validation. So it's still an issue with my setup.
>> >
>> > I could try another version of python and see if that is the issue.
>> >
>> >
>> >
>> > Joel Bernstein
>> > http://joelsolr.blogspot.com/
>> >
>> > On Thu, Apr 20, 2017 at 1:47 PM, Steve Rowe <sa...@gmail.com> wrote:
>> > AFAICT that error occurs very early in the smoke test process, with the
>> first attempt to download the directory listing at the release URL. I’m
>> running the reverted-SSL-changes smokeTestRelease.py on both Python 3.4.2
>> (Linux) and 3.5.1 (macOS), and both are way past that.
>> >
>> > Would you mind trying to run the smoke tester today after reverting
>> your SSL changes? (Maybe it was a temporary problem for some reason.)
>> AFAICT it will fail fast for you.
>> >
>> > I’m not sure if it makes sense to call the release vote yet, since the
>> smoke tester as committed to branch_6_5 doesn’t work for you or for people
>> with Python < 3.4.3. If the problem turns out to be a transient one for
>> you, then I think we should revert your SSL changes to smokeTestRelease.py
>> on branch_6_5 and respin.
>> >
>> > --
>> > Steve
>> > www.lucidworks.com
>> >
>> > > On Apr 20, 2017, at 1:35 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > >
>> > > Here is the error from the smoke test:
>> > >
>> > > Traceback (most recent call last):
>> > >
>> > > File "dev-tools/scripts/smokeTestRelease.py", line 1483, in
>> <module>
>> > >
>> > > main()
>> > >
>> > > File "dev-tools/scripts/smokeTestRelease.py", line 1427, in main
>> > >
>> > > smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir,
>> c.is_signed, ' '.join(c.test_args))
>> > >
>> > > File "dev-tools/scripts/smokeTestRelease.py", line 1449, in
>> smokeTest
>> > >
>> > > for text, subURL in getDirEntries(baseURL):
>> > >
>> > > File "dev-tools/scripts/smokeTestRelease.py", line 604, in
>> getDirEntries
>> > >
>> > > links = getHREFs(urlString)
>> > >
>> > > File "dev-tools/scripts/smokeTestRelease.py", line 94, in getHREFs
>> > >
>> > > h.request('HEAD', url.path)
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>> line 1239, in request
>> > >
>> > > self._send_request(method, url, body, headers, encode_chunked)
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>> line 1285, in _send_request
>> > >
>> > > self.endheaders(body, encode_chunked=encode_chunked)
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>> line 1234, in endheaders
>> > >
>> > > self._send_output(message_body, encode_chunked=encode_chunked)
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>> line 1026, in _send_output
>> > >
>> > > self.send(msg)
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>> line 964, in send
>> > >
>> > > self.connect()
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>> line 1400, in connect
>> > >
>> > > server_hostname=server_hostname)
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
>> line 401, in wrap_socket
>> > >
>> > > _context=self, _session=session)
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
>> line 808, in __init__
>> > >
>> > > self.do_handshake()
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
>> line 1061, in do_handshake
>> > >
>> > > self._sslobj.do_handshake()
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
>> line 683, in do_handshake
>> > >
>> > > self._sslobj.do_handshake()
>> > >
>> > > ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
>> failed (_ssl.c:749)
>> > >
>> > >
>> > > Joel Bernstein
>> > > http://joelsolr.blogspot.com/
>> > >
>> > > On Thu, Apr 20, 2017 at 1:31 PM, Steve Rowe <sa...@gmail.com> wrote:
>> > > That’s the error you posted for buildAndPushRelease.py - are you
>> saying that you got identical errors for both?
>> > >
>> > > --
>> > > Steve
>> > > www.lucidworks.com
>> > >
>> > > > On Apr 20, 2017, at 1:28 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > > >
>> > > > Python 3.6.1
>> > > >
>> > > >
>> > > > Joel Bernstein
>> > > > http://joelsolr.blogspot.com/
>> > > >
>> > > > On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > > > This was the error:
>> > > >
>> > > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> line 504, in _call_chain
>> > > >
>> > > > result = func(*args)
>> > > >
>> > > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> line 1361, in https_open
>> > > >
>> > > > context=self._context, check_hostname=self._check_hostname)
>> > > >
>> > > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> line 1320, in do_open
>> > > >
>> > > > raise URLError(err)
>> > > >
>> > > > urllib.error.URLError: <urlopen error [SSL:
>> CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)>
>> > > >
>> > > >
>> > > >
>> > > > Perhaps the error was only local to my machine. But I didn't have
>> this error when building RC1
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > Joel Bernstein
>> > > > http://joelsolr.blogspot.com/
>> > > >
>> > > > On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > > Joel,
>> > > >
>> > > > I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t
>> see any problems so far when I run it with my Python 3.4.2 with the
>> 6.5.1RC2 URL. (Still in progress; Lucene distributions have downloaded so
>> far.)
>> > > >
>> > > > What was the error that caused you to make the SSL changes to
>> smokeTestRelease.py? And what version of Python are you using?
>> > > >
>> > > > --
>> > > > Steve
>> > > > www.lucidworks.com
>> > > >
>> > > > > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
>> > > > >
>> > > > > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the
>> first that supports the changes you made, so the smoke tester is failing
>> for me:
>> > > > >
>> > > > > -----
>> > > > > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
>> > > > > content = urllib.request.urlopen(urlString,
>> context=ctx).read().decode('utf-8')
>> > > > > TypeError: urlopen() got an unexpected keyword argument ‘context’
>> > > > > ------
>> > > > >
>> > > > > I’ll install a newer Python.
>> > > > >
>> > > > > --
>> > > > > Steve
>> > > > > www.lucidworks.com
>> > > > >
>> > > > >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > > > >>
>> > > > >> thanks
>> > > > >>
>> > > > >> Joel Bernstein
>> > > > >> http://joelsolr.blogspot.com/
>> > > > >>
>> > > > >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > > >> I’ll take a look.
>> > > > >>
>> > > > >> --
>> > > > >> Steve
>> > > > >> www.lucidworks.com
>> > > > >>
>> > > > >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > > >>>
>> > > > >>> I've uploaded the RC2 here https://dist.apache.org/repos/
>> dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62
>> d88652952ec3e2b3e0070/.
>> > > > >>>
>> > > > >>> But the smoke test breaks with SSL error in different spot when
>> you smoke test from this URL. It's failing with a different command this
>> time so the fix I used in other sports of smoke tester doesn't work.
>> > > > >>>
>> > > > >>> Steve, would you mind taking a look at this and pushing out a
>> fix?
>> > > > >>>
>> > > > >>> Joel Bernstein
>> > > > >>> http://joelsolr.blogspot.com/
>> > > > >>>
>> > > > >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > > >>> I was thinking that if buildAndPushRelease.py can identify
>> problems early, the RM won’t have to later redo work when a problem is
>> found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop
>> anyway) from auto-running precommit would be worth it.
>> > > > >>>
>> > > > >>> But I agree that the smoke tester should be heavy, since it’s
>> possible that the RM had weird local conditions that weren’t caught by the
>> release production tools.
>> > > > >>>
>> > > > >>> --
>> > > > >>> Steve
>> > > > >>> www.lucidworks.com
>> > > > >>>
>> > > > >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > > >>>>
>> > > > >>>> They are both quite long processes. Perhaps we should look at
>> eliminating some of the overlap?
>> > > > >>>>
>> > > > >>>> Since the smokeTesters is run by those voting on the release
>> maybe this should be the heavier of the two.
>> > > > >>>>
>> > > > >>>> Joel Bernstein
>> > > > >>>> http://joelsolr.blogspot.com/
>> > > > >>>>
>> > > > >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > > >>>> Also, I think buildAndPushRelease.py should invoke “precommit"
>> too, (near) where it runs 'ant clean test'.
>> > > > >>>>
>> > > > >>>> --
>> > > > >>>> Steve
>> > > > >>>> www.lucidworks.com
>> > > > >>>>
>> > > > >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > > >>>>>
>> > > > >>>>> That’s bizarre.
>> > > > >>>>>
>> > > > >>>>> The smoke tester runs ‘ant validate’, which does *not*
>> include "documentation-lint” (which includes "-ecj-javadoc-lint”, where
>> unused imports are looked for).
>> > > > >>>>>
>> > > > >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”,
>> “validate”, and “documentation-lint”.
>> > > > >>>>>
>> > > > >>>>> Jenkins caught this not because of the smoke tester, but
>> rather because the “nightly-smoke” task it uses runs “-jenkins-base”,
>> which, like “precommit”, runs “check-working-copy”, “validate”, and
>> “documentation-lint” (among others).
>> > > > >>>>>
>> > > > >>>>> I think we should change the smoke tester to look at the same
>> things as precommit,
>> > > > >>>>>
>> > > > >>>>> --
>> > > > >>>>> Steve
>> > > > >>>>> www.lucidworks.com
>> > > > >>>>>
>> > > > >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > > >>>>>>
>> > > > >>>>>> Smoke testes passed as well
>> > > > >>>>>>
>> > > > >>>>>>
>> > > > >>>>>> Joel Bernstein
>> > > > >>>>>> http://joelsolr.blogspot.com/
>> > > > >>>>>>
>> > > > >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <
>> sarowe@gmail.com> wrote:
>> > > > >>>>>> I guess precommit is only run as part of the smoke tester.
>> > > > >>>>>>
>> > > > >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > > >>>>>>>
>> > > > >>>>>>> Interesting the entire release process completed without
>> complaining.
>> > > > >>>>>>>
>> > > > >>>>>>> Joel Bernstein
>> > > > >>>>>>> http://joelsolr.blogspot.com/
>> > > > >>>>>>>
>> > > > >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <
>> sarowe@gmail.com> wrote:
>> > > > >>>>>>> The unused import was the only problem; I’ve removed it on
>> branch_6_5.
>> > > > >>>>>>>
>> > > > >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
>> > > > >>>>>>>
>> > > > >>>>>>> --
>> > > > >>>>>>> Steve
>> > > > >>>>>>> www.lucidworks.com
>> > > > >>>>>>>
>> > > > >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > > >>>>>>>>
>> > > > >>>>>>>> Crap, Jenkins found an unused import in my commit on
>> branch_6_5 :(. I forgot to run precommit. Doing so now.
>> > > > >>>>>>>>
>> > > > >>>>>>>> --
>> > > > >>>>>>>> Steve
>> > > > >>>>>>>> www.lucidworks.com
>> > > > >>>>>>>>
>> > > > >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > > >>>>>>>>>
>> > > > >>>>>>>>> Done.
>> > > > >>>>>>>>>
>> > > > >>>>>>>>> --
>> > > > >>>>>>>>> Steve
>> > > > >>>>>>>>> www.lucidworks.com
>> > > > >>>>>>>>>
>> > > > >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <
>> sarowe@gmail.com> wrote:
>> > > > >>>>>>>>>>
>> > > > >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5
>> now.
>> > > > >>>>>>>>>>
>> > > > >>>>>>>>>> --
>> > > > >>>>>>>>>> Steve
>> > > > >>>>>>>>>> www.lucidworks.com
>> > > > >>>>>>>>>>
>> > > > >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > > >>>>>>>>>>>
>> > > > >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish
>> the back port.
>> > > > >>>>>>>>>>>
>> > > > >>>>>>>>>>> Joel Bernstein
>> > > > >>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > > >>>>>>>>>>>
>> > > > >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <
>> sarowe@gmail.com> wrote:
>> > > > >>>>>>>>>>> Joel,
>> > > > >>>>>>>>>>>
>> > > > >>>>>>>>>>> I know you’re in-process with RC2, but if you have to
>> restart for some reason, I’d like to include SOLR-10527.
>> > > > >>>>>>>>>>>
>> > > > >>>>>>>>>>> --
>> > > > >>>>>>>>>>> Steve
>> > > > >>>>>>>>>>> www.lucidworks.com
>> > > > >>>>>>>>>>>
>> > > > >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> I also had to change the smoke tester because of the
>> SSL issue. Which in theory means everyone else will have to as well. I'm
>> pushing out my changes to branch_6_5, so people can just update their
>> branch before running the smoke tester.
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> Joel Bernstein
>> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > > >>>>>>>>>>>> Ok, I had to push out three changes to the branch but
>> I seemed to have moved passed this issue.
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> Joel Bernstein
>> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > > >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully
>> the changes will do the trick after they've been pushed.
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> Joel Bernstein
>> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <
>> sarowe@gmail.com> wrote:
>> > > > >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make
>> modifications on the release branch, but you can’t test unless you commit
>> (and push).
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> Another alternative: make modifications in another
>> checkout, then invoke the script with from an unmodified source tree.
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> e.g.:
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> cd ..
>> > > > >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr
>> is your checkout dir
>> > > > >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/script
>> s/buildAndPushRelease.py
>> > > > >>>>>>>>>>>> cd lucene-solr
>> > > > >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>> …
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> (a shorter form of that is to make a copy the script
>> alone and invoke the modified version from your checkout)
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> --
>> > > > >>>>>>>>>>>> Steve
>> > > > >>>>>>>>>>>> www.lucidworks.com
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
>> origin/branch_6_5.." output is:
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> So, I'm going to have to push this out.
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> Let's first decide if this makes sense as the way
>> forward.
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> Joel Bernstein
>> > > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > > >>>>>>>>>>>>> Steve, when I change the script to turn off
>> verification I get the following error:
>> > > > >>>>>>>>>>>>> RuntimeError: git clone is dirty:
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> So as part of the work around I think I'm going to
>> have to commit locally and then revert locally. Does that make sense to you
>> as the way forward?
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> Joel Bernstein
>> > > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre
>> Rafalovitch <ar...@gmail.com> wrote:
>> > > > >>>>>>>>>>>>> Could it be anything to do with the fact that the
>> signer is Semantic
>> > > > >>>>>>>>>>>>> and they are being actively distrusted by - at least
>> - Google:
>> > > > >>>>>>>>>>>>> http://www.securityweek.com/go
>> ogle-stops-trusting-symantec-issued-certificates
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> Regards,
>> > > > >>>>>>>>>>>>> Alex.
>> > > > >>>>>>>>>>>>> ----
>> > > > >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr
>> users, new and experienced
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > > >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't
>> sure if cert verification
>> > > > >>>>>>>>>>>>>> was something that was integral to the process.
>> > > > >>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>> Joel Bernstein
>> > > > >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > > >>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
>> sarowe@gmail.com> wrote:
>> > > > >>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>> Hi Joel,
>> > > > >>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess
>> “SNI”
>> > > > >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki
>> /Server_Name_Indication> has been enabled on
>> > > > >>>>>>>>>>>>>>> archive.apache.org?
>> > > > >>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib,
>> AFAICT an alternative to
>> > > > >>>>>>>>>>>>>>> urllib):
>> > > > >>>>>>>>>>>>>>> <http://docs.python-requests.o
>> rg/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>> > > > >>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>> Short term, you could turn off certificate
>> verification. The bottom
>> > > > >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib
>> instead of urllib2,
>> > > > >>>>>>>>>>>>>>> which is assumed in the other answers on the page),
>> to turn off certificate
>> > > > >>>>>>>>>>>>>>> verification:
>> > > > >>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>> <http://stackoverflow.com/ques
>> tions/19268548/python-ignore-certicate-validation-urllib2>
>> > > > >>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>> --
>> > > > >>>>>>>>>>>>>>> Steve
>> > > > >>>>>>>>>>>>>>> www.lucidworks.com
>> > > > >>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL
>> cert for
>> > > > >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> Joel Bernstein
>> > > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>> joelsolr@gmail.com>
>> > > > >>>>>>>>>>>>>>>> wrote:
>> > > > >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the
>> following:
>> > > > >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>> --push-local
>> > > > >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> I believe this is same basic command I used for
>> RC1. But this time I got
>> > > > >>>>>>>>>>>>>>>> a new error. At first I thought it might be
>> incorrect keystore password but
>> > > > >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what
>> the issue is?
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> Traceback (most recent call last):
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>> line 313, in <module>
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> main()
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>> line 294, in main
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id,
>> c.key_password)
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>> line 98, in prepare
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> checkDOAPfiles(version)
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>> line 143, in
>> > > > >>>>>>>>>>>>>>>> checkDOAPfiles
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> distpage = load(url)
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>> line 67, in load
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> content = urllib.request.urlopen(urlStri
>> ng).read().decode('utf-8')
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> File
>> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > > > >>>>>>>>>>>>>>>> line 223, in urlopen
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> File
>> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > > > >>>>>>>>>>>>>>>> line 526, in open
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> response = self._open(req, data)
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> File
>> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > > > >>>>>>>>>>>>>>>> line 544, in _open
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> '_open', req)
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> File
>> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > > > >>>>>>>>>>>>>>>> line 504, in _call_chain
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> result = func(*args)
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> File
>> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > > > >>>>>>>>>>>>>>>> line 1361, in https_open
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> context=self._context,
>> check_hostname=self._check_hostname)
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> File
>> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > > > >>>>>>>>>>>>>>>> line 1320, in do_open
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> raise URLError(err)
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>> CERTIFICATE_VERIFY_FAILED]
>> > > > >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>> Joel Bernstein
>> > > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > > >>>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>> ------------------------------
>> ---------------------------------------
>> > > > >>>>>>>>>>>>>>> To unsubscribe, e-mail:
>> dev-unsubscribe@lucene.apache.org
>> > > > >>>>>>>>>>>>>>> For additional commands, e-mail:
>> dev-help@lucene.apache.org
>> > > > >>>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>> ------------------------------
>> ---------------------------------------
>> > > > >>>>>>>>>>>>> To unsubscribe, e-mail:
>> dev-unsubscribe@lucene.apache.org
>> > > > >>>>>>>>>>>>> For additional commands, e-mail:
>> dev-help@lucene.apache.org
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>>
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>> ------------------------------
>> ---------------------------------------
>> > > > >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
>> org
>> > > > >>>>>>>>>>>> For additional commands, e-mail:
>> dev-help@lucene.apache.org
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>>
>> > > > >>>>>>>>>>>
>> > > > >>>>>>>>>>>
>> > > > >>>>>>>>>>> ------------------------------
>> ---------------------------------------
>> > > > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
>> org
>> > > > >>>>>>>>>>> For additional commands, e-mail:
>> dev-help@lucene.apache.org
>> > > > >>>>>>>>>>>
>> > > > >>>>>>>>>>>
>> > > > >>>>>>>>>>
>> > > > >>>>>>>>>
>> > > > >>>>>>>>
>> > > > >>>>>>>
>> > > > >>>>>>>
>> > > > >>>>>>> ------------------------------
>> ---------------------------------------
>> > > > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > > > >>>>>>>
>> > > > >>>>>>>
>> > > > >>>>>>
>> > > > >>>>>>
>> > > > >>>>>> ------------------------------------------------------------
>> ---------
>> > > > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > > > >>>>>>
>> > > > >>>>>>
>> > > > >>>>>
>> > > > >>>>
>> > > > >>>>
>> > > > >>>> ------------------------------------------------------------
>> ---------
>> > > > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > > > >>>>
>> > > > >>>>
>> > > > >>>
>> > > > >>>
>> > > > >>> ------------------------------------------------------------
>> ---------
>> > > > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > > >>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > > > >>>
>> > > > >>>
>> > > > >>
>> > > > >>
>> > > > >> ------------------------------------------------------------
>> ---------
>> > > > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > > >> For additional commands, e-mail: dev-help@lucene.apache.org
>> > > > >>
>> > > > >>
>> > > > >
>> > > >
>> > > >
>> > > > ------------------------------------------------------------
>> ---------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > > For additional commands, e-mail: dev-help@lucene.apache.org
>> > > >
>> > > >
>> > > >
>> > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > For additional commands, e-mail: dev-help@lucene.apache.org
>> > >
>> > >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > For additional commands, e-mail: dev-help@lucene.apache.org
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
FYI my macOS tests with Python 3.5.1 were on 10.12.4 (Sierra).
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 2:03 PM, Joel Bernstein <jo...@gmail.com> wrote:
>
> I'm on 10.10.5 (Yosemite).
>
> It could be related to the platform or just something odd with python 3.6.1
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 2:00 PM, Steve Rowe <sa...@gmail.com> wrote:
> FYI I got SUCCESS! [0:36:33.390707] from my reverted-SSL-changes smokeTestRelease.py on Python 3.4.2 against the 6.5.1RC2 URL. (macOS/Python 3.5.1 reverted smoke tester is still running.)
>
> It may be the case that you’re missing root certificates that I have (on both Linux and macOS), and that’s the reason SSL validation is failing for you.
>
> What platform are you on? IIRC some Linux distros have ways of updating root certificate stores. (I’ve never had to do that myself though.)
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 1:54 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > I just ran the smoke tester and it failed in the part of code that I hadn't suppressed the SSL validation. So it's still an issue with my setup.
> >
> > I could try another version of python and see if that is the issue.
> >
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 1:47 PM, Steve Rowe <sa...@gmail.com> wrote:
> > AFAICT that error occurs very early in the smoke test process, with the first attempt to download the directory listing at the release URL. I’m running the reverted-SSL-changes smokeTestRelease.py on both Python 3.4.2 (Linux) and 3.5.1 (macOS), and both are way past that.
> >
> > Would you mind trying to run the smoke tester today after reverting your SSL changes? (Maybe it was a temporary problem for some reason.) AFAICT it will fail fast for you.
> >
> > I’m not sure if it makes sense to call the release vote yet, since the smoke tester as committed to branch_6_5 doesn’t work for you or for people with Python < 3.4.3. If the problem turns out to be a transient one for you, then I think we should revert your SSL changes to smokeTestRelease.py on branch_6_5 and respin.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 1:35 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >
> > > Here is the error from the smoke test:
> > >
> > > Traceback (most recent call last):
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 1483, in <module>
> > >
> > > main()
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 1427, in main
> > >
> > > smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir, c.is_signed, ' '.join(c.test_args))
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 1449, in smokeTest
> > >
> > > for text, subURL in getDirEntries(baseURL):
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 604, in getDirEntries
> > >
> > > links = getHREFs(urlString)
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 94, in getHREFs
> > >
> > > h.request('HEAD', url.path)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1239, in request
> > >
> > > self._send_request(method, url, body, headers, encode_chunked)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1285, in _send_request
> > >
> > > self.endheaders(body, encode_chunked=encode_chunked)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1234, in endheaders
> > >
> > > self._send_output(message_body, encode_chunked=encode_chunked)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1026, in _send_output
> > >
> > > self.send(msg)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 964, in send
> > >
> > > self.connect()
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1400, in connect
> > >
> > > server_hostname=server_hostname)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 401, in wrap_socket
> > >
> > > _context=self, _session=session)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 808, in __init__
> > >
> > > self.do_handshake()
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 1061, in do_handshake
> > >
> > > self._sslobj.do_handshake()
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 683, in do_handshake
> > >
> > > self._sslobj.do_handshake()
> > >
> > > ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)
> > >
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Thu, Apr 20, 2017 at 1:31 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > That’s the error you posted for buildAndPushRelease.py - are you saying that you got identical errors for both?
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > > > On Apr 20, 2017, at 1:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >
> > > > Python 3.6.1
> > > >
> > > >
> > > > Joel Bernstein
> > > > http://joelsolr.blogspot.com/
> > > >
> > > > On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > This was the error:
> > > >
> > > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 504, in _call_chain
> > > >
> > > > result = func(*args)
> > > >
> > > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 1361, in https_open
> > > >
> > > > context=self._context, check_hostname=self._check_hostname)
> > > >
> > > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 1320, in do_open
> > > >
> > > > raise URLError(err)
> > > >
> > > > urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)>
> > > >
> > > >
> > > >
> > > > Perhaps the error was only local to my machine. But I didn't have this error when building RC1
> > > >
> > > >
> > > >
> > > >
> > > > Joel Bernstein
> > > > http://joelsolr.blogspot.com/
> > > >
> > > > On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > Joel,
> > > >
> > > > I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t see any problems so far when I run it with my Python 3.4.2 with the 6.5.1RC2 URL. (Still in progress; Lucene distributions have downloaded so far.)
> > > >
> > > > What was the error that caused you to make the SSL changes to smokeTestRelease.py? And what version of Python are you using?
> > > >
> > > > --
> > > > Steve
> > > > www.lucidworks.com
> > > >
> > > > > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >
> > > > > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the first that supports the changes you made, so the smoke tester is failing for me:
> > > > >
> > > > > -----
> > > > > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
> > > > > content = urllib.request.urlopen(urlString, context=ctx).read().decode('utf-8')
> > > > > TypeError: urlopen() got an unexpected keyword argument ‘context’
> > > > > ------
> > > > >
> > > > > I’ll install a newer Python.
> > > > >
> > > > > --
> > > > > Steve
> > > > > www.lucidworks.com
> > > > >
> > > > >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>
> > > > >> thanks
> > > > >>
> > > > >> Joel Bernstein
> > > > >> http://joelsolr.blogspot.com/
> > > > >>
> > > > >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >> I’ll take a look.
> > > > >>
> > > > >> --
> > > > >> Steve
> > > > >> www.lucidworks.com
> > > > >>
> > > > >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>
> > > > >>> I've uploaded the RC2 here https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d88652952ec3e2b3e0070/.
> > > > >>>
> > > > >>> But the smoke test breaks with SSL error in different spot when you smoke test from this URL. It's failing with a different command this time so the fix I used in other sports of smoke tester doesn't work.
> > > > >>>
> > > > >>> Steve, would you mind taking a look at this and pushing out a fix?
> > > > >>>
> > > > >>> Joel Bernstein
> > > > >>> http://joelsolr.blogspot.com/
> > > > >>>
> > > > >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>> I was thinking that if buildAndPushRelease.py can identify problems early, the RM won’t have to later redo work when a problem is found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from auto-running precommit would be worth it.
> > > > >>>
> > > > >>> But I agree that the smoke tester should be heavy, since it’s possible that the RM had weird local conditions that weren’t caught by the release production tools.
> > > > >>>
> > > > >>> --
> > > > >>> Steve
> > > > >>> www.lucidworks.com
> > > > >>>
> > > > >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>
> > > > >>>> They are both quite long processes. Perhaps we should look at eliminating some of the overlap?
> > > > >>>>
> > > > >>>> Since the smokeTesters is run by those voting on the release maybe this should be the heavier of the two.
> > > > >>>>
> > > > >>>> Joel Bernstein
> > > > >>>> http://joelsolr.blogspot.com/
> > > > >>>>
> > > > >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>> Also, I think buildAndPushRelease.py should invoke “precommit" too, (near) where it runs 'ant clean test'.
> > > > >>>>
> > > > >>>> --
> > > > >>>> Steve
> > > > >>>> www.lucidworks.com
> > > > >>>>
> > > > >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>
> > > > >>>>> That’s bizarre.
> > > > >>>>>
> > > > >>>>> The smoke tester runs ‘ant validate’, which does *not* include "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused imports are looked for).
> > > > >>>>>
> > > > >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and “documentation-lint”.
> > > > >>>>>
> > > > >>>>> Jenkins caught this not because of the smoke tester, but rather because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like “precommit”, runs “check-working-copy”, “validate”, and “documentation-lint” (among others).
> > > > >>>>>
> > > > >>>>> I think we should change the smoke tester to look at the same things as precommit,
> > > > >>>>>
> > > > >>>>> --
> > > > >>>>> Steve
> > > > >>>>> www.lucidworks.com
> > > > >>>>>
> > > > >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>
> > > > >>>>>> Smoke testes passed as well
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> Joel Bernstein
> > > > >>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>
> > > > >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>> I guess precommit is only run as part of the smoke tester.
> > > > >>>>>>
> > > > >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>
> > > > >>>>>>> Interesting the entire release process completed without complaining.
> > > > >>>>>>>
> > > > >>>>>>> Joel Bernstein
> > > > >>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>
> > > > >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>> The unused import was the only problem; I’ve removed it on branch_6_5.
> > > > >>>>>>>
> > > > >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
> > > > >>>>>>>
> > > > >>>>>>> --
> > > > >>>>>>> Steve
> > > > >>>>>>> www.lucidworks.com
> > > > >>>>>>>
> > > > >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>>>
> > > > >>>>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
> > > > >>>>>>>>
> > > > >>>>>>>> --
> > > > >>>>>>>> Steve
> > > > >>>>>>>> www.lucidworks.com
> > > > >>>>>>>>
> > > > >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>>>>
> > > > >>>>>>>>> Done.
> > > > >>>>>>>>>
> > > > >>>>>>>>> --
> > > > >>>>>>>>> Steve
> > > > >>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>
> > > > >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>>>>>
> > > > >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > > > >>>>>>>>>>
> > > > >>>>>>>>>> --
> > > > >>>>>>>>>> Steve
> > > > >>>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the back port.
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>>>>>> Joel,
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> --
> > > > >>>>>>>>>>> Steve
> > > > >>>>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> e.g.:
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> cd ..
> > > > >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> > > > >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > > > >>>>>>>>>>>> cd lucene-solr
> > > > >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> --
> > > > >>>>>>>>>>>> Steve
> > > > >>>>>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> So, I'm going to have to push this out.
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Let's first decide if this makes sense as the way forward.
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>>> Steve, when I change the script to turn off verification I get the following error:
> > > > >>>>>>>>>>>>> RuntimeError: git clone is dirty:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> > > > >>>>>>>>>>>>> Could it be anything to do with the fact that the signer is Semantic
> > > > >>>>>>>>>>>>> and they are being actively distrusted by - at least - Google:
> > > > >>>>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Regards,
> > > > >>>>>>>>>>>>> Alex.
> > > > >>>>>>>>>>>>> ----
> > > > >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> > > > >>>>>>>>>>>>>> was something that was integral to the process.
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> Hi Joel,
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > > > >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> > > > >>>>>>>>>>>>>>> archive.apache.org?
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
> > > > >>>>>>>>>>>>>>> urllib):
> > > > >>>>>>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> Short term, you could turn off certificate verification. The bottom
> > > > >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
> > > > >>>>>>>>>>>>>>> which is assumed in the other answers on the page), to turn off certificate
> > > > >>>>>>>>>>>>>>> verification:
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> --
> > > > >>>>>>>>>>>>>>> Steve
> > > > >>>>>>>>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> > > > >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> > > > >>>>>>>>>>>>>>>> wrote:
> > > > >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > > > >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> > > > >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
> > > > >>>>>>>>>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
> > > > >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> Traceback (most recent call last):
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> main()
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> checkDOAPfiles(version)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> > > > >>>>>>>>>>>>>>>> checkDOAPfiles
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> distpage = load(url)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 223, in urlopen
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 526, in open
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> response = self._open(req, data)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 544, in _open
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> '_open', req)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 504, in _call_chain
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> result = func(*args)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 1361, in https_open
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 1320, in do_open
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> raise URLError(err)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> > > > >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> ---------------------------------------------------------------------
> > > > >>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> ---------------------------------------------------------------------
> > > > >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> ---------------------------------------------------------------------
> > > > >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> ---------------------------------------------------------------------
> > > > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>
> > > > >>>>>>>>>
> > > > >>>>>>>>
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>> ---------------------------------------------------------------------
> > > > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> ---------------------------------------------------------------------
> > > > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>> ---------------------------------------------------------------------
> > > > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>
> > > > >>>>
> > > > >>>
> > > > >>>
> > > > >>> ---------------------------------------------------------------------
> > > > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>
> > > > >>>
> > > > >>
> > > > >>
> > > > >> ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > For additional commands, e-mail: dev-help@lucene.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: dev-help@lucene.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
I'm on 10.10.5 (Yosemite).
It could be related to the platform or just something odd with python 3.6.1
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 2:00 PM, Steve Rowe <sa...@gmail.com> wrote:
> FYI I got SUCCESS! [0:36:33.390707] from my reverted-SSL-changes
> smokeTestRelease.py on Python 3.4.2 against the 6.5.1RC2 URL.
> (macOS/Python 3.5.1 reverted smoke tester is still running.)
>
> It may be the case that you’re missing root certificates that I have (on
> both Linux and macOS), and that’s the reason SSL validation is failing for
> you.
>
> What platform are you on? IIRC some Linux distros have ways of updating
> root certificate stores. (I’ve never had to do that myself though.)
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 1:54 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > I just ran the smoke tester and it failed in the part of code that I
> hadn't suppressed the SSL validation. So it's still an issue with my setup.
> >
> > I could try another version of python and see if that is the issue.
> >
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 1:47 PM, Steve Rowe <sa...@gmail.com> wrote:
> > AFAICT that error occurs very early in the smoke test process, with the
> first attempt to download the directory listing at the release URL. I’m
> running the reverted-SSL-changes smokeTestRelease.py on both Python 3.4.2
> (Linux) and 3.5.1 (macOS), and both are way past that.
> >
> > Would you mind trying to run the smoke tester today after reverting your
> SSL changes? (Maybe it was a temporary problem for some reason.) AFAICT
> it will fail fast for you.
> >
> > I’m not sure if it makes sense to call the release vote yet, since the
> smoke tester as committed to branch_6_5 doesn’t work for you or for people
> with Python < 3.4.3. If the problem turns out to be a transient one for
> you, then I think we should revert your SSL changes to smokeTestRelease.py
> on branch_6_5 and respin.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 1:35 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >
> > > Here is the error from the smoke test:
> > >
> > > Traceback (most recent call last):
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 1483, in <module>
> > >
> > > main()
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 1427, in main
> > >
> > > smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir,
> c.is_signed, ' '.join(c.test_args))
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 1449, in
> smokeTest
> > >
> > > for text, subURL in getDirEntries(baseURL):
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 604, in
> getDirEntries
> > >
> > > links = getHREFs(urlString)
> > >
> > > File "dev-tools/scripts/smokeTestRelease.py", line 94, in getHREFs
> > >
> > > h.request('HEAD', url.path)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
> line 1239, in request
> > >
> > > self._send_request(method, url, body, headers, encode_chunked)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
> line 1285, in _send_request
> > >
> > > self.endheaders(body, encode_chunked=encode_chunked)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
> line 1234, in endheaders
> > >
> > > self._send_output(message_body, encode_chunked=encode_chunked)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
> line 1026, in _send_output
> > >
> > > self.send(msg)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
> line 964, in send
> > >
> > > self.connect()
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
> line 1400, in connect
> > >
> > > server_hostname=server_hostname)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
> line 401, in wrap_socket
> > >
> > > _context=self, _session=session)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
> line 808, in __init__
> > >
> > > self.do_handshake()
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
> line 1061, in do_handshake
> > >
> > > self._sslobj.do_handshake()
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
> line 683, in do_handshake
> > >
> > > self._sslobj.do_handshake()
> > >
> > > ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
> failed (_ssl.c:749)
> > >
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Thu, Apr 20, 2017 at 1:31 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > That’s the error you posted for buildAndPushRelease.py - are you
> saying that you got identical errors for both?
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > > > On Apr 20, 2017, at 1:28 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > >
> > > > Python 3.6.1
> > > >
> > > >
> > > > Joel Bernstein
> > > > http://joelsolr.blogspot.com/
> > > >
> > > > On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > > This was the error:
> > > >
> > > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 504, in _call_chain
> > > >
> > > > result = func(*args)
> > > >
> > > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 1361, in https_open
> > > >
> > > > context=self._context, check_hostname=self._check_hostname)
> > > >
> > > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 1320, in do_open
> > > >
> > > > raise URLError(err)
> > > >
> > > > urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)>
> > > >
> > > >
> > > >
> > > > Perhaps the error was only local to my machine. But I didn't have
> this error when building RC1
> > > >
> > > >
> > > >
> > > >
> > > > Joel Bernstein
> > > > http://joelsolr.blogspot.com/
> > > >
> > > > On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > > Joel,
> > > >
> > > > I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t
> see any problems so far when I run it with my Python 3.4.2 with the
> 6.5.1RC2 URL. (Still in progress; Lucene distributions have downloaded so
> far.)
> > > >
> > > > What was the error that caused you to make the SSL changes to
> smokeTestRelease.py? And what version of Python are you using?
> > > >
> > > > --
> > > > Steve
> > > > www.lucidworks.com
> > > >
> > > > > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > > >
> > > > > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the
> first that supports the changes you made, so the smoke tester is failing
> for me:
> > > > >
> > > > > -----
> > > > > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
> > > > > content = urllib.request.urlopen(urlString,
> context=ctx).read().decode('utf-8')
> > > > > TypeError: urlopen() got an unexpected keyword argument ‘context’
> > > > > ------
> > > > >
> > > > > I’ll install a newer Python.
> > > > >
> > > > > --
> > > > > Steve
> > > > > www.lucidworks.com
> > > > >
> > > > >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > > >>
> > > > >> thanks
> > > > >>
> > > > >> Joel Bernstein
> > > > >> http://joelsolr.blogspot.com/
> > > > >>
> > > > >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > > >> I’ll take a look.
> > > > >>
> > > > >> --
> > > > >> Steve
> > > > >> www.lucidworks.com
> > > > >>
> > > > >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > > >>>
> > > > >>> I've uploaded the RC2 here https://dist.apache.org/repos/
> dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d8865295
> 2ec3e2b3e0070/.
> > > > >>>
> > > > >>> But the smoke test breaks with SSL error in different spot when
> you smoke test from this URL. It's failing with a different command this
> time so the fix I used in other sports of smoke tester doesn't work.
> > > > >>>
> > > > >>> Steve, would you mind taking a look at this and pushing out a
> fix?
> > > > >>>
> > > > >>> Joel Bernstein
> > > > >>> http://joelsolr.blogspot.com/
> > > > >>>
> > > > >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > > >>> I was thinking that if buildAndPushRelease.py can identify
> problems early, the RM won’t have to later redo work when a problem is
> found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop
> anyway) from auto-running precommit would be worth it.
> > > > >>>
> > > > >>> But I agree that the smoke tester should be heavy, since it’s
> possible that the RM had weird local conditions that weren’t caught by the
> release production tools.
> > > > >>>
> > > > >>> --
> > > > >>> Steve
> > > > >>> www.lucidworks.com
> > > > >>>
> > > > >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > > >>>>
> > > > >>>> They are both quite long processes. Perhaps we should look at
> eliminating some of the overlap?
> > > > >>>>
> > > > >>>> Since the smokeTesters is run by those voting on the release
> maybe this should be the heavier of the two.
> > > > >>>>
> > > > >>>> Joel Bernstein
> > > > >>>> http://joelsolr.blogspot.com/
> > > > >>>>
> > > > >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > > >>>> Also, I think buildAndPushRelease.py should invoke “precommit"
> too, (near) where it runs 'ant clean test'.
> > > > >>>>
> > > > >>>> --
> > > > >>>> Steve
> > > > >>>> www.lucidworks.com
> > > > >>>>
> > > > >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > > >>>>>
> > > > >>>>> That’s bizarre.
> > > > >>>>>
> > > > >>>>> The smoke tester runs ‘ant validate’, which does *not* include
> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
> imports are looked for).
> > > > >>>>>
> > > > >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”,
> “validate”, and “documentation-lint”.
> > > > >>>>>
> > > > >>>>> Jenkins caught this not because of the smoke tester, but
> rather because the “nightly-smoke” task it uses runs “-jenkins-base”,
> which, like “precommit”, runs “check-working-copy”, “validate”, and
> “documentation-lint” (among others).
> > > > >>>>>
> > > > >>>>> I think we should change the smoke tester to look at the same
> things as precommit,
> > > > >>>>>
> > > > >>>>> --
> > > > >>>>> Steve
> > > > >>>>> www.lucidworks.com
> > > > >>>>>
> > > > >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > > >>>>>>
> > > > >>>>>> Smoke testes passed as well
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> Joel Bernstein
> > > > >>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>
> > > > >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > > >>>>>> I guess precommit is only run as part of the smoke tester.
> > > > >>>>>>
> > > > >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > > >>>>>>>
> > > > >>>>>>> Interesting the entire release process completed without
> complaining.
> > > > >>>>>>>
> > > > >>>>>>> Joel Bernstein
> > > > >>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>
> > > > >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <
> sarowe@gmail.com> wrote:
> > > > >>>>>>> The unused import was the only problem; I’ve removed it on
> branch_6_5.
> > > > >>>>>>>
> > > > >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
> > > > >>>>>>>
> > > > >>>>>>> --
> > > > >>>>>>> Steve
> > > > >>>>>>> www.lucidworks.com
> > > > >>>>>>>
> > > > >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > > >>>>>>>>
> > > > >>>>>>>> Crap, Jenkins found an unused import in my commit on
> branch_6_5 :(. I forgot to run precommit. Doing so now.
> > > > >>>>>>>>
> > > > >>>>>>>> --
> > > > >>>>>>>> Steve
> > > > >>>>>>>> www.lucidworks.com
> > > > >>>>>>>>
> > > > >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > > >>>>>>>>>
> > > > >>>>>>>>> Done.
> > > > >>>>>>>>>
> > > > >>>>>>>>> --
> > > > >>>>>>>>> Steve
> > > > >>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>
> > > > >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > > >>>>>>>>>>
> > > > >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5
> now.
> > > > >>>>>>>>>>
> > > > >>>>>>>>>> --
> > > > >>>>>>>>>> Steve
> > > > >>>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish
> the back port.
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <
> sarowe@gmail.com> wrote:
> > > > >>>>>>>>>>> Joel,
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> I know you’re in-process with RC2, but if you have to
> restart for some reason, I’d like to include SOLR-10527.
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> --
> > > > >>>>>>>>>>> Steve
> > > > >>>>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> I also had to change the smoke tester because of the
> SSL issue. Which in theory means everyone else will have to as well. I'm
> pushing out my changes to branch_6_5, so people can just update their
> branch before running the smoke tester.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > > >>>>>>>>>>>> Ok, I had to push out three changes to the branch but I
> seemed to have moved passed this issue.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > > >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully
> the changes will do the trick after they've been pushed.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <
> sarowe@gmail.com> wrote:
> > > > >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make
> modifications on the release branch, but you can’t test unless you commit
> (and push).
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Another alternative: make modifications in another
> checkout, then invoke the script with from an unmodified source tree.
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> e.g.:
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> cd ..
> > > > >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr
> is your checkout dir
> > > > >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/
> scripts/buildAndPushRelease.py
> > > > >>>>>>>>>>>> cd lucene-solr
> > > > >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> …
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> (a shorter form of that is to make a copy the script
> alone and invoke the modified version from your checkout)
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> --
> > > > >>>>>>>>>>>> Steve
> > > > >>>>>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
> origin/branch_6_5.." output is:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> So, I'm going to have to push this out.
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Let's first decide if this makes sense as the way
> forward.
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > > >>>>>>>>>>>>> Steve, when I change the script to turn off
> verification I get the following error:
> > > > >>>>>>>>>>>>> RuntimeError: git clone is dirty:
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> So as part of the work around I think I'm going to
> have to commit locally and then revert locally. Does that make sense to you
> as the way forward?
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch
> <ar...@gmail.com> wrote:
> > > > >>>>>>>>>>>>> Could it be anything to do with the fact that the
> signer is Semantic
> > > > >>>>>>>>>>>>> and they are being actively distrusted by - at least -
> Google:
> > > > >>>>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> Regards,
> > > > >>>>>>>>>>>>> Alex.
> > > > >>>>>>>>>>>>> ----
> > > > >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr
> users, new and experienced
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > > >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't
> sure if cert verification
> > > > >>>>>>>>>>>>>> was something that was integral to the process.
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
> sarowe@gmail.com> wrote:
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> Hi Joel,
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess
> “SNI”
> > > > >>>>>>>>>>>>>>> <https://en.wikipedia.org/
> wiki/Server_Name_Indication> has been enabled on
> > > > >>>>>>>>>>>>>>> archive.apache.org?
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib,
> AFAICT an alternative to
> > > > >>>>>>>>>>>>>>> urllib):
> > > > >>>>>>>>>>>>>>> <http://docs.python-requests.
> org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> Short term, you could turn off certificate
> verification. The bottom
> > > > >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib
> instead of urllib2,
> > > > >>>>>>>>>>>>>>> which is assumed in the other answers on the page),
> to turn off certificate
> > > > >>>>>>>>>>>>>>> verification:
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> --
> > > > >>>>>>>>>>>>>>> Steve
> > > > >>>>>>>>>>>>>>> www.lucidworks.com
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL
> cert for
> > > > >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
> joelsolr@gmail.com>
> > > > >>>>>>>>>>>>>>>> wrote:
> > > > >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > > > >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
> --push-local
> > > > >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> I believe this is same basic command I used for
> RC1. But this time I got
> > > > >>>>>>>>>>>>>>>> a new error. At first I thought it might be
> incorrect keystore password but
> > > > >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what
> the issue is?
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> Traceback (most recent call last):
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
> line 313, in <module>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> main()
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
> line 294, in main
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id,
> c.key_password)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
> line 98, in prepare
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> checkDOAPfiles(version)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
> line 143, in
> > > > >>>>>>>>>>>>>>>> checkDOAPfiles
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> distpage = load(url)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
> line 67, in load
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> content = urllib.request.urlopen(
> urlString).read().decode('utf-8')
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.
> framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 223, in urlopen
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.
> framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 526, in open
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> response = self._open(req, data)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.
> framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 544, in _open
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> '_open', req)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.
> framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 504, in _call_chain
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> result = func(*args)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.
> framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 1361, in https_open
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_
> hostname)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> File
> > > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.
> framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > > >>>>>>>>>>>>>>>> line 1320, in do_open
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> raise URLError(err)
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> > > > >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>> Joel Bernstein
> > > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > > >>>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>> ------------------------------
> ---------------------------------------
> > > > >>>>>>>>>>>>>>> To unsubscribe, e-mail:
> dev-unsubscribe@lucene.apache.org
> > > > >>>>>>>>>>>>>>> For additional commands, e-mail:
> dev-help@lucene.apache.org
> > > > >>>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>> ------------------------------
> ---------------------------------------
> > > > >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
> org
> > > > >>>>>>>>>>>>> For additional commands, e-mail:
> dev-help@lucene.apache.org
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> ------------------------------
> ---------------------------------------
> > > > >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
> org
> > > > >>>>>>>>>>>> For additional commands, e-mail:
> dev-help@lucene.apache.org
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> ------------------------------
> ---------------------------------------
> > > > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
> org
> > > > >>>>>>>>>>> For additional commands, e-mail:
> dev-help@lucene.apache.org
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>
> > > > >>>>>>>>>
> > > > >>>>>>>>
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>> ------------------------------------------------------------
> ---------
> > > > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> ------------------------------------------------------------
> ---------
> > > > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>
> > > > >>>>
> > > > >>>>
> > > > >>>> ------------------------------------------------------------
> ---------
> > > > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>>
> > > > >>>>
> > > > >>>
> > > > >>>
> > > > >>> ------------------------------------------------------------
> ---------
> > > > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>>
> > > > >>>
> > > > >>
> > > > >>
> > > > >> ------------------------------------------------------------
> ---------
> > > > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > > > ------------------------------------------------------------
> ---------
> > > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > > For additional commands, e-mail: dev-help@lucene.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: dev-help@lucene.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
FYI I got SUCCESS! [0:36:33.390707] from my reverted-SSL-changes smokeTestRelease.py on Python 3.4.2 against the 6.5.1RC2 URL. (macOS/Python 3.5.1 reverted smoke tester is still running.)
It may be the case that you’re missing root certificates that I have (on both Linux and macOS), and that’s the reason SSL validation is failing for you.
What platform are you on? IIRC some Linux distros have ways of updating root certificate stores. (I’ve never had to do that myself though.)
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 1:54 PM, Joel Bernstein <jo...@gmail.com> wrote:
>
> I just ran the smoke tester and it failed in the part of code that I hadn't suppressed the SSL validation. So it's still an issue with my setup.
>
> I could try another version of python and see if that is the issue.
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 1:47 PM, Steve Rowe <sa...@gmail.com> wrote:
> AFAICT that error occurs very early in the smoke test process, with the first attempt to download the directory listing at the release URL. I’m running the reverted-SSL-changes smokeTestRelease.py on both Python 3.4.2 (Linux) and 3.5.1 (macOS), and both are way past that.
>
> Would you mind trying to run the smoke tester today after reverting your SSL changes? (Maybe it was a temporary problem for some reason.) AFAICT it will fail fast for you.
>
> I’m not sure if it makes sense to call the release vote yet, since the smoke tester as committed to branch_6_5 doesn’t work for you or for people with Python < 3.4.3. If the problem turns out to be a transient one for you, then I think we should revert your SSL changes to smokeTestRelease.py on branch_6_5 and respin.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 1:35 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > Here is the error from the smoke test:
> >
> > Traceback (most recent call last):
> >
> > File "dev-tools/scripts/smokeTestRelease.py", line 1483, in <module>
> >
> > main()
> >
> > File "dev-tools/scripts/smokeTestRelease.py", line 1427, in main
> >
> > smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir, c.is_signed, ' '.join(c.test_args))
> >
> > File "dev-tools/scripts/smokeTestRelease.py", line 1449, in smokeTest
> >
> > for text, subURL in getDirEntries(baseURL):
> >
> > File "dev-tools/scripts/smokeTestRelease.py", line 604, in getDirEntries
> >
> > links = getHREFs(urlString)
> >
> > File "dev-tools/scripts/smokeTestRelease.py", line 94, in getHREFs
> >
> > h.request('HEAD', url.path)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1239, in request
> >
> > self._send_request(method, url, body, headers, encode_chunked)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1285, in _send_request
> >
> > self.endheaders(body, encode_chunked=encode_chunked)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1234, in endheaders
> >
> > self._send_output(message_body, encode_chunked=encode_chunked)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1026, in _send_output
> >
> > self.send(msg)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 964, in send
> >
> > self.connect()
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1400, in connect
> >
> > server_hostname=server_hostname)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 401, in wrap_socket
> >
> > _context=self, _session=session)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 808, in __init__
> >
> > self.do_handshake()
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 1061, in do_handshake
> >
> > self._sslobj.do_handshake()
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 683, in do_handshake
> >
> > self._sslobj.do_handshake()
> >
> > ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 1:31 PM, Steve Rowe <sa...@gmail.com> wrote:
> > That’s the error you posted for buildAndPushRelease.py - are you saying that you got identical errors for both?
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 1:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >
> > > Python 3.6.1
> > >
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > This was the error:
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 504, in _call_chain
> > >
> > > result = func(*args)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 1361, in https_open
> > >
> > > context=self._context, check_hostname=self._check_hostname)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 1320, in do_open
> > >
> > > raise URLError(err)
> > >
> > > urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)>
> > >
> > >
> > >
> > > Perhaps the error was only local to my machine. But I didn't have this error when building RC1
> > >
> > >
> > >
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > Joel,
> > >
> > > I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t see any problems so far when I run it with my Python 3.4.2 with the 6.5.1RC2 URL. (Still in progress; Lucene distributions have downloaded so far.)
> > >
> > > What was the error that caused you to make the SSL changes to smokeTestRelease.py? And what version of Python are you using?
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > > > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >
> > > > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the first that supports the changes you made, so the smoke tester is failing for me:
> > > >
> > > > -----
> > > > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
> > > > content = urllib.request.urlopen(urlString, context=ctx).read().decode('utf-8')
> > > > TypeError: urlopen() got an unexpected keyword argument ‘context’
> > > > ------
> > > >
> > > > I’ll install a newer Python.
> > > >
> > > > --
> > > > Steve
> > > > www.lucidworks.com
> > > >
> > > >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>
> > > >> thanks
> > > >>
> > > >> Joel Bernstein
> > > >> http://joelsolr.blogspot.com/
> > > >>
> > > >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >> I’ll take a look.
> > > >>
> > > >> --
> > > >> Steve
> > > >> www.lucidworks.com
> > > >>
> > > >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>
> > > >>> I've uploaded the RC2 here https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d88652952ec3e2b3e0070/.
> > > >>>
> > > >>> But the smoke test breaks with SSL error in different spot when you smoke test from this URL. It's failing with a different command this time so the fix I used in other sports of smoke tester doesn't work.
> > > >>>
> > > >>> Steve, would you mind taking a look at this and pushing out a fix?
> > > >>>
> > > >>> Joel Bernstein
> > > >>> http://joelsolr.blogspot.com/
> > > >>>
> > > >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>> I was thinking that if buildAndPushRelease.py can identify problems early, the RM won’t have to later redo work when a problem is found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from auto-running precommit would be worth it.
> > > >>>
> > > >>> But I agree that the smoke tester should be heavy, since it’s possible that the RM had weird local conditions that weren’t caught by the release production tools.
> > > >>>
> > > >>> --
> > > >>> Steve
> > > >>> www.lucidworks.com
> > > >>>
> > > >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>
> > > >>>> They are both quite long processes. Perhaps we should look at eliminating some of the overlap?
> > > >>>>
> > > >>>> Since the smokeTesters is run by those voting on the release maybe this should be the heavier of the two.
> > > >>>>
> > > >>>> Joel Bernstein
> > > >>>> http://joelsolr.blogspot.com/
> > > >>>>
> > > >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>> Also, I think buildAndPushRelease.py should invoke “precommit" too, (near) where it runs 'ant clean test'.
> > > >>>>
> > > >>>> --
> > > >>>> Steve
> > > >>>> www.lucidworks.com
> > > >>>>
> > > >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>
> > > >>>>> That’s bizarre.
> > > >>>>>
> > > >>>>> The smoke tester runs ‘ant validate’, which does *not* include "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused imports are looked for).
> > > >>>>>
> > > >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and “documentation-lint”.
> > > >>>>>
> > > >>>>> Jenkins caught this not because of the smoke tester, but rather because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like “precommit”, runs “check-working-copy”, “validate”, and “documentation-lint” (among others).
> > > >>>>>
> > > >>>>> I think we should change the smoke tester to look at the same things as precommit,
> > > >>>>>
> > > >>>>> --
> > > >>>>> Steve
> > > >>>>> www.lucidworks.com
> > > >>>>>
> > > >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>
> > > >>>>>> Smoke testes passed as well
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> Joel Bernstein
> > > >>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>
> > > >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>> I guess precommit is only run as part of the smoke tester.
> > > >>>>>>
> > > >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>
> > > >>>>>>> Interesting the entire release process completed without complaining.
> > > >>>>>>>
> > > >>>>>>> Joel Bernstein
> > > >>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>
> > > >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>>> The unused import was the only problem; I’ve removed it on branch_6_5.
> > > >>>>>>>
> > > >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
> > > >>>>>>>
> > > >>>>>>> --
> > > >>>>>>> Steve
> > > >>>>>>> www.lucidworks.com
> > > >>>>>>>
> > > >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>>>>
> > > >>>>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
> > > >>>>>>>>
> > > >>>>>>>> --
> > > >>>>>>>> Steve
> > > >>>>>>>> www.lucidworks.com
> > > >>>>>>>>
> > > >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>>>>>
> > > >>>>>>>>> Done.
> > > >>>>>>>>>
> > > >>>>>>>>> --
> > > >>>>>>>>> Steve
> > > >>>>>>>>> www.lucidworks.com
> > > >>>>>>>>>
> > > >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>>>>>>
> > > >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > > >>>>>>>>>>
> > > >>>>>>>>>> --
> > > >>>>>>>>>> Steve
> > > >>>>>>>>>> www.lucidworks.com
> > > >>>>>>>>>>
> > > >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the back port.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>>>>>>> Joel,
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> --
> > > >>>>>>>>>>> Steve
> > > >>>>>>>>>>> www.lucidworks.com
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> e.g.:
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> cd ..
> > > >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> > > >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > > >>>>>>>>>>>> cd lucene-solr
> > > >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> --
> > > >>>>>>>>>>>> Steve
> > > >>>>>>>>>>>> www.lucidworks.com
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> So, I'm going to have to push this out.
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Let's first decide if this makes sense as the way forward.
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>>>>>> Steve, when I change the script to turn off verification I get the following error:
> > > >>>>>>>>>>>>> RuntimeError: git clone is dirty:
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> > > >>>>>>>>>>>>> Could it be anything to do with the fact that the signer is Semantic
> > > >>>>>>>>>>>>> and they are being actively distrusted by - at least - Google:
> > > >>>>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Regards,
> > > >>>>>>>>>>>>> Alex.
> > > >>>>>>>>>>>>> ----
> > > >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> > > >>>>>>>>>>>>>> was something that was integral to the process.
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> Hi Joel,
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > > >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> > > >>>>>>>>>>>>>>> archive.apache.org?
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
> > > >>>>>>>>>>>>>>> urllib):
> > > >>>>>>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> Short term, you could turn off certificate verification. The bottom
> > > >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
> > > >>>>>>>>>>>>>>> which is assumed in the other answers on the page), to turn off certificate
> > > >>>>>>>>>>>>>>> verification:
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> --
> > > >>>>>>>>>>>>>>> Steve
> > > >>>>>>>>>>>>>>> www.lucidworks.com
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> > > >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> > > >>>>>>>>>>>>>>>> wrote:
> > > >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > > >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> > > >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
> > > >>>>>>>>>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
> > > >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> Traceback (most recent call last):
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> main()
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> checkDOAPfiles(version)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> > > >>>>>>>>>>>>>>>> checkDOAPfiles
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> distpage = load(url)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File
> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>>>>>> line 223, in urlopen
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File
> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>>>>>> line 526, in open
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> response = self._open(req, data)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File
> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>>>>>> line 544, in _open
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> '_open', req)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File
> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>>>>>> line 504, in _call_chain
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> result = func(*args)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File
> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>>>>>> line 1361, in https_open
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File
> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>>>>>> line 1320, in do_open
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> raise URLError(err)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> > > >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> ---------------------------------------------------------------------
> > > >>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> ---------------------------------------------------------------------
> > > >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> ---------------------------------------------------------------------
> > > >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> ---------------------------------------------------------------------
> > > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> ---------------------------------------------------------------------
> > > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> ---------------------------------------------------------------------
> > > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>
> > > >>>>
> > > >>>> ---------------------------------------------------------------------
> > > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>> ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>
> > > >>
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: dev-help@lucene.apache.org
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
Ok, it works for me with Python 3.4.3. So the issue is with Python 3.6.1.
I will pull and respin.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 1:54 PM, Joel Bernstein <jo...@gmail.com> wrote:
> I just ran the smoke tester and it failed in the part of code that I
> hadn't suppressed the SSL validation. So it's still an issue with my setup.
>
> I could try another version of python and see if that is the issue.
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 1:47 PM, Steve Rowe <sa...@gmail.com> wrote:
>
>> AFAICT that error occurs very early in the smoke test process, with the
>> first attempt to download the directory listing at the release URL. I’m
>> running the reverted-SSL-changes smokeTestRelease.py on both Python 3.4.2
>> (Linux) and 3.5.1 (macOS), and both are way past that.
>>
>> Would you mind trying to run the smoke tester today after reverting your
>> SSL changes? (Maybe it was a temporary problem for some reason.) AFAICT
>> it will fail fast for you.
>>
>> I’m not sure if it makes sense to call the release vote yet, since the
>> smoke tester as committed to branch_6_5 doesn’t work for you or for people
>> with Python < 3.4.3. If the problem turns out to be a transient one for
>> you, then I think we should revert your SSL changes to smokeTestRelease.py
>> on branch_6_5 and respin.
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>> > On Apr 20, 2017, at 1:35 PM, Joel Bernstein <jo...@gmail.com> wrote:
>> >
>> > Here is the error from the smoke test:
>> >
>> > Traceback (most recent call last):
>> >
>> > File "dev-tools/scripts/smokeTestRelease.py", line 1483, in <module>
>> >
>> > main()
>> >
>> > File "dev-tools/scripts/smokeTestRelease.py", line 1427, in main
>> >
>> > smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir,
>> c.is_signed, ' '.join(c.test_args))
>> >
>> > File "dev-tools/scripts/smokeTestRelease.py", line 1449, in smokeTest
>> >
>> > for text, subURL in getDirEntries(baseURL):
>> >
>> > File "dev-tools/scripts/smokeTestRelease.py", line 604, in
>> getDirEntries
>> >
>> > links = getHREFs(urlString)
>> >
>> > File "dev-tools/scripts/smokeTestRelease.py", line 94, in getHREFs
>> >
>> > h.request('HEAD', url.path)
>> >
>> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>> line 1239, in request
>> >
>> > self._send_request(method, url, body, headers, encode_chunked)
>> >
>> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>> line 1285, in _send_request
>> >
>> > self.endheaders(body, encode_chunked=encode_chunked)
>> >
>> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>> line 1234, in endheaders
>> >
>> > self._send_output(message_body, encode_chunked=encode_chunked)
>> >
>> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>> line 1026, in _send_output
>> >
>> > self.send(msg)
>> >
>> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>> line 964, in send
>> >
>> > self.connect()
>> >
>> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
>> line 1400, in connect
>> >
>> > server_hostname=server_hostname)
>> >
>> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
>> line 401, in wrap_socket
>> >
>> > _context=self, _session=session)
>> >
>> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
>> line 808, in __init__
>> >
>> > self.do_handshake()
>> >
>> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
>> line 1061, in do_handshake
>> >
>> > self._sslobj.do_handshake()
>> >
>> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
>> line 683, in do_handshake
>> >
>> > self._sslobj.do_handshake()
>> >
>> > ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
>> failed (_ssl.c:749)
>> >
>> >
>> > Joel Bernstein
>> > http://joelsolr.blogspot.com/
>> >
>> > On Thu, Apr 20, 2017 at 1:31 PM, Steve Rowe <sa...@gmail.com> wrote:
>> > That’s the error you posted for buildAndPushRelease.py - are you saying
>> that you got identical errors for both?
>> >
>> > --
>> > Steve
>> > www.lucidworks.com
>> >
>> > > On Apr 20, 2017, at 1:28 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > >
>> > > Python 3.6.1
>> > >
>> > >
>> > > Joel Bernstein
>> > > http://joelsolr.blogspot.com/
>> > >
>> > > On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > > This was the error:
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> line 504, in _call_chain
>> > >
>> > > result = func(*args)
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> line 1361, in https_open
>> > >
>> > > context=self._context, check_hostname=self._check_hostname)
>> > >
>> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> line 1320, in do_open
>> > >
>> > > raise URLError(err)
>> > >
>> > > urllib.error.URLError: <urlopen error [SSL:
>> CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)>
>> > >
>> > >
>> > >
>> > > Perhaps the error was only local to my machine. But I didn't have
>> this error when building RC1
>> > >
>> > >
>> > >
>> > >
>> > > Joel Bernstein
>> > > http://joelsolr.blogspot.com/
>> > >
>> > > On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com> wrote:
>> > > Joel,
>> > >
>> > > I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t
>> see any problems so far when I run it with my Python 3.4.2 with the
>> 6.5.1RC2 URL. (Still in progress; Lucene distributions have downloaded so
>> far.)
>> > >
>> > > What was the error that caused you to make the SSL changes to
>> smokeTestRelease.py? And what version of Python are you using?
>> > >
>> > > --
>> > > Steve
>> > > www.lucidworks.com
>> > >
>> > > > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
>> > > >
>> > > > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the
>> first that supports the changes you made, so the smoke tester is failing
>> for me:
>> > > >
>> > > > -----
>> > > > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
>> > > > content = urllib.request.urlopen(urlString,
>> context=ctx).read().decode('utf-8')
>> > > > TypeError: urlopen() got an unexpected keyword argument ‘context’
>> > > > ------
>> > > >
>> > > > I’ll install a newer Python.
>> > > >
>> > > > --
>> > > > Steve
>> > > > www.lucidworks.com
>> > > >
>> > > >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > > >>
>> > > >> thanks
>> > > >>
>> > > >> Joel Bernstein
>> > > >> http://joelsolr.blogspot.com/
>> > > >>
>> > > >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > >> I’ll take a look.
>> > > >>
>> > > >> --
>> > > >> Steve
>> > > >> www.lucidworks.com
>> > > >>
>> > > >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > > >>>
>> > > >>> I've uploaded the RC2 here https://dist.apache.org/repos/
>> dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62
>> d88652952ec3e2b3e0070/.
>> > > >>>
>> > > >>> But the smoke test breaks with SSL error in different spot when
>> you smoke test from this URL. It's failing with a different command this
>> time so the fix I used in other sports of smoke tester doesn't work.
>> > > >>>
>> > > >>> Steve, would you mind taking a look at this and pushing out a fix?
>> > > >>>
>> > > >>> Joel Bernstein
>> > > >>> http://joelsolr.blogspot.com/
>> > > >>>
>> > > >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > >>> I was thinking that if buildAndPushRelease.py can identify
>> problems early, the RM won’t have to later redo work when a problem is
>> found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop
>> anyway) from auto-running precommit would be worth it.
>> > > >>>
>> > > >>> But I agree that the smoke tester should be heavy, since it’s
>> possible that the RM had weird local conditions that weren’t caught by the
>> release production tools.
>> > > >>>
>> > > >>> --
>> > > >>> Steve
>> > > >>> www.lucidworks.com
>> > > >>>
>> > > >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > > >>>>
>> > > >>>> They are both quite long processes. Perhaps we should look at
>> eliminating some of the overlap?
>> > > >>>>
>> > > >>>> Since the smokeTesters is run by those voting on the release
>> maybe this should be the heavier of the two.
>> > > >>>>
>> > > >>>> Joel Bernstein
>> > > >>>> http://joelsolr.blogspot.com/
>> > > >>>>
>> > > >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > >>>> Also, I think buildAndPushRelease.py should invoke “precommit"
>> too, (near) where it runs 'ant clean test'.
>> > > >>>>
>> > > >>>> --
>> > > >>>> Steve
>> > > >>>> www.lucidworks.com
>> > > >>>>
>> > > >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > >>>>>
>> > > >>>>> That’s bizarre.
>> > > >>>>>
>> > > >>>>> The smoke tester runs ‘ant validate’, which does *not* include
>> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
>> imports are looked for).
>> > > >>>>>
>> > > >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”,
>> “validate”, and “documentation-lint”.
>> > > >>>>>
>> > > >>>>> Jenkins caught this not because of the smoke tester, but rather
>> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
>> “precommit”, runs “check-working-copy”, “validate”, and
>> “documentation-lint” (among others).
>> > > >>>>>
>> > > >>>>> I think we should change the smoke tester to look at the same
>> things as precommit,
>> > > >>>>>
>> > > >>>>> --
>> > > >>>>> Steve
>> > > >>>>> www.lucidworks.com
>> > > >>>>>
>> > > >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > >>>>>>
>> > > >>>>>> Smoke testes passed as well
>> > > >>>>>>
>> > > >>>>>>
>> > > >>>>>> Joel Bernstein
>> > > >>>>>> http://joelsolr.blogspot.com/
>> > > >>>>>>
>> > > >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > >>>>>> I guess precommit is only run as part of the smoke tester.
>> > > >>>>>>
>> > > >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > >>>>>>>
>> > > >>>>>>> Interesting the entire release process completed without
>> complaining.
>> > > >>>>>>>
>> > > >>>>>>> Joel Bernstein
>> > > >>>>>>> http://joelsolr.blogspot.com/
>> > > >>>>>>>
>> > > >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > >>>>>>> The unused import was the only problem; I’ve removed it on
>> branch_6_5.
>> > > >>>>>>>
>> > > >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
>> > > >>>>>>>
>> > > >>>>>>> --
>> > > >>>>>>> Steve
>> > > >>>>>>> www.lucidworks.com
>> > > >>>>>>>
>> > > >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > >>>>>>>>
>> > > >>>>>>>> Crap, Jenkins found an unused import in my commit on
>> branch_6_5 :(. I forgot to run precommit. Doing so now.
>> > > >>>>>>>>
>> > > >>>>>>>> --
>> > > >>>>>>>> Steve
>> > > >>>>>>>> www.lucidworks.com
>> > > >>>>>>>>
>> > > >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > >>>>>>>>>
>> > > >>>>>>>>> Done.
>> > > >>>>>>>>>
>> > > >>>>>>>>> --
>> > > >>>>>>>>> Steve
>> > > >>>>>>>>> www.lucidworks.com
>> > > >>>>>>>>>
>> > > >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > > >>>>>>>>>>
>> > > >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>> > > >>>>>>>>>>
>> > > >>>>>>>>>> --
>> > > >>>>>>>>>> Steve
>> > > >>>>>>>>>> www.lucidworks.com
>> > > >>>>>>>>>>
>> > > >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > >>>>>>>>>>>
>> > > >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish
>> the back port.
>> > > >>>>>>>>>>>
>> > > >>>>>>>>>>> Joel Bernstein
>> > > >>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > >>>>>>>>>>>
>> > > >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <
>> sarowe@gmail.com> wrote:
>> > > >>>>>>>>>>> Joel,
>> > > >>>>>>>>>>>
>> > > >>>>>>>>>>> I know you’re in-process with RC2, but if you have to
>> restart for some reason, I’d like to include SOLR-10527.
>> > > >>>>>>>>>>>
>> > > >>>>>>>>>>> --
>> > > >>>>>>>>>>> Steve
>> > > >>>>>>>>>>> www.lucidworks.com
>> > > >>>>>>>>>>>
>> > > >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> I also had to change the smoke tester because of the SSL
>> issue. Which in theory means everyone else will have to as well. I'm
>> pushing out my changes to branch_6_5, so people can just update their
>> branch before running the smoke tester.
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> Joel Bernstein
>> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > >>>>>>>>>>>> Ok, I had to push out three changes to the branch but I
>> seemed to have moved passed this issue.
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> Joel Bernstein
>> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully the
>> changes will do the trick after they've been pushed.
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> Joel Bernstein
>> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <
>> sarowe@gmail.com> wrote:
>> > > >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make
>> modifications on the release branch, but you can’t test unless you commit
>> (and push).
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> Another alternative: make modifications in another
>> checkout, then invoke the script with from an unmodified source tree.
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> e.g.:
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> cd ..
>> > > >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr
>> is your checkout dir
>> > > >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/script
>> s/buildAndPushRelease.py
>> > > >>>>>>>>>>>> cd lucene-solr
>> > > >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>> …
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> (a shorter form of that is to make a copy the script
>> alone and invoke the modified version from your checkout)
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> --
>> > > >>>>>>>>>>>> Steve
>> > > >>>>>>>>>>>> www.lucidworks.com
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
>> origin/branch_6_5.." output is:
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>> So, I'm going to have to push this out.
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>> Let's first decide if this makes sense as the way
>> forward.
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>> Joel Bernstein
>> > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > >>>>>>>>>>>>> Steve, when I change the script to turn off
>> verification I get the following error:
>> > > >>>>>>>>>>>>> RuntimeError: git clone is dirty:
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>> So as part of the work around I think I'm going to have
>> to commit locally and then revert locally. Does that make sense to you as
>> the way forward?
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>> Joel Bernstein
>> > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>> arafalov@gmail.com> wrote:
>> > > >>>>>>>>>>>>> Could it be anything to do with the fact that the
>> signer is Semantic
>> > > >>>>>>>>>>>>> and they are being actively distrusted by - at least -
>> Google:
>> > > >>>>>>>>>>>>> http://www.securityweek.com/go
>> ogle-stops-trusting-symantec-issued-certificates
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>> Regards,
>> > > >>>>>>>>>>>>> Alex.
>> > > >>>>>>>>>>>>> ----
>> > > >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users,
>> new and experienced
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure
>> if cert verification
>> > > >>>>>>>>>>>>>> was something that was integral to the process.
>> > > >>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>> Joel Bernstein
>> > > >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > >>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
>> sarowe@gmail.com> wrote:
>> > > >>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>> Hi Joel,
>> > > >>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>> > > >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication>
>> has been enabled on
>> > > >>>>>>>>>>>>>>> archive.apache.org?
>> > > >>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT
>> an alternative to
>> > > >>>>>>>>>>>>>>> urllib):
>> > > >>>>>>>>>>>>>>> <http://docs.python-requests.o
>> rg/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>> > > >>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>> Short term, you could turn off certificate
>> verification. The bottom
>> > > >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib
>> instead of urllib2,
>> > > >>>>>>>>>>>>>>> which is assumed in the other answers on the page),
>> to turn off certificate
>> > > >>>>>>>>>>>>>>> verification:
>> > > >>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>> <http://stackoverflow.com/ques
>> tions/19268548/python-ignore-certicate-validation-urllib2>
>> > > >>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>> --
>> > > >>>>>>>>>>>>>>> Steve
>> > > >>>>>>>>>>>>>>> www.lucidworks.com
>> > > >>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL
>> cert for
>> > > >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> Joel Bernstein
>> > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>> joelsolr@gmail.com>
>> > > >>>>>>>>>>>>>>>> wrote:
>> > > >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>> > > >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>> --push-local
>> > > >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> I believe this is same basic command I used for RC1.
>> But this time I got
>> > > >>>>>>>>>>>>>>>> a new error. At first I thought it might be
>> incorrect keystore password but
>> > > >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what
>> the issue is?
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> Traceback (most recent call last):
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>> line 313, in <module>
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> main()
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>> line 294, in main
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id,
>> c.key_password)
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>> line 98, in prepare
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> checkDOAPfiles(version)
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>> line 143, in
>> > > >>>>>>>>>>>>>>>> checkDOAPfiles
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> distpage = load(url)
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>> line 67, in load
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> content = urllib.request.urlopen(urlStri
>> ng).read().decode('utf-8')
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> File
>> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > > >>>>>>>>>>>>>>>> line 223, in urlopen
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> File
>> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > > >>>>>>>>>>>>>>>> line 526, in open
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> response = self._open(req, data)
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> File
>> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > > >>>>>>>>>>>>>>>> line 544, in _open
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> '_open', req)
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> File
>> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > > >>>>>>>>>>>>>>>> line 504, in _call_chain
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> result = func(*args)
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> File
>> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > > >>>>>>>>>>>>>>>> line 1361, in https_open
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hos
>> tname)
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> File
>> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > > >>>>>>>>>>>>>>>> line 1320, in do_open
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> raise URLError(err)
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>> CERTIFICATE_VERIFY_FAILED]
>> > > >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>> Joel Bernstein
>> > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> > > >>>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>> ------------------------------
>> ---------------------------------------
>> > > >>>>>>>>>>>>>>> To unsubscribe, e-mail:
>> dev-unsubscribe@lucene.apache.org
>> > > >>>>>>>>>>>>>>> For additional commands, e-mail:
>> dev-help@lucene.apache.org
>> > > >>>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>> ------------------------------
>> ---------------------------------------
>> > > >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
>> org
>> > > >>>>>>>>>>>>> For additional commands, e-mail:
>> dev-help@lucene.apache.org
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>>
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>> ------------------------------
>> ---------------------------------------
>> > > >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
>> org
>> > > >>>>>>>>>>>> For additional commands, e-mail:
>> dev-help@lucene.apache.org
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>>
>> > > >>>>>>>>>>>
>> > > >>>>>>>>>>>
>> > > >>>>>>>>>>> ------------------------------
>> ---------------------------------------
>> > > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > >>>>>>>>>>> For additional commands, e-mail:
>> dev-help@lucene.apache.org
>> > > >>>>>>>>>>>
>> > > >>>>>>>>>>>
>> > > >>>>>>>>>>
>> > > >>>>>>>>>
>> > > >>>>>>>>
>> > > >>>>>>>
>> > > >>>>>>>
>> > > >>>>>>> ------------------------------------------------------------
>> ---------
>> > > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > > >>>>>>>
>> > > >>>>>>>
>> > > >>>>>>
>> > > >>>>>>
>> > > >>>>>> ------------------------------------------------------------
>> ---------
>> > > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > > >>>>>>
>> > > >>>>>>
>> > > >>>>>
>> > > >>>>
>> > > >>>>
>> > > >>>> ------------------------------------------------------------
>> ---------
>> > > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > > >>>>
>> > > >>>>
>> > > >>>
>> > > >>>
>> > > >>> ------------------------------------------------------------
>> ---------
>> > > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > >>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > > >>>
>> > > >>>
>> > > >>
>> > > >>
>> > > >> ------------------------------------------------------------
>> ---------
>> > > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > >> For additional commands, e-mail: dev-help@lucene.apache.org
>> > > >>
>> > > >>
>> > > >
>> > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > > For additional commands, e-mail: dev-help@lucene.apache.org
>> > >
>> > >
>> > >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > For additional commands, e-mail: dev-help@lucene.apache.org
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
I just ran the smoke tester and it failed in the part of code that I hadn't
suppressed the SSL validation. So it's still an issue with my setup.
I could try another version of python and see if that is the issue.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 1:47 PM, Steve Rowe <sa...@gmail.com> wrote:
> AFAICT that error occurs very early in the smoke test process, with the
> first attempt to download the directory listing at the release URL. I’m
> running the reverted-SSL-changes smokeTestRelease.py on both Python 3.4.2
> (Linux) and 3.5.1 (macOS), and both are way past that.
>
> Would you mind trying to run the smoke tester today after reverting your
> SSL changes? (Maybe it was a temporary problem for some reason.) AFAICT
> it will fail fast for you.
>
> I’m not sure if it makes sense to call the release vote yet, since the
> smoke tester as committed to branch_6_5 doesn’t work for you or for people
> with Python < 3.4.3. If the problem turns out to be a transient one for
> you, then I think we should revert your SSL changes to smokeTestRelease.py
> on branch_6_5 and respin.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 1:35 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > Here is the error from the smoke test:
> >
> > Traceback (most recent call last):
> >
> > File "dev-tools/scripts/smokeTestRelease.py", line 1483, in <module>
> >
> > main()
> >
> > File "dev-tools/scripts/smokeTestRelease.py", line 1427, in main
> >
> > smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir,
> c.is_signed, ' '.join(c.test_args))
> >
> > File "dev-tools/scripts/smokeTestRelease.py", line 1449, in smokeTest
> >
> > for text, subURL in getDirEntries(baseURL):
> >
> > File "dev-tools/scripts/smokeTestRelease.py", line 604, in
> getDirEntries
> >
> > links = getHREFs(urlString)
> >
> > File "dev-tools/scripts/smokeTestRelease.py", line 94, in getHREFs
> >
> > h.request('HEAD', url.path)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
> line 1239, in request
> >
> > self._send_request(method, url, body, headers, encode_chunked)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
> line 1285, in _send_request
> >
> > self.endheaders(body, encode_chunked=encode_chunked)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
> line 1234, in endheaders
> >
> > self._send_output(message_body, encode_chunked=encode_chunked)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
> line 1026, in _send_output
> >
> > self.send(msg)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
> line 964, in send
> >
> > self.connect()
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
> line 1400, in connect
> >
> > server_hostname=server_hostname)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
> line 401, in wrap_socket
> >
> > _context=self, _session=session)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
> line 808, in __init__
> >
> > self.do_handshake()
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
> line 1061, in do_handshake
> >
> > self._sslobj.do_handshake()
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
> line 683, in do_handshake
> >
> > self._sslobj.do_handshake()
> >
> > ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
> (_ssl.c:749)
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 1:31 PM, Steve Rowe <sa...@gmail.com> wrote:
> > That’s the error you posted for buildAndPushRelease.py - are you saying
> that you got identical errors for both?
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 1:28 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >
> > > Python 3.6.1
> > >
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > This was the error:
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 504, in _call_chain
> > >
> > > result = func(*args)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 1361, in https_open
> > >
> > > context=self._context, check_hostname=self._check_hostname)
> > >
> > > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 1320, in do_open
> > >
> > > raise URLError(err)
> > >
> > > urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> certificate verify failed (_ssl.c:749)>
> > >
> > >
> > >
> > > Perhaps the error was only local to my machine. But I didn't have this
> error when building RC1
> > >
> > >
> > >
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > Joel,
> > >
> > > I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t see
> any problems so far when I run it with my Python 3.4.2 with the 6.5.1RC2
> URL. (Still in progress; Lucene distributions have downloaded so far.)
> > >
> > > What was the error that caused you to make the SSL changes to
> smokeTestRelease.py? And what version of Python are you using?
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > > > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >
> > > > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the
> first that supports the changes you made, so the smoke tester is failing
> for me:
> > > >
> > > > -----
> > > > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
> > > > content = urllib.request.urlopen(urlString,
> context=ctx).read().decode('utf-8')
> > > > TypeError: urlopen() got an unexpected keyword argument ‘context’
> > > > ------
> > > >
> > > > I’ll install a newer Python.
> > > >
> > > > --
> > > > Steve
> > > > www.lucidworks.com
> > > >
> > > >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > >>
> > > >> thanks
> > > >>
> > > >> Joel Bernstein
> > > >> http://joelsolr.blogspot.com/
> > > >>
> > > >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >> I’ll take a look.
> > > >>
> > > >> --
> > > >> Steve
> > > >> www.lucidworks.com
> > > >>
> > > >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > >>>
> > > >>> I've uploaded the RC2 here https://dist.apache.org/repos/
> dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d8865295
> 2ec3e2b3e0070/.
> > > >>>
> > > >>> But the smoke test breaks with SSL error in different spot when
> you smoke test from this URL. It's failing with a different command this
> time so the fix I used in other sports of smoke tester doesn't work.
> > > >>>
> > > >>> Steve, would you mind taking a look at this and pushing out a fix?
> > > >>>
> > > >>> Joel Bernstein
> > > >>> http://joelsolr.blogspot.com/
> > > >>>
> > > >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>> I was thinking that if buildAndPushRelease.py can identify
> problems early, the RM won’t have to later redo work when a problem is
> found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop
> anyway) from auto-running precommit would be worth it.
> > > >>>
> > > >>> But I agree that the smoke tester should be heavy, since it’s
> possible that the RM had weird local conditions that weren’t caught by the
> release production tools.
> > > >>>
> > > >>> --
> > > >>> Steve
> > > >>> www.lucidworks.com
> > > >>>
> > > >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > >>>>
> > > >>>> They are both quite long processes. Perhaps we should look at
> eliminating some of the overlap?
> > > >>>>
> > > >>>> Since the smokeTesters is run by those voting on the release
> maybe this should be the heavier of the two.
> > > >>>>
> > > >>>> Joel Bernstein
> > > >>>> http://joelsolr.blogspot.com/
> > > >>>>
> > > >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>> Also, I think buildAndPushRelease.py should invoke “precommit"
> too, (near) where it runs 'ant clean test'.
> > > >>>>
> > > >>>> --
> > > >>>> Steve
> > > >>>> www.lucidworks.com
> > > >>>>
> > > >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>>>
> > > >>>>> That’s bizarre.
> > > >>>>>
> > > >>>>> The smoke tester runs ‘ant validate’, which does *not* include
> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
> imports are looked for).
> > > >>>>>
> > > >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”,
> “validate”, and “documentation-lint”.
> > > >>>>>
> > > >>>>> Jenkins caught this not because of the smoke tester, but rather
> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
> “precommit”, runs “check-working-copy”, “validate”, and
> “documentation-lint” (among others).
> > > >>>>>
> > > >>>>> I think we should change the smoke tester to look at the same
> things as precommit,
> > > >>>>>
> > > >>>>> --
> > > >>>>> Steve
> > > >>>>> www.lucidworks.com
> > > >>>>>
> > > >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > >>>>>>
> > > >>>>>> Smoke testes passed as well
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> Joel Bernstein
> > > >>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>
> > > >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>>>> I guess precommit is only run as part of the smoke tester.
> > > >>>>>>
> > > >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>
> > > >>>>>>> Interesting the entire release process completed without
> complaining.
> > > >>>>>>>
> > > >>>>>>> Joel Bernstein
> > > >>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>
> > > >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>>>>> The unused import was the only problem; I’ve removed it on
> branch_6_5.
> > > >>>>>>>
> > > >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
> > > >>>>>>>
> > > >>>>>>> --
> > > >>>>>>> Steve
> > > >>>>>>> www.lucidworks.com
> > > >>>>>>>
> > > >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>>>>>>
> > > >>>>>>>> Crap, Jenkins found an unused import in my commit on
> branch_6_5 :(. I forgot to run precommit. Doing so now.
> > > >>>>>>>>
> > > >>>>>>>> --
> > > >>>>>>>> Steve
> > > >>>>>>>> www.lucidworks.com
> > > >>>>>>>>
> > > >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>>>>>>>
> > > >>>>>>>>> Done.
> > > >>>>>>>>>
> > > >>>>>>>>> --
> > > >>>>>>>>> Steve
> > > >>>>>>>>> www.lucidworks.com
> > > >>>>>>>>>
> > > >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>>>>>>>>
> > > >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > > >>>>>>>>>>
> > > >>>>>>>>>> --
> > > >>>>>>>>>> Steve
> > > >>>>>>>>>> www.lucidworks.com
> > > >>>>>>>>>>
> > > >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish
> the back port.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <
> sarowe@gmail.com> wrote:
> > > >>>>>>>>>>> Joel,
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> I know you’re in-process with RC2, but if you have to
> restart for some reason, I’d like to include SOLR-10527.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> --
> > > >>>>>>>>>>> Steve
> > > >>>>>>>>>>> www.lucidworks.com
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> I also had to change the smoke tester because of the SSL
> issue. Which in theory means everyone else will have to as well. I'm
> pushing out my changes to branch_6_5, so people can just update their
> branch before running the smoke tester.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>>>>> Ok, I had to push out three changes to the branch but I
> seemed to have moved passed this issue.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully the
> changes will do the trick after they've been pushed.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <
> sarowe@gmail.com> wrote:
> > > >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make
> modifications on the release branch, but you can’t test unless you commit
> (and push).
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Another alternative: make modifications in another
> checkout, then invoke the script with from an unmodified source tree.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> e.g.:
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> cd ..
> > > >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is
> your checkout dir
> > > >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/
> scripts/buildAndPushRelease.py
> > > >>>>>>>>>>>> cd lucene-solr
> > > >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> …
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> (a shorter form of that is to make a copy the script
> alone and invoke the modified version from your checkout)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> --
> > > >>>>>>>>>>>> Steve
> > > >>>>>>>>>>>> www.lucidworks.com
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
> origin/branch_6_5.." output is:
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> So, I'm going to have to push this out.
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Let's first decide if this makes sense as the way
> forward.
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>>>>>> Steve, when I change the script to turn off verification
> I get the following error:
> > > >>>>>>>>>>>>> RuntimeError: git clone is dirty:
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> So as part of the work around I think I'm going to have
> to commit locally and then revert locally. Does that make sense to you as
> the way forward?
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
> arafalov@gmail.com> wrote:
> > > >>>>>>>>>>>>> Could it be anything to do with the fact that the signer
> is Semantic
> > > >>>>>>>>>>>>> and they are being actively distrusted by - at least -
> Google:
> > > >>>>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> Regards,
> > > >>>>>>>>>>>>> Alex.
> > > >>>>>>>>>>>>> ----
> > > >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users,
> new and experienced
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure
> if cert verification
> > > >>>>>>>>>>>>>> was something that was integral to the process.
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
> sarowe@gmail.com> wrote:
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> Hi Joel,
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > > >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication>
> has been enabled on
> > > >>>>>>>>>>>>>>> archive.apache.org?
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT
> an alternative to
> > > >>>>>>>>>>>>>>> urllib):
> > > >>>>>>>>>>>>>>> <http://docs.python-requests.
> org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> Short term, you could turn off certificate
> verification. The bottom
> > > >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib
> instead of urllib2,
> > > >>>>>>>>>>>>>>> which is assumed in the other answers on the page), to
> turn off certificate
> > > >>>>>>>>>>>>>>> verification:
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> --
> > > >>>>>>>>>>>>>>> Steve
> > > >>>>>>>>>>>>>>> www.lucidworks.com
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL
> cert for
> > > >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
> joelsolr@gmail.com>
> > > >>>>>>>>>>>>>>>> wrote:
> > > >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > > >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
> --push-local
> > > >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> I believe this is same basic command I used for RC1.
> But this time I got
> > > >>>>>>>>>>>>>>>> a new error. At first I thought it might be incorrect
> keystore password but
> > > >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the
> issue is?
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> Traceback (most recent call last):
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
> line 313, in <module>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> main()
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
> line 294, in main
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id,
> c.key_password)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
> line 98, in prepare
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> checkDOAPfiles(version)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
> line 143, in
> > > >>>>>>>>>>>>>>>> checkDOAPfiles
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> distpage = load(url)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
> line 67, in load
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> content = urllib.request.urlopen(
> urlString).read().decode('utf-8')
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File
> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.
> framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>>>>>> line 223, in urlopen
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File
> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.
> framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>>>>>> line 526, in open
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> response = self._open(req, data)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File
> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.
> framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>>>>>> line 544, in _open
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> '_open', req)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File
> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.
> framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>>>>>> line 504, in _call_chain
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> result = func(*args)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File
> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.
> framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>>>>>> line 1361, in https_open
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_
> hostname)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> File
> > > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.
> framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>>>>>> line 1320, in do_open
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> raise URLError(err)
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> > > >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> ------------------------------
> ---------------------------------------
> > > >>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
> org
> > > >>>>>>>>>>>>>>> For additional commands, e-mail:
> dev-help@lucene.apache.org
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> ------------------------------
> ---------------------------------------
> > > >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
> org
> > > >>>>>>>>>>>>> For additional commands, e-mail:
> dev-help@lucene.apache.org
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> ------------------------------
> ---------------------------------------
> > > >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>>>>>> For additional commands, e-mail:
> dev-help@lucene.apache.org
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> ------------------------------
> ---------------------------------------
> > > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>>>>> For additional commands, e-mail:
> dev-help@lucene.apache.org
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> ------------------------------------------------------------
> ---------
> > > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> ------------------------------------------------------------
> ---------
> > > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>
> > > >>>>
> > > >>>> ------------------------------------------------------------
> ---------
> > > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>> ------------------------------------------------------------
> ---------
> > > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >> ------------------------------------------------------------
> ---------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>
> > > >>
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: dev-help@lucene.apache.org
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
AFAICT that error occurs very early in the smoke test process, with the first attempt to download the directory listing at the release URL. I’m running the reverted-SSL-changes smokeTestRelease.py on both Python 3.4.2 (Linux) and 3.5.1 (macOS), and both are way past that.
Would you mind trying to run the smoke tester today after reverting your SSL changes? (Maybe it was a temporary problem for some reason.) AFAICT it will fail fast for you.
I’m not sure if it makes sense to call the release vote yet, since the smoke tester as committed to branch_6_5 doesn’t work for you or for people with Python < 3.4.3. If the problem turns out to be a transient one for you, then I think we should revert your SSL changes to smokeTestRelease.py on branch_6_5 and respin.
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 1:35 PM, Joel Bernstein <jo...@gmail.com> wrote:
>
> Here is the error from the smoke test:
>
> Traceback (most recent call last):
>
> File "dev-tools/scripts/smokeTestRelease.py", line 1483, in <module>
>
> main()
>
> File "dev-tools/scripts/smokeTestRelease.py", line 1427, in main
>
> smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir, c.is_signed, ' '.join(c.test_args))
>
> File "dev-tools/scripts/smokeTestRelease.py", line 1449, in smokeTest
>
> for text, subURL in getDirEntries(baseURL):
>
> File "dev-tools/scripts/smokeTestRelease.py", line 604, in getDirEntries
>
> links = getHREFs(urlString)
>
> File "dev-tools/scripts/smokeTestRelease.py", line 94, in getHREFs
>
> h.request('HEAD', url.path)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1239, in request
>
> self._send_request(method, url, body, headers, encode_chunked)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1285, in _send_request
>
> self.endheaders(body, encode_chunked=encode_chunked)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1234, in endheaders
>
> self._send_output(message_body, encode_chunked=encode_chunked)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1026, in _send_output
>
> self.send(msg)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 964, in send
>
> self.connect()
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py", line 1400, in connect
>
> server_hostname=server_hostname)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 401, in wrap_socket
>
> _context=self, _session=session)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 808, in __init__
>
> self.do_handshake()
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 1061, in do_handshake
>
> self._sslobj.do_handshake()
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py", line 683, in do_handshake
>
> self._sslobj.do_handshake()
>
> ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 1:31 PM, Steve Rowe <sa...@gmail.com> wrote:
> That’s the error you posted for buildAndPushRelease.py - are you saying that you got identical errors for both?
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 1:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > Python 3.6.1
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > This was the error:
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 504, in _call_chain
> >
> > result = func(*args)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 1361, in https_open
> >
> > context=self._context, check_hostname=self._check_hostname)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 1320, in do_open
> >
> > raise URLError(err)
> >
> > urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)>
> >
> >
> >
> > Perhaps the error was only local to my machine. But I didn't have this error when building RC1
> >
> >
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com> wrote:
> > Joel,
> >
> > I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t see any problems so far when I run it with my Python 3.4.2 with the 6.5.1RC2 URL. (Still in progress; Lucene distributions have downloaded so far.)
> >
> > What was the error that caused you to make the SSL changes to smokeTestRelease.py? And what version of Python are you using?
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >
> > > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the first that supports the changes you made, so the smoke tester is failing for me:
> > >
> > > -----
> > > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
> > > content = urllib.request.urlopen(urlString, context=ctx).read().decode('utf-8')
> > > TypeError: urlopen() got an unexpected keyword argument ‘context’
> > > ------
> > >
> > > I’ll install a newer Python.
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>
> > >> thanks
> > >>
> > >> Joel Bernstein
> > >> http://joelsolr.blogspot.com/
> > >>
> > >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >> I’ll take a look.
> > >>
> > >> --
> > >> Steve
> > >> www.lucidworks.com
> > >>
> > >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>
> > >>> I've uploaded the RC2 here https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d88652952ec3e2b3e0070/.
> > >>>
> > >>> But the smoke test breaks with SSL error in different spot when you smoke test from this URL. It's failing with a different command this time so the fix I used in other sports of smoke tester doesn't work.
> > >>>
> > >>> Steve, would you mind taking a look at this and pushing out a fix?
> > >>>
> > >>> Joel Bernstein
> > >>> http://joelsolr.blogspot.com/
> > >>>
> > >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >>> I was thinking that if buildAndPushRelease.py can identify problems early, the RM won’t have to later redo work when a problem is found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from auto-running precommit would be worth it.
> > >>>
> > >>> But I agree that the smoke tester should be heavy, since it’s possible that the RM had weird local conditions that weren’t caught by the release production tools.
> > >>>
> > >>> --
> > >>> Steve
> > >>> www.lucidworks.com
> > >>>
> > >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>
> > >>>> They are both quite long processes. Perhaps we should look at eliminating some of the overlap?
> > >>>>
> > >>>> Since the smokeTesters is run by those voting on the release maybe this should be the heavier of the two.
> > >>>>
> > >>>> Joel Bernstein
> > >>>> http://joelsolr.blogspot.com/
> > >>>>
> > >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>> Also, I think buildAndPushRelease.py should invoke “precommit" too, (near) where it runs 'ant clean test'.
> > >>>>
> > >>>> --
> > >>>> Steve
> > >>>> www.lucidworks.com
> > >>>>
> > >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>
> > >>>>> That’s bizarre.
> > >>>>>
> > >>>>> The smoke tester runs ‘ant validate’, which does *not* include "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused imports are looked for).
> > >>>>>
> > >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and “documentation-lint”.
> > >>>>>
> > >>>>> Jenkins caught this not because of the smoke tester, but rather because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like “precommit”, runs “check-working-copy”, “validate”, and “documentation-lint” (among others).
> > >>>>>
> > >>>>> I think we should change the smoke tester to look at the same things as precommit,
> > >>>>>
> > >>>>> --
> > >>>>> Steve
> > >>>>> www.lucidworks.com
> > >>>>>
> > >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>
> > >>>>>> Smoke testes passed as well
> > >>>>>>
> > >>>>>>
> > >>>>>> Joel Bernstein
> > >>>>>> http://joelsolr.blogspot.com/
> > >>>>>>
> > >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>> I guess precommit is only run as part of the smoke tester.
> > >>>>>>
> > >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>
> > >>>>>>> Interesting the entire release process completed without complaining.
> > >>>>>>>
> > >>>>>>> Joel Bernstein
> > >>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>
> > >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>> The unused import was the only problem; I’ve removed it on branch_6_5.
> > >>>>>>>
> > >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
> > >>>>>>>
> > >>>>>>> --
> > >>>>>>> Steve
> > >>>>>>> www.lucidworks.com
> > >>>>>>>
> > >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>>>
> > >>>>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
> > >>>>>>>>
> > >>>>>>>> --
> > >>>>>>>> Steve
> > >>>>>>>> www.lucidworks.com
> > >>>>>>>>
> > >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>>>>
> > >>>>>>>>> Done.
> > >>>>>>>>>
> > >>>>>>>>> --
> > >>>>>>>>> Steve
> > >>>>>>>>> www.lucidworks.com
> > >>>>>>>>>
> > >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>>>>>
> > >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > >>>>>>>>>>
> > >>>>>>>>>> --
> > >>>>>>>>>> Steve
> > >>>>>>>>>> www.lucidworks.com
> > >>>>>>>>>>
> > >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>>>>
> > >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the back port.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>
> > >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>>>>>> Joel,
> > >>>>>>>>>>>
> > >>>>>>>>>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
> > >>>>>>>>>>>
> > >>>>>>>>>>> --
> > >>>>>>>>>>> Steve
> > >>>>>>>>>>> www.lucidworks.com
> > >>>>>>>>>>>
> > >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> e.g.:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> cd ..
> > >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> > >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > >>>>>>>>>>>> cd lucene-solr
> > >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> --
> > >>>>>>>>>>>> Steve
> > >>>>>>>>>>>> www.lucidworks.com
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> So, I'm going to have to push this out.
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Let's first decide if this makes sense as the way forward.
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>>>>>> Steve, when I change the script to turn off verification I get the following error:
> > >>>>>>>>>>>>> RuntimeError: git clone is dirty:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> > >>>>>>>>>>>>> Could it be anything to do with the fact that the signer is Semantic
> > >>>>>>>>>>>>> and they are being actively distrusted by - at least - Google:
> > >>>>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Regards,
> > >>>>>>>>>>>>> Alex.
> > >>>>>>>>>>>>> ----
> > >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> > >>>>>>>>>>>>>> was something that was integral to the process.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Hi Joel,
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> > >>>>>>>>>>>>>>> archive.apache.org?
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
> > >>>>>>>>>>>>>>> urllib):
> > >>>>>>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Short term, you could turn off certificate verification. The bottom
> > >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
> > >>>>>>>>>>>>>>> which is assumed in the other answers on the page), to turn off certificate
> > >>>>>>>>>>>>>>> verification:
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>> Steve
> > >>>>>>>>>>>>>>> www.lucidworks.com
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> > >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> > >>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> > >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
> > >>>>>>>>>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
> > >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> Traceback (most recent call last):
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> main()
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> checkDOAPfiles(version)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> > >>>>>>>>>>>>>>>> checkDOAPfiles
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> distpage = load(url)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File
> > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>>>>>>>>> line 223, in urlopen
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File
> > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>>>>>>>>> line 526, in open
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> response = self._open(req, data)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File
> > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>>>>>>>>> line 544, in _open
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> '_open', req)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File
> > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>>>>>>>>> line 504, in _call_chain
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> result = func(*args)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File
> > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>>>>>>>>> line 1361, in https_open
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File
> > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>>>>>>>>> line 1320, in do_open
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> raise URLError(err)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> > >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> ---------------------------------------------------------------------
> > >>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> ---------------------------------------------------------------------
> > >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> ---------------------------------------------------------------------
> > >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> ---------------------------------------------------------------------
> > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> ---------------------------------------------------------------------
> > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> ---------------------------------------------------------------------
> > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>
> > >>>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>
> > >>
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
Here is the error from the smoke test:
Traceback (most recent call last):
File "dev-tools/scripts/smokeTestRelease.py", line 1483, in <module>
main()
File "dev-tools/scripts/smokeTestRelease.py", line 1427, in main
smokeTest(c.java, c.url, c.revision, c.version, c.tmp_dir, c.is_signed,
' '.join(c.test_args))
File "dev-tools/scripts/smokeTestRelease.py", line 1449, in smokeTest
for text, subURL in getDirEntries(baseURL):
File "dev-tools/scripts/smokeTestRelease.py", line 604, in getDirEntries
links = getHREFs(urlString)
File "dev-tools/scripts/smokeTestRelease.py", line 94, in getHREFs
h.request('HEAD', url.path)
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
line 1239, in request
self._send_request(method, url, body, headers, encode_chunked)
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
line 1285, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
line 1234, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
line 1026, in _send_output
self.send(msg)
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
line 964, in send
self.connect()
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/http/client.py",
line 1400, in connect
server_hostname=server_hostname)
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
line 401, in wrap_socket
_context=self, _session=session)
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
line 808, in __init__
self.do_handshake()
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
line 1061, in do_handshake
self._sslobj.do_handshake()
File
"/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/ssl.py",
line 683, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
(_ssl.c:749)
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 1:31 PM, Steve Rowe <sa...@gmail.com> wrote:
> That’s the error you posted for buildAndPushRelease.py - are you saying
> that you got identical errors for both?
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 1:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > Python 3.6.1
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > This was the error:
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 504, in _call_chain
> >
> > result = func(*args)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 1361, in https_open
> >
> > context=self._context, check_hostname=self._check_hostname)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 1320, in do_open
> >
> > raise URLError(err)
> >
> > urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> certificate verify failed (_ssl.c:749)>
> >
> >
> >
> > Perhaps the error was only local to my machine. But I didn't have this
> error when building RC1
> >
> >
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com> wrote:
> > Joel,
> >
> > I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t see
> any problems so far when I run it with my Python 3.4.2 with the 6.5.1RC2
> URL. (Still in progress; Lucene distributions have downloaded so far.)
> >
> > What was the error that caused you to make the SSL changes to
> smokeTestRelease.py? And what version of Python are you using?
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >
> > > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the first
> that supports the changes you made, so the smoke tester is failing for me:
> > >
> > > -----
> > > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
> > > content = urllib.request.urlopen(urlString,
> context=ctx).read().decode('utf-8')
> > > TypeError: urlopen() got an unexpected keyword argument ‘context’
> > > ------
> > >
> > > I’ll install a newer Python.
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>
> > >> thanks
> > >>
> > >> Joel Bernstein
> > >> http://joelsolr.blogspot.com/
> > >>
> > >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >> I’ll take a look.
> > >>
> > >> --
> > >> Steve
> > >> www.lucidworks.com
> > >>
> > >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>>
> > >>> I've uploaded the RC2 here https://dist.apache.org/repos/
> dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d8865295
> 2ec3e2b3e0070/.
> > >>>
> > >>> But the smoke test breaks with SSL error in different spot when you
> smoke test from this URL. It's failing with a different command this time
> so the fix I used in other sports of smoke tester doesn't work.
> > >>>
> > >>> Steve, would you mind taking a look at this and pushing out a fix?
> > >>>
> > >>> Joel Bernstein
> > >>> http://joelsolr.blogspot.com/
> > >>>
> > >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>> I was thinking that if buildAndPushRelease.py can identify problems
> early, the RM won’t have to later redo work when a problem is found, e.g.
> by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from
> auto-running precommit would be worth it.
> > >>>
> > >>> But I agree that the smoke tester should be heavy, since it’s
> possible that the RM had weird local conditions that weren’t caught by the
> release production tools.
> > >>>
> > >>> --
> > >>> Steve
> > >>> www.lucidworks.com
> > >>>
> > >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>>>
> > >>>> They are both quite long processes. Perhaps we should look at
> eliminating some of the overlap?
> > >>>>
> > >>>> Since the smokeTesters is run by those voting on the release maybe
> this should be the heavier of the two.
> > >>>>
> > >>>> Joel Bernstein
> > >>>> http://joelsolr.blogspot.com/
> > >>>>
> > >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>>> Also, I think buildAndPushRelease.py should invoke “precommit" too,
> (near) where it runs 'ant clean test'.
> > >>>>
> > >>>> --
> > >>>> Steve
> > >>>> www.lucidworks.com
> > >>>>
> > >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>
> > >>>>> That’s bizarre.
> > >>>>>
> > >>>>> The smoke tester runs ‘ant validate’, which does *not* include
> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
> imports are looked for).
> > >>>>>
> > >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”,
> “validate”, and “documentation-lint”.
> > >>>>>
> > >>>>> Jenkins caught this not because of the smoke tester, but rather
> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
> “precommit”, runs “check-working-copy”, “validate”, and
> “documentation-lint” (among others).
> > >>>>>
> > >>>>> I think we should change the smoke tester to look at the same
> things as precommit,
> > >>>>>
> > >>>>> --
> > >>>>> Steve
> > >>>>> www.lucidworks.com
> > >>>>>
> > >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>>>>>
> > >>>>>> Smoke testes passed as well
> > >>>>>>
> > >>>>>>
> > >>>>>> Joel Bernstein
> > >>>>>> http://joelsolr.blogspot.com/
> > >>>>>>
> > >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>>>>> I guess precommit is only run as part of the smoke tester.
> > >>>>>>
> > >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>>>>>>
> > >>>>>>> Interesting the entire release process completed without
> complaining.
> > >>>>>>>
> > >>>>>>> Joel Bernstein
> > >>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>
> > >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>>>>>> The unused import was the only problem; I’ve removed it on
> branch_6_5.
> > >>>>>>>
> > >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
> > >>>>>>>
> > >>>>>>> --
> > >>>>>>> Steve
> > >>>>>>> www.lucidworks.com
> > >>>>>>>
> > >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>>>>>>>
> > >>>>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5
> :(. I forgot to run precommit. Doing so now.
> > >>>>>>>>
> > >>>>>>>> --
> > >>>>>>>> Steve
> > >>>>>>>> www.lucidworks.com
> > >>>>>>>>
> > >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>>>>>>>>
> > >>>>>>>>> Done.
> > >>>>>>>>>
> > >>>>>>>>> --
> > >>>>>>>>> Steve
> > >>>>>>>>> www.lucidworks.com
> > >>>>>>>>>
> > >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>>>>>>>>>
> > >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > >>>>>>>>>>
> > >>>>>>>>>> --
> > >>>>>>>>>> Steve
> > >>>>>>>>>> www.lucidworks.com
> > >>>>>>>>>>
> > >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>>>>>
> > >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the
> back port.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>
> > >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <
> sarowe@gmail.com> wrote:
> > >>>>>>>>>>> Joel,
> > >>>>>>>>>>>
> > >>>>>>>>>>> I know you’re in-process with RC2, but if you have to
> restart for some reason, I’d like to include SOLR-10527.
> > >>>>>>>>>>>
> > >>>>>>>>>>> --
> > >>>>>>>>>>> Steve
> > >>>>>>>>>>> www.lucidworks.com
> > >>>>>>>>>>>
> > >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I also had to change the smoke tester because of the SSL
> issue. Which in theory means everyone else will have to as well. I'm
> pushing out my changes to branch_6_5, so people can just update their
> branch before running the smoke tester.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>>>>>> Ok, I had to push out three changes to the branch but I
> seemed to have moved passed this issue.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully the
> changes will do the trick after they've been pushed.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <
> sarowe@gmail.com> wrote:
> > >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make
> modifications on the release branch, but you can’t test unless you commit
> (and push).
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Another alternative: make modifications in another
> checkout, then invoke the script with from an unmodified source tree.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> e.g.:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> cd ..
> > >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is
> your checkout dir
> > >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/
> scripts/buildAndPushRelease.py
> > >>>>>>>>>>>> cd lucene-solr
> > >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> …
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> (a shorter form of that is to make a copy the script alone
> and invoke the modified version from your checkout)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> --
> > >>>>>>>>>>>> Steve
> > >>>>>>>>>>>> www.lucidworks.com
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
> origin/branch_6_5.." output is:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> So, I'm going to have to push this out.
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Let's first decide if this makes sense as the way forward.
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>>>>>>> Steve, when I change the script to turn off verification I
> get the following error:
> > >>>>>>>>>>>>> RuntimeError: git clone is dirty:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> So as part of the work around I think I'm going to have to
> commit locally and then revert locally. Does that make sense to you as the
> way forward?
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
> arafalov@gmail.com> wrote:
> > >>>>>>>>>>>>> Could it be anything to do with the fact that the signer
> is Semantic
> > >>>>>>>>>>>>> and they are being actively distrusted by - at least -
> Google:
> > >>>>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Regards,
> > >>>>>>>>>>>>> Alex.
> > >>>>>>>>>>>>> ----
> > >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users,
> new and experienced
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if
> cert verification
> > >>>>>>>>>>>>>> was something that was integral to the process.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
> sarowe@gmail.com> wrote:
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Hi Joel,
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication>
> has been enabled on
> > >>>>>>>>>>>>>>> archive.apache.org?
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
> alternative to
> > >>>>>>>>>>>>>>> urllib):
> > >>>>>>>>>>>>>>> <http://docs.python-requests.
> org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Short term, you could turn off certificate
> verification. The bottom
> > >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib
> instead of urllib2,
> > >>>>>>>>>>>>>>> which is assumed in the other answers on the page), to
> turn off certificate
> > >>>>>>>>>>>>>>> verification:
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>> Steve
> > >>>>>>>>>>>>>>> www.lucidworks.com
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert
> for
> > >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
> joelsolr@gmail.com>
> > >>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
> --push-local
> > >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> I believe this is same basic command I used for RC1.
> But this time I got
> > >>>>>>>>>>>>>>>> a new error. At first I thought it might be incorrect
> keystore password but
> > >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the
> issue is?
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> Traceback (most recent call last):
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 313, in <module>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> main()
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 294, in main
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id,
> c.key_password)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 98, in prepare
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> checkDOAPfiles(version)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 143, in
> > >>>>>>>>>>>>>>>> checkDOAPfiles
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> distpage = load(url)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 67, in load
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> content = urllib.request.urlopen(
> urlString).read().decode('utf-8')
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File
> > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>>>>>>>>> line 223, in urlopen
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File
> > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>>>>>>>>> line 526, in open
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> response = self._open(req, data)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File
> > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>>>>>>>>> line 544, in _open
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> '_open', req)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File
> > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>>>>>>>>> line 504, in _call_chain
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> result = func(*args)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File
> > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>>>>>>>>> line 1361, in https_open
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_
> hostname)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> File
> > >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>>>>>>>>> line 1320, in do_open
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> raise URLError(err)
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> > >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> ------------------------------
> ---------------------------------------
> > >>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
> org
> > >>>>>>>>>>>>>>> For additional commands, e-mail:
> dev-help@lucene.apache.org
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> ------------------------------
> ---------------------------------------
> > >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>>>>>>> For additional commands, e-mail:
> dev-help@lucene.apache.org
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> ------------------------------
> ---------------------------------------
> > >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> ------------------------------------------------------------
> ---------
> > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> ------------------------------------------------------------
> ---------
> > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> ------------------------------------------------------------
> ---------
> > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>> ------------------------------------------------------------
> ---------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>> ------------------------------------------------------------
> ---------
> > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>
> > >>>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>
> > >>
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
That’s the error you posted for buildAndPushRelease.py - are you saying that you got identical errors for both?
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 1:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
>
> Python 3.6.1
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <jo...@gmail.com> wrote:
> This was the error:
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 504, in _call_chain
>
> result = func(*args)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 1361, in https_open
>
> context=self._context, check_hostname=self._check_hostname)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 1320, in do_open
>
> raise URLError(err)
>
> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)>
>
>
>
> Perhaps the error was only local to my machine. But I didn't have this error when building RC1
>
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com> wrote:
> Joel,
>
> I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t see any problems so far when I run it with my Python 3.4.2 with the 6.5.1RC2 URL. (Still in progress; Lucene distributions have downloaded so far.)
>
> What was the error that caused you to make the SSL changes to smokeTestRelease.py? And what version of Python are you using?
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
> >
> > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the first that supports the changes you made, so the smoke tester is failing for me:
> >
> > -----
> > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
> > content = urllib.request.urlopen(urlString, context=ctx).read().decode('utf-8')
> > TypeError: urlopen() got an unexpected keyword argument ‘context’
> > ------
> >
> > I’ll install a newer Python.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>
> >> thanks
> >>
> >> Joel Bernstein
> >> http://joelsolr.blogspot.com/
> >>
> >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com> wrote:
> >> I’ll take a look.
> >>
> >> --
> >> Steve
> >> www.lucidworks.com
> >>
> >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>
> >>> I've uploaded the RC2 here https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d88652952ec3e2b3e0070/.
> >>>
> >>> But the smoke test breaks with SSL error in different spot when you smoke test from this URL. It's failing with a different command this time so the fix I used in other sports of smoke tester doesn't work.
> >>>
> >>> Steve, would you mind taking a look at this and pushing out a fix?
> >>>
> >>> Joel Bernstein
> >>> http://joelsolr.blogspot.com/
> >>>
> >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>> I was thinking that if buildAndPushRelease.py can identify problems early, the RM won’t have to later redo work when a problem is found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from auto-running precommit would be worth it.
> >>>
> >>> But I agree that the smoke tester should be heavy, since it’s possible that the RM had weird local conditions that weren’t caught by the release production tools.
> >>>
> >>> --
> >>> Steve
> >>> www.lucidworks.com
> >>>
> >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>
> >>>> They are both quite long processes. Perhaps we should look at eliminating some of the overlap?
> >>>>
> >>>> Since the smokeTesters is run by those voting on the release maybe this should be the heavier of the two.
> >>>>
> >>>> Joel Bernstein
> >>>> http://joelsolr.blogspot.com/
> >>>>
> >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>>> Also, I think buildAndPushRelease.py should invoke “precommit" too, (near) where it runs 'ant clean test'.
> >>>>
> >>>> --
> >>>> Steve
> >>>> www.lucidworks.com
> >>>>
> >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>
> >>>>> That’s bizarre.
> >>>>>
> >>>>> The smoke tester runs ‘ant validate’, which does *not* include "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused imports are looked for).
> >>>>>
> >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and “documentation-lint”.
> >>>>>
> >>>>> Jenkins caught this not because of the smoke tester, but rather because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like “precommit”, runs “check-working-copy”, “validate”, and “documentation-lint” (among others).
> >>>>>
> >>>>> I think we should change the smoke tester to look at the same things as precommit,
> >>>>>
> >>>>> --
> >>>>> Steve
> >>>>> www.lucidworks.com
> >>>>>
> >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>
> >>>>>> Smoke testes passed as well
> >>>>>>
> >>>>>>
> >>>>>> Joel Bernstein
> >>>>>> http://joelsolr.blogspot.com/
> >>>>>>
> >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>> I guess precommit is only run as part of the smoke tester.
> >>>>>>
> >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> Interesting the entire release process completed without complaining.
> >>>>>>>
> >>>>>>> Joel Bernstein
> >>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>
> >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>> The unused import was the only problem; I’ve removed it on branch_6_5.
> >>>>>>>
> >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
> >>>>>>>
> >>>>>>> --
> >>>>>>> Steve
> >>>>>>> www.lucidworks.com
> >>>>>>>
> >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Steve
> >>>>>>>> www.lucidworks.com
> >>>>>>>>
> >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>> Done.
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Steve
> >>>>>>>>> www.lucidworks.com
> >>>>>>>>>
> >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Steve
> >>>>>>>>>> www.lucidworks.com
> >>>>>>>>>>
> >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the back port.
> >>>>>>>>>>>
> >>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>
> >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>>>>>> Joel,
> >>>>>>>>>>>
> >>>>>>>>>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Steve
> >>>>>>>>>>> www.lucidworks.com
> >>>>>>>>>>>
> >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
> >>>>>>>>>>>>
> >>>>>>>>>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
> >>>>>>>>>>>>
> >>>>>>>>>>>> e.g.:
> >>>>>>>>>>>>
> >>>>>>>>>>>> cd ..
> >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> >>>>>>>>>>>> cd lucene-solr
> >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
> >>>>>>>>>>>>
> >>>>>>>>>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
> >>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> Steve
> >>>>>>>>>>>> www.lucidworks.com
> >>>>>>>>>>>>
> >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> So, I'm going to have to push this out.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Let's first decide if this makes sense as the way forward.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>>>>>> Steve, when I change the script to turn off verification I get the following error:
> >>>>>>>>>>>>> RuntimeError: git clone is dirty:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> >>>>>>>>>>>>> Could it be anything to do with the fact that the signer is Semantic
> >>>>>>>>>>>>> and they are being actively distrusted by - at least - Google:
> >>>>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>> Alex.
> >>>>>>>>>>>>> ----
> >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> >>>>>>>>>>>>>> was something that was integral to the process.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Hi Joel,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> >>>>>>>>>>>>>>> archive.apache.org?
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
> >>>>>>>>>>>>>>> urllib):
> >>>>>>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Short term, you could turn off certificate verification. The bottom
> >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
> >>>>>>>>>>>>>>> which is assumed in the other answers on the page), to turn off certificate
> >>>>>>>>>>>>>>> verification:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>> Steve
> >>>>>>>>>>>>>>> www.lucidworks.com
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
> >>>>>>>>>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
> >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Traceback (most recent call last):
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> main()
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> checkDOAPfiles(version)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> >>>>>>>>>>>>>>>> checkDOAPfiles
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> distpage = load(url)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File
> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>>>>>>>>> line 223, in urlopen
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File
> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>>>>>>>>> line 526, in open
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> response = self._open(req, data)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File
> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>>>>>>>>> line 544, in _open
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> '_open', req)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File
> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>>>>>>>>> line 504, in _call_chain
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> result = func(*args)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File
> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>>>>>>>>> line 1361, in https_open
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File
> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>>>>>>>>> line 1320, in do_open
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> raise URLError(err)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> ---------------------------------------------------------------------
> >>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> ---------------------------------------------------------------------
> >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> ---------------------------------------------------------------------
> >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> ---------------------------------------------------------------------
> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: dev-help@lucene.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
Shall we just start the vote then?
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 1:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> Python 3.6.1
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
>
>> This was the error:
>>
>> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> line 504, in _call_chain
>>
>> result = func(*args)
>>
>> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> line 1361, in https_open
>>
>> context=self._context, check_hostname=self._check_hostname)
>>
>> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> line 1320, in do_open
>>
>> raise URLError(err)
>>
>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
>> certificate verify failed (_ssl.c:749)>
>>
>>
>> Perhaps the error was only local to my machine. But I didn't have this
>> error when building RC1
>>
>>
>>
>> Joel Bernstein
>> http://joelsolr.blogspot.com/
>>
>> On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com> wrote:
>>
>>> Joel,
>>>
>>> I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t see
>>> any problems so far when I run it with my Python 3.4.2 with the 6.5.1RC2
>>> URL. (Still in progress; Lucene distributions have downloaded so far.)
>>>
>>> What was the error that caused you to make the SSL changes to
>>> smokeTestRelease.py? And what version of Python are you using?
>>>
>>> --
>>> Steve
>>> www.lucidworks.com
>>>
>>> > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
>>> >
>>> > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the first
>>> that supports the changes you made, so the smoke tester is failing for me:
>>> >
>>> > -----
>>> > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
>>> > content = urllib.request.urlopen(urlString,
>>> context=ctx).read().decode('utf-8')
>>> > TypeError: urlopen() got an unexpected keyword argument ‘context’
>>> > ------
>>> >
>>> > I’ll install a newer Python.
>>> >
>>> > --
>>> > Steve
>>> > www.lucidworks.com
>>> >
>>> >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> >>
>>> >> thanks
>>> >>
>>> >> Joel Bernstein
>>> >> http://joelsolr.blogspot.com/
>>> >>
>>> >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >> I’ll take a look.
>>> >>
>>> >> --
>>> >> Steve
>>> >> www.lucidworks.com
>>> >>
>>> >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> >>>
>>> >>> I've uploaded the RC2 here https://dist.apache.org/repos/
>>> dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62
>>> d88652952ec3e2b3e0070/.
>>> >>>
>>> >>> But the smoke test breaks with SSL error in different spot when you
>>> smoke test from this URL. It's failing with a different command this time
>>> so the fix I used in other sports of smoke tester doesn't work.
>>> >>>
>>> >>> Steve, would you mind taking a look at this and pushing out a fix?
>>> >>>
>>> >>> Joel Bernstein
>>> >>> http://joelsolr.blogspot.com/
>>> >>>
>>> >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>> I was thinking that if buildAndPushRelease.py can identify problems
>>> early, the RM won’t have to later redo work when a problem is found, e.g.
>>> by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from
>>> auto-running precommit would be worth it.
>>> >>>
>>> >>> But I agree that the smoke tester should be heavy, since it’s
>>> possible that the RM had weird local conditions that weren’t caught by the
>>> release production tools.
>>> >>>
>>> >>> --
>>> >>> Steve
>>> >>> www.lucidworks.com
>>> >>>
>>> >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> >>>>
>>> >>>> They are both quite long processes. Perhaps we should look at
>>> eliminating some of the overlap?
>>> >>>>
>>> >>>> Since the smokeTesters is run by those voting on the release maybe
>>> this should be the heavier of the two.
>>> >>>>
>>> >>>> Joel Bernstein
>>> >>>> http://joelsolr.blogspot.com/
>>> >>>>
>>> >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>>> Also, I think buildAndPushRelease.py should invoke “precommit" too,
>>> (near) where it runs 'ant clean test'.
>>> >>>>
>>> >>>> --
>>> >>>> Steve
>>> >>>> www.lucidworks.com
>>> >>>>
>>> >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
>>> >>>>>
>>> >>>>> That’s bizarre.
>>> >>>>>
>>> >>>>> The smoke tester runs ‘ant validate’, which does *not* include
>>> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
>>> imports are looked for).
>>> >>>>>
>>> >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”,
>>> “validate”, and “documentation-lint”.
>>> >>>>>
>>> >>>>> Jenkins caught this not because of the smoke tester, but rather
>>> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
>>> “precommit”, runs “check-working-copy”, “validate”, and
>>> “documentation-lint” (among others).
>>> >>>>>
>>> >>>>> I think we should change the smoke tester to look at the same
>>> things as precommit,
>>> >>>>>
>>> >>>>> --
>>> >>>>> Steve
>>> >>>>> www.lucidworks.com
>>> >>>>>
>>> >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> >>>>>>
>>> >>>>>> Smoke testes passed as well
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> Joel Bernstein
>>> >>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>
>>> >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>>>>> I guess precommit is only run as part of the smoke tester.
>>> >>>>>>
>>> >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> >>>>>>>
>>> >>>>>>> Interesting the entire release process completed without
>>> complaining.
>>> >>>>>>>
>>> >>>>>>> Joel Bernstein
>>> >>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>
>>> >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>>>>>> The unused import was the only problem; I’ve removed it on
>>> branch_6_5.
>>> >>>>>>>
>>> >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
>>> >>>>>>>
>>> >>>>>>> --
>>> >>>>>>> Steve
>>> >>>>>>> www.lucidworks.com
>>> >>>>>>>
>>> >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>>>>>>>
>>> >>>>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5
>>> :(. I forgot to run precommit. Doing so now.
>>> >>>>>>>>
>>> >>>>>>>> --
>>> >>>>>>>> Steve
>>> >>>>>>>> www.lucidworks.com
>>> >>>>>>>>
>>> >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>>>>>>>>
>>> >>>>>>>>> Done.
>>> >>>>>>>>>
>>> >>>>>>>>> --
>>> >>>>>>>>> Steve
>>> >>>>>>>>> www.lucidworks.com
>>> >>>>>>>>>
>>> >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>>>>>>>>>
>>> >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>>> >>>>>>>>>>
>>> >>>>>>>>>> --
>>> >>>>>>>>>> Steve
>>> >>>>>>>>>> www.lucidworks.com
>>> >>>>>>>>>>
>>> >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the
>>> back port.
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <
>>> sarowe@gmail.com> wrote:
>>> >>>>>>>>>>> Joel,
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> I know you’re in-process with RC2, but if you have to
>>> restart for some reason, I’d like to include SOLR-10527.
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> --
>>> >>>>>>>>>>> Steve
>>> >>>>>>>>>>> www.lucidworks.com
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> I also had to change the smoke tester because of the SSL
>>> issue. Which in theory means everyone else will have to as well. I'm
>>> pushing out my changes to branch_6_5, so people can just update their
>>> branch before running the smoke tester.
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>>> Ok, I had to push out three changes to the branch but I
>>> seemed to have moved passed this issue.
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully the
>>> changes will do the trick after they've been pushed.
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <
>>> sarowe@gmail.com> wrote:
>>> >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make
>>> modifications on the release branch, but you can’t test unless you commit
>>> (and push).
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> Another alternative: make modifications in another
>>> checkout, then invoke the script with from an unmodified source tree.
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> e.g.:
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> cd ..
>>> >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is
>>> your checkout dir
>>> >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/script
>>> s/buildAndPushRelease.py
>>> >>>>>>>>>>>> cd lucene-solr
>>> >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>> …
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> (a shorter form of that is to make a copy the script alone
>>> and invoke the modified version from your checkout)
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> --
>>> >>>>>>>>>>>> Steve
>>> >>>>>>>>>>>> www.lucidworks.com
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
>>> origin/branch_6_5.." output is:
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> So, I'm going to have to push this out.
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Let's first decide if this makes sense as the way forward.
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>>>> Steve, when I change the script to turn off verification I
>>> get the following error:
>>> >>>>>>>>>>>>> RuntimeError: git clone is dirty:
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> So as part of the work around I think I'm going to have to
>>> commit locally and then revert locally. Does that make sense to you as the
>>> way forward?
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>>> arafalov@gmail.com> wrote:
>>> >>>>>>>>>>>>> Could it be anything to do with the fact that the signer
>>> is Semantic
>>> >>>>>>>>>>>>> and they are being actively distrusted by - at least -
>>> Google:
>>> >>>>>>>>>>>>> http://www.securityweek.com/go
>>> ogle-stops-trusting-symantec-issued-certificates
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Regards,
>>> >>>>>>>>>>>>> Alex.
>>> >>>>>>>>>>>>> ----
>>> >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users,
>>> new and experienced
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if
>>> cert verification
>>> >>>>>>>>>>>>>> was something that was integral to the process.
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
>>> sarowe@gmail.com> wrote:
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> Hi Joel,
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>>> >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication>
>>> has been enabled on
>>> >>>>>>>>>>>>>>> archive.apache.org?
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
>>> alternative to
>>> >>>>>>>>>>>>>>> urllib):
>>> >>>>>>>>>>>>>>> <http://docs.python-requests.o
>>> rg/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> Short term, you could turn off certificate
>>> verification. The bottom
>>> >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib
>>> instead of urllib2,
>>> >>>>>>>>>>>>>>> which is assumed in the other answers on the page), to
>>> turn off certificate
>>> >>>>>>>>>>>>>>> verification:
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> <http://stackoverflow.com/ques
>>> tions/19268548/python-ignore-certicate-validation-urllib2>
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> --
>>> >>>>>>>>>>>>>>> Steve
>>> >>>>>>>>>>>>>>> www.lucidworks.com
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert
>>> for
>>> >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>>> joelsolr@gmail.com>
>>> >>>>>>>>>>>>>>>> wrote:
>>> >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>>> >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>>> --push-local
>>> >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> I believe this is same basic command I used for RC1.
>>> But this time I got
>>> >>>>>>>>>>>>>>>> a new error. At first I thought it might be incorrect
>>> keystore password but
>>> >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the
>>> issue is?
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> Traceback (most recent call last):
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>> 313, in <module>
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> main()
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>> 294, in main
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id,
>>> c.key_password)
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>> 98, in prepare
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> checkDOAPfiles(version)
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>> 143, in
>>> >>>>>>>>>>>>>>>> checkDOAPfiles
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> distpage = load(url)
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>> 67, in load
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> content = urllib.request.urlopen(urlStri
>>> ng).read().decode('utf-8')
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> File
>>> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> >>>>>>>>>>>>>>>> line 223, in urlopen
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> File
>>> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> >>>>>>>>>>>>>>>> line 526, in open
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> response = self._open(req, data)
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> File
>>> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> >>>>>>>>>>>>>>>> line 544, in _open
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> '_open', req)
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> File
>>> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> >>>>>>>>>>>>>>>> line 504, in _call_chain
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> result = func(*args)
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> File
>>> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> >>>>>>>>>>>>>>>> line 1361, in https_open
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hos
>>> tname)
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> File
>>> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> >>>>>>>>>>>>>>>> line 1320, in do_open
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> raise URLError(err)
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>>> CERTIFICATE_VERIFY_FAILED]
>>> >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>> ------------------------------
>>> ---------------------------------------
>>> >>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
>>> org
>>> >>>>>>>>>>>>>>> For additional commands, e-mail:
>>> dev-help@lucene.apache.org
>>> >>>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> ------------------------------
>>> ---------------------------------------
>>> >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>>>>>>>>>>>> For additional commands, e-mail:
>>> dev-help@lucene.apache.org
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> ------------------------------
>>> ---------------------------------------
>>> >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> ------------------------------------------------------------
>>> ---------
>>> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>> ------------------------------------------------------------
>>> ---------
>>> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> ------------------------------------------------------------
>>> ---------
>>> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>>>>>
>>> >>>>>>
>>> >>>>>
>>> >>>>
>>> >>>>
>>> >>>> ------------------------------------------------------------
>>> ---------
>>> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>>>
>>> >>>>
>>> >>>
>>> >>>
>>> >>> ------------------------------------------------------------
>>> ---------
>>> >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>>
>>> >>>
>>> >>
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>
>>> >>
>>> >
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
Python 3.6.1
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 1:27 PM, Joel Bernstein <jo...@gmail.com> wrote:
> This was the error:
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 504, in _call_chain
>
> result = func(*args)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 1361, in https_open
>
> context=self._context, check_hostname=self._check_hostname)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 1320, in do_open
>
> raise URLError(err)
>
> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> certificate verify failed (_ssl.c:749)>
>
>
> Perhaps the error was only local to my machine. But I didn't have this
> error when building RC1
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com> wrote:
>
>> Joel,
>>
>> I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t see
>> any problems so far when I run it with my Python 3.4.2 with the 6.5.1RC2
>> URL. (Still in progress; Lucene distributions have downloaded so far.)
>>
>> What was the error that caused you to make the SSL changes to
>> smokeTestRelease.py? And what version of Python are you using?
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>> > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
>> >
>> > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the first
>> that supports the changes you made, so the smoke tester is failing for me:
>> >
>> > -----
>> > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
>> > content = urllib.request.urlopen(urlString,
>> context=ctx).read().decode('utf-8')
>> > TypeError: urlopen() got an unexpected keyword argument ‘context’
>> > ------
>> >
>> > I’ll install a newer Python.
>> >
>> > --
>> > Steve
>> > www.lucidworks.com
>> >
>> >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>
>> >> thanks
>> >>
>> >> Joel Bernstein
>> >> http://joelsolr.blogspot.com/
>> >>
>> >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com> wrote:
>> >> I’ll take a look.
>> >>
>> >> --
>> >> Steve
>> >> www.lucidworks.com
>> >>
>> >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>
>> >>> I've uploaded the RC2 here https://dist.apache.org/repos/
>> dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62
>> d88652952ec3e2b3e0070/.
>> >>>
>> >>> But the smoke test breaks with SSL error in different spot when you
>> smoke test from this URL. It's failing with a different command this time
>> so the fix I used in other sports of smoke tester doesn't work.
>> >>>
>> >>> Steve, would you mind taking a look at this and pushing out a fix?
>> >>>
>> >>> Joel Bernstein
>> >>> http://joelsolr.blogspot.com/
>> >>>
>> >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>> I was thinking that if buildAndPushRelease.py can identify problems
>> early, the RM won’t have to later redo work when a problem is found, e.g.
>> by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from
>> auto-running precommit would be worth it.
>> >>>
>> >>> But I agree that the smoke tester should be heavy, since it’s
>> possible that the RM had weird local conditions that weren’t caught by the
>> release production tools.
>> >>>
>> >>> --
>> >>> Steve
>> >>> www.lucidworks.com
>> >>>
>> >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>
>> >>>> They are both quite long processes. Perhaps we should look at
>> eliminating some of the overlap?
>> >>>>
>> >>>> Since the smokeTesters is run by those voting on the release maybe
>> this should be the heavier of the two.
>> >>>>
>> >>>> Joel Bernstein
>> >>>> http://joelsolr.blogspot.com/
>> >>>>
>> >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>> Also, I think buildAndPushRelease.py should invoke “precommit" too,
>> (near) where it runs 'ant clean test'.
>> >>>>
>> >>>> --
>> >>>> Steve
>> >>>> www.lucidworks.com
>> >>>>
>> >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
>> >>>>>
>> >>>>> That’s bizarre.
>> >>>>>
>> >>>>> The smoke tester runs ‘ant validate’, which does *not* include
>> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
>> imports are looked for).
>> >>>>>
>> >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”,
>> and “documentation-lint”.
>> >>>>>
>> >>>>> Jenkins caught this not because of the smoke tester, but rather
>> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
>> “precommit”, runs “check-working-copy”, “validate”, and
>> “documentation-lint” (among others).
>> >>>>>
>> >>>>> I think we should change the smoke tester to look at the same
>> things as precommit,
>> >>>>>
>> >>>>> --
>> >>>>> Steve
>> >>>>> www.lucidworks.com
>> >>>>>
>> >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>>>
>> >>>>>> Smoke testes passed as well
>> >>>>>>
>> >>>>>>
>> >>>>>> Joel Bernstein
>> >>>>>> http://joelsolr.blogspot.com/
>> >>>>>>
>> >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>>>> I guess precommit is only run as part of the smoke tester.
>> >>>>>>
>> >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>>>>
>> >>>>>>> Interesting the entire release process completed without
>> complaining.
>> >>>>>>>
>> >>>>>>> Joel Bernstein
>> >>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>
>> >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>>>>> The unused import was the only problem; I’ve removed it on
>> branch_6_5.
>> >>>>>>>
>> >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
>> >>>>>>>
>> >>>>>>> --
>> >>>>>>> Steve
>> >>>>>>> www.lucidworks.com
>> >>>>>>>
>> >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>>>>>>
>> >>>>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5
>> :(. I forgot to run precommit. Doing so now.
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>> Steve
>> >>>>>>>> www.lucidworks.com
>> >>>>>>>>
>> >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>>>>>>>
>> >>>>>>>>> Done.
>> >>>>>>>>>
>> >>>>>>>>> --
>> >>>>>>>>> Steve
>> >>>>>>>>> www.lucidworks.com
>> >>>>>>>>>
>> >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>> >>>>>>>>>>
>> >>>>>>>>>> --
>> >>>>>>>>>> Steve
>> >>>>>>>>>> www.lucidworks.com
>> >>>>>>>>>>
>> >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>>>
>> >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the
>> back port.
>> >>>>>>>>>>>
>> >>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>>>>>>>>> Joel,
>> >>>>>>>>>>>
>> >>>>>>>>>>> I know you’re in-process with RC2, but if you have to restart
>> for some reason, I’d like to include SOLR-10527.
>> >>>>>>>>>>>
>> >>>>>>>>>>> --
>> >>>>>>>>>>> Steve
>> >>>>>>>>>>> www.lucidworks.com
>> >>>>>>>>>>>
>> >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> I also had to change the smoke tester because of the SSL
>> issue. Which in theory means everyone else will have to as well. I'm
>> pushing out my changes to branch_6_5, so people can just update their
>> branch before running the smoke tester.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>>>> Ok, I had to push out three changes to the branch but I
>> seemed to have moved passed this issue.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully the
>> changes will do the trick after they've been pushed.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <
>> sarowe@gmail.com> wrote:
>> >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make
>> modifications on the release branch, but you can’t test unless you commit
>> (and push).
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Another alternative: make modifications in another checkout,
>> then invoke the script with from an unmodified source tree.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> e.g.:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> cd ..
>> >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is
>> your checkout dir
>> >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/script
>> s/buildAndPushRelease.py
>> >>>>>>>>>>>> cd lucene-solr
>> >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>> …
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> (a shorter form of that is to make a copy the script alone
>> and invoke the modified version from your checkout)
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> --
>> >>>>>>>>>>>> Steve
>> >>>>>>>>>>>> www.lucidworks.com
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
>> origin/branch_6_5.." output is:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> So, I'm going to have to push this out.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Let's first decide if this makes sense as the way forward.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>>>>> Steve, when I change the script to turn off verification I
>> get the following error:
>> >>>>>>>>>>>>> RuntimeError: git clone is dirty:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> So as part of the work around I think I'm going to have to
>> commit locally and then revert locally. Does that make sense to you as the
>> way forward?
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>> arafalov@gmail.com> wrote:
>> >>>>>>>>>>>>> Could it be anything to do with the fact that the signer is
>> Semantic
>> >>>>>>>>>>>>> and they are being actively distrusted by - at least -
>> Google:
>> >>>>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-
>> issued-certificates
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Regards,
>> >>>>>>>>>>>>> Alex.
>> >>>>>>>>>>>>> ----
>> >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new
>> and experienced
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if
>> cert verification
>> >>>>>>>>>>>>>> was something that was integral to the process.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
>> sarowe@gmail.com> wrote:
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Hi Joel,
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>> >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication>
>> has been enabled on
>> >>>>>>>>>>>>>>> archive.apache.org?
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
>> alternative to
>> >>>>>>>>>>>>>>> urllib):
>> >>>>>>>>>>>>>>> <http://docs.python-requests.o
>> rg/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Short term, you could turn off certificate verification.
>> The bottom
>> >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib
>> instead of urllib2,
>> >>>>>>>>>>>>>>> which is assumed in the other answers on the page), to
>> turn off certificate
>> >>>>>>>>>>>>>>> verification:
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> <http://stackoverflow.com/ques
>> tions/19268548/python-ignore-certicate-validation-urllib2>
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> --
>> >>>>>>>>>>>>>>> Steve
>> >>>>>>>>>>>>>>> www.lucidworks.com
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert
>> for
>> >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>> joelsolr@gmail.com>
>> >>>>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>> >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>> --push-local
>> >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But
>> this time I got
>> >>>>>>>>>>>>>>>> a new error. At first I thought it might be incorrect
>> keystore password but
>> >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the
>> issue is?
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Traceback (most recent call last):
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>> 313, in <module>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> main()
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>> 294, in main
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id,
>> c.key_password)
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>> 98, in prepare
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> checkDOAPfiles(version)
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>> 143, in
>> >>>>>>>>>>>>>>>> checkDOAPfiles
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> distpage = load(url)
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>> 67, in load
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> content = urllib.request.urlopen(urlStri
>> ng).read().decode('utf-8')
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> File
>> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> >>>>>>>>>>>>>>>> line 223, in urlopen
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> File
>> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> >>>>>>>>>>>>>>>> line 526, in open
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> response = self._open(req, data)
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> File
>> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> >>>>>>>>>>>>>>>> line 544, in _open
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> '_open', req)
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> File
>> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> >>>>>>>>>>>>>>>> line 504, in _call_chain
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> result = func(*args)
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> File
>> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> >>>>>>>>>>>>>>>> line 1361, in https_open
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hos
>> tname)
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> File
>> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> >>>>>>>>>>>>>>>> line 1320, in do_open
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> raise URLError(err)
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>> CERTIFICATE_VERIFY_FAILED]
>> >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> ------------------------------
>> ---------------------------------------
>> >>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>>>>>>>>>>>> For additional commands, e-mail:
>> dev-help@lucene.apache.org
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> ------------------------------
>> ---------------------------------------
>> >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> ------------------------------------------------------------
>> ---------
>> >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> ------------------------------------------------------------
>> ---------
>> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> ------------------------------------------------------------
>> ---------
>> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> ------------------------------------------------------------
>> ---------
>> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>> ------------------------------------------------------------
>> ---------
>> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>
>> >>>
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>
>> >>
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
This was the error:
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
line 504, in _call_chain
result = func(*args)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
line 1361, in https_open
context=self._context, check_hostname=self._check_hostname)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
line 1320, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
certificate verify failed (_ssl.c:749)>
Perhaps the error was only local to my machine. But I didn't have this
error when building RC1
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 1:25 PM, Steve Rowe <sa...@gmail.com> wrote:
> Joel,
>
> I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t see any
> problems so far when I run it with my Python 3.4.2 with the 6.5.1RC2 URL.
> (Still in progress; Lucene distributions have downloaded so far.)
>
> What was the error that caused you to make the SSL changes to
> smokeTestRelease.py? And what version of Python are you using?
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
> >
> > I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the first
> that supports the changes you made, so the smoke tester is failing for me:
> >
> > -----
> > File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
> > content = urllib.request.urlopen(urlString,
> context=ctx).read().decode('utf-8')
> > TypeError: urlopen() got an unexpected keyword argument ‘context’
> > ------
> >
> > I’ll install a newer Python.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> >> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>
> >> thanks
> >>
> >> Joel Bernstein
> >> http://joelsolr.blogspot.com/
> >>
> >> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com> wrote:
> >> I’ll take a look.
> >>
> >> --
> >> Steve
> >> www.lucidworks.com
> >>
> >>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>
> >>> I've uploaded the RC2 here https://dist.apache.org/repos/
> dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d8865295
> 2ec3e2b3e0070/.
> >>>
> >>> But the smoke test breaks with SSL error in different spot when you
> smoke test from this URL. It's failing with a different command this time
> so the fix I used in other sports of smoke tester doesn't work.
> >>>
> >>> Steve, would you mind taking a look at this and pushing out a fix?
> >>>
> >>> Joel Bernstein
> >>> http://joelsolr.blogspot.com/
> >>>
> >>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>> I was thinking that if buildAndPushRelease.py can identify problems
> early, the RM won’t have to later redo work when a problem is found, e.g.
> by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from
> auto-running precommit would be worth it.
> >>>
> >>> But I agree that the smoke tester should be heavy, since it’s possible
> that the RM had weird local conditions that weren’t caught by the release
> production tools.
> >>>
> >>> --
> >>> Steve
> >>> www.lucidworks.com
> >>>
> >>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>
> >>>> They are both quite long processes. Perhaps we should look at
> eliminating some of the overlap?
> >>>>
> >>>> Since the smokeTesters is run by those voting on the release maybe
> this should be the heavier of the two.
> >>>>
> >>>> Joel Bernstein
> >>>> http://joelsolr.blogspot.com/
> >>>>
> >>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>> Also, I think buildAndPushRelease.py should invoke “precommit" too,
> (near) where it runs 'ant clean test'.
> >>>>
> >>>> --
> >>>> Steve
> >>>> www.lucidworks.com
> >>>>
> >>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>
> >>>>> That’s bizarre.
> >>>>>
> >>>>> The smoke tester runs ‘ant validate’, which does *not* include
> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
> imports are looked for).
> >>>>>
> >>>>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”,
> and “documentation-lint”.
> >>>>>
> >>>>> Jenkins caught this not because of the smoke tester, but rather
> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
> “precommit”, runs “check-working-copy”, “validate”, and
> “documentation-lint” (among others).
> >>>>>
> >>>>> I think we should change the smoke tester to look at the same things
> as precommit,
> >>>>>
> >>>>> --
> >>>>> Steve
> >>>>> www.lucidworks.com
> >>>>>
> >>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>>
> >>>>>> Smoke testes passed as well
> >>>>>>
> >>>>>>
> >>>>>> Joel Bernstein
> >>>>>> http://joelsolr.blogspot.com/
> >>>>>>
> >>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>> I guess precommit is only run as part of the smoke tester.
> >>>>>>
> >>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>>>
> >>>>>>> Interesting the entire release process completed without
> complaining.
> >>>>>>>
> >>>>>>> Joel Bernstein
> >>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>
> >>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>>> The unused import was the only problem; I’ve removed it on
> branch_6_5.
> >>>>>>>
> >>>>>>> Sorry, hope I didn’t cause a delay in the release process.
> >>>>>>>
> >>>>>>> --
> >>>>>>> Steve
> >>>>>>> www.lucidworks.com
> >>>>>>>
> >>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5
> :(. I forgot to run precommit. Doing so now.
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Steve
> >>>>>>>> www.lucidworks.com
> >>>>>>>>
> >>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>>>>>
> >>>>>>>>> Done.
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Steve
> >>>>>>>>> www.lucidworks.com
> >>>>>>>>>
> >>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Steve
> >>>>>>>>>> www.lucidworks.com
> >>>>>>>>>>
> >>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the
> back port.
> >>>>>>>>>>>
> >>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>
> >>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>>>>>>> Joel,
> >>>>>>>>>>>
> >>>>>>>>>>> I know you’re in-process with RC2, but if you have to restart
> for some reason, I’d like to include SOLR-10527.
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Steve
> >>>>>>>>>>> www.lucidworks.com
> >>>>>>>>>>>
> >>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> I also had to change the smoke tester because of the SSL
> issue. Which in theory means everyone else will have to as well. I'm
> pushing out my changes to branch_6_5, so people can just update their
> branch before running the smoke tester.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>>>> Ok, I had to push out three changes to the branch but I
> seemed to have moved passed this issue.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>>>> I'll push out the changes and then revert. Hopefully the
> changes will do the trick after they've been pushed.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make
> modifications on the release branch, but you can’t test unless you commit
> (and push).
> >>>>>>>>>>>>
> >>>>>>>>>>>> Another alternative: make modifications in another checkout,
> then invoke the script with from an unmodified source tree.
> >>>>>>>>>>>>
> >>>>>>>>>>>> e.g.:
> >>>>>>>>>>>>
> >>>>>>>>>>>> cd ..
> >>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is
> your checkout dir
> >>>>>>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> >>>>>>>>>>>> cd lucene-solr
> >>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> …
> >>>>>>>>>>>>
> >>>>>>>>>>>> (a shorter form of that is to make a copy the script alone
> and invoke the modified version from your checkout)
> >>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> Steve
> >>>>>>>>>>>> www.lucidworks.com
> >>>>>>>>>>>>
> >>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
> origin/branch_6_5.." output is:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> So, I'm going to have to push this out.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Let's first decide if this makes sense as the way forward.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>>>>> Steve, when I change the script to turn off verification I
> get the following error:
> >>>>>>>>>>>>> RuntimeError: git clone is dirty:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> So as part of the work around I think I'm going to have to
> commit locally and then revert locally. Does that make sense to you as the
> way forward?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
> arafalov@gmail.com> wrote:
> >>>>>>>>>>>>> Could it be anything to do with the fact that the signer is
> Semantic
> >>>>>>>>>>>>> and they are being actively distrusted by - at least -
> Google:
> >>>>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>> Alex.
> >>>>>>>>>>>>> ----
> >>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new
> and experienced
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if
> cert verification
> >>>>>>>>>>>>>> was something that was integral to the process.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
> sarowe@gmail.com> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Hi Joel,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> >>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication>
> has been enabled on
> >>>>>>>>>>>>>>> archive.apache.org?
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
> alternative to
> >>>>>>>>>>>>>>> urllib):
> >>>>>>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#
> what-are-hostname-doesn-t-match-errors>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Short term, you could turn off certificate verification.
> The bottom
> >>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib
> instead of urllib2,
> >>>>>>>>>>>>>>> which is assumed in the other answers on the page), to
> turn off certificate
> >>>>>>>>>>>>>>> verification:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>> Steve
> >>>>>>>>>>>>>>> www.lucidworks.com
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> >>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
> joelsolr@gmail.com>
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> >>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
> --push-local
> >>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But
> this time I got
> >>>>>>>>>>>>>>>> a new error. At first I thought it might be incorrect
> keystore password but
> >>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the
> issue is?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Traceback (most recent call last):
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 313, in <module>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> main()
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 294, in main
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 98, in prepare
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> checkDOAPfiles(version)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 143, in
> >>>>>>>>>>>>>>>> checkDOAPfiles
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> distpage = load(url)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 67, in load
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> content = urllib.request.urlopen(
> urlString).read().decode('utf-8')
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File
> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>>>>>> line 223, in urlopen
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File
> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>>>>>> line 526, in open
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> response = self._open(req, data)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File
> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>>>>>> line 544, in _open
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> '_open', req)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File
> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>>>>>> line 504, in _call_chain
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> result = func(*args)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File
> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>>>>>> line 1361, in https_open
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_
> hostname)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> File
> >>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>>>>>> line 1320, in do_open
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> raise URLError(err)
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> >>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> ------------------------------
> ---------------------------------------
> >>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>>>>>>> For additional commands, e-mail:
> dev-help@lucene.apache.org
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> ------------------------------------------------------------
> ---------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: dev-help@lucene.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
Joel,
I’ve reverted your SSL changes to smokeTestRelease.py, and I don’t see any problems so far when I run it with my Python 3.4.2 with the 6.5.1RC2 URL. (Still in progress; Lucene distributions have downloaded so far.)
What was the error that caused you to make the SSL changes to smokeTestRelease.py? And what version of Python are you using?
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 1:01 PM, Steve Rowe <sa...@gmail.com> wrote:
>
> I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the first that supports the changes you made, so the smoke tester is failing for me:
>
> -----
> File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
> content = urllib.request.urlopen(urlString, context=ctx).read().decode('utf-8')
> TypeError: urlopen() got an unexpected keyword argument ‘context’
> ------
>
> I’ll install a newer Python.
>
> --
> Steve
> www.lucidworks.com
>
>> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>
>> thanks
>>
>> Joel Bernstein
>> http://joelsolr.blogspot.com/
>>
>> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com> wrote:
>> I’ll take a look.
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>>> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>
>>> I've uploaded the RC2 here https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d88652952ec3e2b3e0070/.
>>>
>>> But the smoke test breaks with SSL error in different spot when you smoke test from this URL. It's failing with a different command this time so the fix I used in other sports of smoke tester doesn't work.
>>>
>>> Steve, would you mind taking a look at this and pushing out a fix?
>>>
>>> Joel Bernstein
>>> http://joelsolr.blogspot.com/
>>>
>>> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
>>> I was thinking that if buildAndPushRelease.py can identify problems early, the RM won’t have to later redo work when a problem is found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from auto-running precommit would be worth it.
>>>
>>> But I agree that the smoke tester should be heavy, since it’s possible that the RM had weird local conditions that weren’t caught by the release production tools.
>>>
>>> --
>>> Steve
>>> www.lucidworks.com
>>>
>>>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>
>>>> They are both quite long processes. Perhaps we should look at eliminating some of the overlap?
>>>>
>>>> Since the smokeTesters is run by those voting on the release maybe this should be the heavier of the two.
>>>>
>>>> Joel Bernstein
>>>> http://joelsolr.blogspot.com/
>>>>
>>>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>> Also, I think buildAndPushRelease.py should invoke “precommit" too, (near) where it runs 'ant clean test'.
>>>>
>>>> --
>>>> Steve
>>>> www.lucidworks.com
>>>>
>>>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>
>>>>> That’s bizarre.
>>>>>
>>>>> The smoke tester runs ‘ant validate’, which does *not* include "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused imports are looked for).
>>>>>
>>>>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and “documentation-lint”.
>>>>>
>>>>> Jenkins caught this not because of the smoke tester, but rather because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like “precommit”, runs “check-working-copy”, “validate”, and “documentation-lint” (among others).
>>>>>
>>>>> I think we should change the smoke tester to look at the same things as precommit,
>>>>>
>>>>> --
>>>>> Steve
>>>>> www.lucidworks.com
>>>>>
>>>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>
>>>>>> Smoke testes passed as well
>>>>>>
>>>>>>
>>>>>> Joel Bernstein
>>>>>> http://joelsolr.blogspot.com/
>>>>>>
>>>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>> I guess precommit is only run as part of the smoke tester.
>>>>>>
>>>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>
>>>>>>> Interesting the entire release process completed without complaining.
>>>>>>>
>>>>>>> Joel Bernstein
>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>
>>>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>> The unused import was the only problem; I’ve removed it on branch_6_5.
>>>>>>>
>>>>>>> Sorry, hope I didn’t cause a delay in the release process.
>>>>>>>
>>>>>>> --
>>>>>>> Steve
>>>>>>> www.lucidworks.com
>>>>>>>
>>>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Steve
>>>>>>>> www.lucidworks.com
>>>>>>>>
>>>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Done.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Steve
>>>>>>>>> www.lucidworks.com
>>>>>>>>>
>>>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Steve
>>>>>>>>>> www.lucidworks.com
>>>>>>>>>>
>>>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the back port.
>>>>>>>>>>>
>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>>>>> Joel,
>>>>>>>>>>>
>>>>>>>>>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Steve
>>>>>>>>>>> www.lucidworks.com
>>>>>>>>>>>
>>>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
>>>>>>>>>>>>
>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
>>>>>>>>>>>>
>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
>>>>>>>>>>>>
>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>>>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
>>>>>>>>>>>>
>>>>>>>>>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
>>>>>>>>>>>>
>>>>>>>>>>>> e.g.:
>>>>>>>>>>>>
>>>>>>>>>>>> cd ..
>>>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
>>>>>>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>>>>>>>>>>> cd lucene-solr
>>>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
>>>>>>>>>>>>
>>>>>>>>>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Steve
>>>>>>>>>>>> www.lucidworks.com
>>>>>>>>>>>>
>>>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>>>>>>>>>>>>>
>>>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
>>>>>>>>>>>>>
>>>>>>>>>>>>> So, I'm going to have to push this out.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Let's first decide if this makes sense as the way forward.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>>>> Steve, when I change the script to turn off verification I get the following error:
>>>>>>>>>>>>> RuntimeError: git clone is dirty:
>>>>>>>>>>>>>
>>>>>>>>>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
>>>>>>>>>>>>> Could it be anything to do with the fact that the signer is Semantic
>>>>>>>>>>>>> and they are being actively distrusted by - at least - Google:
>>>>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Alex.
>>>>>>>>>>>>> ----
>>>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
>>>>>>>>>>>>>> was something that was integral to the process.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Joel,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>>>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
>>>>>>>>>>>>>>> archive.apache.org?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
>>>>>>>>>>>>>>> urllib):
>>>>>>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Short term, you could turn off certificate verification. The bottom
>>>>>>>>>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
>>>>>>>>>>>>>>> which is assumed in the other answers on the page), to turn off certificate
>>>>>>>>>>>>>>> verification:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Steve
>>>>>>>>>>>>>>> www.lucidworks.com
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
>>>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>>>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
>>>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
>>>>>>>>>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
>>>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Traceback (most recent call last):
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> main()
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> checkDOAPfiles(version)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
>>>>>>>>>>>>>>>> checkDOAPfiles
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> distpage = load(url)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> File
>>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>>>>>> line 223, in urlopen
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> return opener.open(url, data, timeout)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> File
>>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>>>>>> line 526, in open
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> response = self._open(req, data)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> File
>>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>>>>>> line 544, in _open
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> '_open', req)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> File
>>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>>>>>> line 504, in _call_chain
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> result = func(*args)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> File
>>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>>>>>> line 1361, in https_open
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> File
>>>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>>>>>> line 1320, in do_open
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> raise URLError(err)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
>>>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
I have Python 3.4.2 on my Linux box, and apparently 3.4.3 is the first that supports the changes you made, so the smoke tester is failing for me:
-----
File "dev-tools/scripts/smokeTestRelease.py", line 165, in load
content = urllib.request.urlopen(urlString, context=ctx).read().decode('utf-8')
TypeError: urlopen() got an unexpected keyword argument ‘context’
------
I’ll install a newer Python.
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 12:51 PM, Joel Bernstein <jo...@gmail.com> wrote:
>
> thanks
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com> wrote:
> I’ll take a look.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > I've uploaded the RC2 here https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d88652952ec3e2b3e0070/.
> >
> > But the smoke test breaks with SSL error in different spot when you smoke test from this URL. It's failing with a different command this time so the fix I used in other sports of smoke tester doesn't work.
> >
> > Steve, would you mind taking a look at this and pushing out a fix?
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
> > I was thinking that if buildAndPushRelease.py can identify problems early, the RM won’t have to later redo work when a problem is found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from auto-running precommit would be worth it.
> >
> > But I agree that the smoke tester should be heavy, since it’s possible that the RM had weird local conditions that weren’t caught by the release production tools.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > >
> > > They are both quite long processes. Perhaps we should look at eliminating some of the overlap?
> > >
> > > Since the smokeTesters is run by those voting on the release maybe this should be the heavier of the two.
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > Also, I think buildAndPushRelease.py should invoke “precommit" too, (near) where it runs 'ant clean test'.
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > > > On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >
> > > > That’s bizarre.
> > > >
> > > > The smoke tester runs ‘ant validate’, which does *not* include "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused imports are looked for).
> > > >
> > > > By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and “documentation-lint”.
> > > >
> > > > Jenkins caught this not because of the smoke tester, but rather because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like “precommit”, runs “check-working-copy”, “validate”, and “documentation-lint” (among others).
> > > >
> > > > I think we should change the smoke tester to look at the same things as precommit,
> > > >
> > > > --
> > > > Steve
> > > > www.lucidworks.com
> > > >
> > > >> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>
> > > >> Smoke testes passed as well
> > > >>
> > > >>
> > > >> Joel Bernstein
> > > >> http://joelsolr.blogspot.com/
> > > >>
> > > >> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >> I guess precommit is only run as part of the smoke tester.
> > > >>
> > > >>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>
> > > >>> Interesting the entire release process completed without complaining.
> > > >>>
> > > >>> Joel Bernstein
> > > >>> http://joelsolr.blogspot.com/
> > > >>>
> > > >>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>> The unused import was the only problem; I’ve removed it on branch_6_5.
> > > >>>
> > > >>> Sorry, hope I didn’t cause a delay in the release process.
> > > >>>
> > > >>> --
> > > >>> Steve
> > > >>> www.lucidworks.com
> > > >>>
> > > >>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>
> > > >>>> Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
> > > >>>>
> > > >>>> --
> > > >>>> Steve
> > > >>>> www.lucidworks.com
> > > >>>>
> > > >>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>
> > > >>>>> Done.
> > > >>>>>
> > > >>>>> --
> > > >>>>> Steve
> > > >>>>> www.lucidworks.com
> > > >>>>>
> > > >>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>>
> > > >>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > > >>>>>>
> > > >>>>>> --
> > > >>>>>> Steve
> > > >>>>>> www.lucidworks.com
> > > >>>>>>
> > > >>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>
> > > >>>>>>> I'm OK with restarting RC2. Let me know when you finish the back port.
> > > >>>>>>>
> > > >>>>>>> Joel Bernstein
> > > >>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>
> > > >>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>>> Joel,
> > > >>>>>>>
> > > >>>>>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
> > > >>>>>>>
> > > >>>>>>> --
> > > >>>>>>> Steve
> > > >>>>>>> www.lucidworks.com
> > > >>>>>>>
> > > >>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>
> > > >>>>>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
> > > >>>>>>>>
> > > >>>>>>>> Joel Bernstein
> > > >>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>
> > > >>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
> > > >>>>>>>>
> > > >>>>>>>> Joel Bernstein
> > > >>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>
> > > >>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
> > > >>>>>>>>
> > > >>>>>>>> Joel Bernstein
> > > >>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>
> > > >>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
> > > >>>>>>>>
> > > >>>>>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
> > > >>>>>>>>
> > > >>>>>>>> e.g.:
> > > >>>>>>>>
> > > >>>>>>>> cd ..
> > > >>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> > > >>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > > >>>>>>>> cd lucene-solr
> > > >>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
> > > >>>>>>>>
> > > >>>>>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
> > > >>>>>>>>
> > > >>>>>>>> --
> > > >>>>>>>> Steve
> > > >>>>>>>> www.lucidworks.com
> > > >>>>>>>>
> > > >>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>>
> > > >>>>>>>>> Ha, that doesn't work either. Now I get this error:
> > > >>>>>>>>>
> > > >>>>>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
> > > >>>>>>>>>
> > > >>>>>>>>> So, I'm going to have to push this out.
> > > >>>>>>>>>
> > > >>>>>>>>> Let's first decide if this makes sense as the way forward.
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> Joel Bernstein
> > > >>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>
> > > >>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>> Steve, when I change the script to turn off verification I get the following error:
> > > >>>>>>>>> RuntimeError: git clone is dirty:
> > > >>>>>>>>>
> > > >>>>>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> Joel Bernstein
> > > >>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>
> > > >>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> > > >>>>>>>>> Could it be anything to do with the fact that the signer is Semantic
> > > >>>>>>>>> and they are being actively distrusted by - at least - Google:
> > > >>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
> > > >>>>>>>>>
> > > >>>>>>>>> Regards,
> > > >>>>>>>>> Alex.
> > > >>>>>>>>> ----
> > > >>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> > > >>>>>>>>>> was something that was integral to the process.
> > > >>>>>>>>>>
> > > >>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>
> > > >>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Hi Joel,
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > > >>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> > > >>>>>>>>>>> archive.apache.org?
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
> > > >>>>>>>>>>> urllib):
> > > >>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Short term, you could turn off certificate verification. The bottom
> > > >>>>>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
> > > >>>>>>>>>>> which is assumed in the other answers on the page), to turn off certificate
> > > >>>>>>>>>>> verification:
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> --
> > > >>>>>>>>>>> Steve
> > > >>>>>>>>>>> www.lucidworks.com
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> > > >>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> > > >>>>>>>>>>>> wrote:
> > > >>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > > >>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> > > >>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
> > > >>>>>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
> > > >>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Traceback (most recent call last):
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> main()
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> checkDOAPfiles(version)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> > > >>>>>>>>>>>> checkDOAPfiles
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> distpage = load(url)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File
> > > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>> line 223, in urlopen
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> return opener.open(url, data, timeout)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File
> > > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>> line 526, in open
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> response = self._open(req, data)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File
> > > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>> line 544, in _open
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> '_open', req)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File
> > > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>> line 504, in _call_chain
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> result = func(*args)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File
> > > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>> line 1361, in https_open
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File
> > > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >>>>>>>>>>>> line 1320, in do_open
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> raise URLError(err)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> > > >>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> ---------------------------------------------------------------------
> > > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> ---------------------------------------------------------------------
> > > >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>> ---------------------------------------------------------------------
> > > >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> ---------------------------------------------------------------------
> > > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>> ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>
> > > >>
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: dev-help@lucene.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
thanks
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 12:50 PM, Steve Rowe <sa...@gmail.com> wrote:
> I’ll take a look.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > I've uploaded the RC2 here https://dist.apache.org/repos/
> dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d8865295
> 2ec3e2b3e0070/.
> >
> > But the smoke test breaks with SSL error in different spot when you
> smoke test from this URL. It's failing with a different command this time
> so the fix I used in other sports of smoke tester doesn't work.
> >
> > Steve, would you mind taking a look at this and pushing out a fix?
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
> > I was thinking that if buildAndPushRelease.py can identify problems
> early, the RM won’t have to later redo work when a problem is found, e.g.
> by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from
> auto-running precommit would be worth it.
> >
> > But I agree that the smoke tester should be heavy, since it’s possible
> that the RM had weird local conditions that weren’t caught by the release
> production tools.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >
> > > They are both quite long processes. Perhaps we should look at
> eliminating some of the overlap?
> > >
> > > Since the smokeTesters is run by those voting on the release maybe
> this should be the heavier of the two.
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > Also, I think buildAndPushRelease.py should invoke “precommit" too,
> (near) where it runs 'ant clean test'.
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > > > On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >
> > > > That’s bizarre.
> > > >
> > > > The smoke tester runs ‘ant validate’, which does *not* include
> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
> imports are looked for).
> > > >
> > > > By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”,
> and “documentation-lint”.
> > > >
> > > > Jenkins caught this not because of the smoke tester, but rather
> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
> “precommit”, runs “check-working-copy”, “validate”, and
> “documentation-lint” (among others).
> > > >
> > > > I think we should change the smoke tester to look at the same things
> as precommit,
> > > >
> > > > --
> > > > Steve
> > > > www.lucidworks.com
> > > >
> > > >> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > >>
> > > >> Smoke testes passed as well
> > > >>
> > > >>
> > > >> Joel Bernstein
> > > >> http://joelsolr.blogspot.com/
> > > >>
> > > >> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >> I guess precommit is only run as part of the smoke tester.
> > > >>
> > > >>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > >>>
> > > >>> Interesting the entire release process completed without
> complaining.
> > > >>>
> > > >>> Joel Bernstein
> > > >>> http://joelsolr.blogspot.com/
> > > >>>
> > > >>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>> The unused import was the only problem; I’ve removed it on
> branch_6_5.
> > > >>>
> > > >>> Sorry, hope I didn’t cause a delay in the release process.
> > > >>>
> > > >>> --
> > > >>> Steve
> > > >>> www.lucidworks.com
> > > >>>
> > > >>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>>
> > > >>>> Crap, Jenkins found an unused import in my commit on branch_6_5
> :(. I forgot to run precommit. Doing so now.
> > > >>>>
> > > >>>> --
> > > >>>> Steve
> > > >>>> www.lucidworks.com
> > > >>>>
> > > >>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>>>
> > > >>>>> Done.
> > > >>>>>
> > > >>>>> --
> > > >>>>> Steve
> > > >>>>> www.lucidworks.com
> > > >>>>>
> > > >>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>>>>
> > > >>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > > >>>>>>
> > > >>>>>> --
> > > >>>>>> Steve
> > > >>>>>> www.lucidworks.com
> > > >>>>>>
> > > >>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>
> > > >>>>>>> I'm OK with restarting RC2. Let me know when you finish the
> back port.
> > > >>>>>>>
> > > >>>>>>> Joel Bernstein
> > > >>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>
> > > >>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>>>>> Joel,
> > > >>>>>>>
> > > >>>>>>> I know you’re in-process with RC2, but if you have to restart
> for some reason, I’d like to include SOLR-10527.
> > > >>>>>>>
> > > >>>>>>> --
> > > >>>>>>> Steve
> > > >>>>>>> www.lucidworks.com
> > > >>>>>>>
> > > >>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>
> > > >>>>>>>> I also had to change the smoke tester because of the SSL
> issue. Which in theory means everyone else will have to as well. I'm
> pushing out my changes to branch_6_5, so people can just update their
> branch before running the smoke tester.
> > > >>>>>>>>
> > > >>>>>>>> Joel Bernstein
> > > >>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>
> > > >>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>> Ok, I had to push out three changes to the branch but I
> seemed to have moved passed this issue.
> > > >>>>>>>>
> > > >>>>>>>> Joel Bernstein
> > > >>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>
> > > >>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>> I'll push out the changes and then revert. Hopefully the
> changes will do the trick after they've been pushed.
> > > >>>>>>>>
> > > >>>>>>>> Joel Bernstein
> > > >>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>
> > > >>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>>>>>> Yeah, that is a sucky part of this: you want to make
> modifications on the release branch, but you can’t test unless you commit
> (and push).
> > > >>>>>>>>
> > > >>>>>>>> Another alternative: make modifications in another checkout,
> then invoke the script with from an unmodified source tree.
> > > >>>>>>>>
> > > >>>>>>>> e.g.:
> > > >>>>>>>>
> > > >>>>>>>> cd ..
> > > >>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is
> your checkout dir
> > > >>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > > >>>>>>>> cd lucene-solr
> > > >>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> …
> > > >>>>>>>>
> > > >>>>>>>> (a shorter form of that is to make a copy the script alone
> and invoke the modified version from your checkout)
> > > >>>>>>>>
> > > >>>>>>>> --
> > > >>>>>>>> Steve
> > > >>>>>>>> www.lucidworks.com
> > > >>>>>>>>
> > > >>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>>
> > > >>>>>>>>> Ha, that doesn't work either. Now I get this error:
> > > >>>>>>>>>
> > > >>>>>>>>> RuntimeError: There are unpushed commits - "git log
> origin/branch_6_5.." output is:
> > > >>>>>>>>>
> > > >>>>>>>>> So, I'm going to have to push this out.
> > > >>>>>>>>>
> > > >>>>>>>>> Let's first decide if this makes sense as the way forward.
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> Joel Bernstein
> > > >>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>
> > > >>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>> Steve, when I change the script to turn off verification I
> get the following error:
> > > >>>>>>>>> RuntimeError: git clone is dirty:
> > > >>>>>>>>>
> > > >>>>>>>>> So as part of the work around I think I'm going to have to
> commit locally and then revert locally. Does that make sense to you as the
> way forward?
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> Joel Bernstein
> > > >>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>
> > > >>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
> arafalov@gmail.com> wrote:
> > > >>>>>>>>> Could it be anything to do with the fact that the signer is
> Semantic
> > > >>>>>>>>> and they are being actively distrusted by - at least -
> Google:
> > > >>>>>>>>> http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> > > >>>>>>>>>
> > > >>>>>>>>> Regards,
> > > >>>>>>>>> Alex.
> > > >>>>>>>>> ----
> > > >>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new
> and experienced
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if
> cert verification
> > > >>>>>>>>>> was something that was integral to the process.
> > > >>>>>>>>>>
> > > >>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>
> > > >>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
> sarowe@gmail.com> wrote:
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Hi Joel,
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > > >>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication>
> has been enabled on
> > > >>>>>>>>>>> archive.apache.org?
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
> alternative to
> > > >>>>>>>>>>> urllib):
> > > >>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#
> what-are-hostname-doesn-t-match-errors>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Short term, you could turn off certificate verification.
> The bottom
> > > >>>>>>>>>>> answer here uses the same lib as the script (urllib
> instead of urllib2,
> > > >>>>>>>>>>> which is assumed in the other answers on the page), to
> turn off certificate
> > > >>>>>>>>>>> verification:
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> --
> > > >>>>>>>>>>> Steve
> > > >>>>>>>>>>> www.lucidworks.com
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> > > >>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
> joelsolr@gmail.com>
> > > >>>>>>>>>>>> wrote:
> > > >>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > > >>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
> --push-local
> > > >>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> I believe this is same basic command I used for RC1. But
> this time I got
> > > >>>>>>>>>>>> a new error. At first I thought it might be incorrect
> keystore password but
> > > >>>>>>>>>>>> I changed it and it is correct. Any thoughts what the
> issue is?
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Traceback (most recent call last):
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 313, in <module>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> main()
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 294, in main
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 98, in prepare
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> checkDOAPfiles(version)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 143, in
> > > >>>>>>>>>>>> checkDOAPfiles
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> distpage = load(url)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
> 67, in load
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> content = urllib.request.urlopen(
> urlString).read().decode('utf-8')
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File
> > > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >>>>>>>>>>>> line 223, in urlopen
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> return opener.open(url, data, timeout)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File
> > > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >>>>>>>>>>>> line 526, in open
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> response = self._open(req, data)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File
> > > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >>>>>>>>>>>> line 544, in _open
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> '_open', req)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File
> > > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >>>>>>>>>>>> line 504, in _call_chain
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> result = func(*args)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File
> > > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >>>>>>>>>>>> line 1361, in https_open
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> context=self._context, check_hostname=self._check_
> hostname)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> File
> > > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >>>>>>>>>>>> line 1320, in do_open
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> raise URLError(err)
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> > > >>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Joel Bernstein
> > > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> ------------------------------
> ---------------------------------------
> > > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>>>>> For additional commands, e-mail:
> dev-help@lucene.apache.org
> > > >>>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> ------------------------------------------------------------
> ---------
> > > >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>> ------------------------------------------------------------
> ---------
> > > >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> ------------------------------------------------------------
> ---------
> > > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>> ------------------------------------------------------------
> ---------
> > > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >> ------------------------------------------------------------
> ---------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>
> > > >>
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: dev-help@lucene.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
I’ll take a look.
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 12:46 PM, Joel Bernstein <jo...@gmail.com> wrote:
>
> I've uploaded the RC2 here https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d88652952ec3e2b3e0070/.
>
> But the smoke test breaks with SSL error in different spot when you smoke test from this URL. It's failing with a different command this time so the fix I used in other sports of smoke tester doesn't work.
>
> Steve, would you mind taking a look at this and pushing out a fix?
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
> I was thinking that if buildAndPushRelease.py can identify problems early, the RM won’t have to later redo work when a problem is found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from auto-running precommit would be worth it.
>
> But I agree that the smoke tester should be heavy, since it’s possible that the RM had weird local conditions that weren’t caught by the release production tools.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > They are both quite long processes. Perhaps we should look at eliminating some of the overlap?
> >
> > Since the smokeTesters is run by those voting on the release maybe this should be the heavier of the two.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
> > Also, I think buildAndPushRelease.py should invoke “precommit" too, (near) where it runs 'ant clean test'.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >
> > > That’s bizarre.
> > >
> > > The smoke tester runs ‘ant validate’, which does *not* include "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused imports are looked for).
> > >
> > > By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and “documentation-lint”.
> > >
> > > Jenkins caught this not because of the smoke tester, but rather because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like “precommit”, runs “check-working-copy”, “validate”, and “documentation-lint” (among others).
> > >
> > > I think we should change the smoke tester to look at the same things as precommit,
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > >> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>
> > >> Smoke testes passed as well
> > >>
> > >>
> > >> Joel Bernstein
> > >> http://joelsolr.blogspot.com/
> > >>
> > >> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >> I guess precommit is only run as part of the smoke tester.
> > >>
> > >>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>
> > >>> Interesting the entire release process completed without complaining.
> > >>>
> > >>> Joel Bernstein
> > >>> http://joelsolr.blogspot.com/
> > >>>
> > >>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >>> The unused import was the only problem; I’ve removed it on branch_6_5.
> > >>>
> > >>> Sorry, hope I didn’t cause a delay in the release process.
> > >>>
> > >>> --
> > >>> Steve
> > >>> www.lucidworks.com
> > >>>
> > >>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>
> > >>>> Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
> > >>>>
> > >>>> --
> > >>>> Steve
> > >>>> www.lucidworks.com
> > >>>>
> > >>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>
> > >>>>> Done.
> > >>>>>
> > >>>>> --
> > >>>>> Steve
> > >>>>> www.lucidworks.com
> > >>>>>
> > >>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>
> > >>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > >>>>>>
> > >>>>>> --
> > >>>>>> Steve
> > >>>>>> www.lucidworks.com
> > >>>>>>
> > >>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>
> > >>>>>>> I'm OK with restarting RC2. Let me know when you finish the back port.
> > >>>>>>>
> > >>>>>>> Joel Bernstein
> > >>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>
> > >>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>> Joel,
> > >>>>>>>
> > >>>>>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
> > >>>>>>>
> > >>>>>>> --
> > >>>>>>> Steve
> > >>>>>>> www.lucidworks.com
> > >>>>>>>
> > >>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>
> > >>>>>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
> > >>>>>>>>
> > >>>>>>>> Joel Bernstein
> > >>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>
> > >>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
> > >>>>>>>>
> > >>>>>>>> Joel Bernstein
> > >>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>
> > >>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
> > >>>>>>>>
> > >>>>>>>> Joel Bernstein
> > >>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>
> > >>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
> > >>>>>>>>
> > >>>>>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
> > >>>>>>>>
> > >>>>>>>> e.g.:
> > >>>>>>>>
> > >>>>>>>> cd ..
> > >>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> > >>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > >>>>>>>> cd lucene-solr
> > >>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
> > >>>>>>>>
> > >>>>>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
> > >>>>>>>>
> > >>>>>>>> --
> > >>>>>>>> Steve
> > >>>>>>>> www.lucidworks.com
> > >>>>>>>>
> > >>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>>
> > >>>>>>>>> Ha, that doesn't work either. Now I get this error:
> > >>>>>>>>>
> > >>>>>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
> > >>>>>>>>>
> > >>>>>>>>> So, I'm going to have to push this out.
> > >>>>>>>>>
> > >>>>>>>>> Let's first decide if this makes sense as the way forward.
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> Joel Bernstein
> > >>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>
> > >>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>> Steve, when I change the script to turn off verification I get the following error:
> > >>>>>>>>> RuntimeError: git clone is dirty:
> > >>>>>>>>>
> > >>>>>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> Joel Bernstein
> > >>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>
> > >>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> > >>>>>>>>> Could it be anything to do with the fact that the signer is Semantic
> > >>>>>>>>> and they are being actively distrusted by - at least - Google:
> > >>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
> > >>>>>>>>>
> > >>>>>>>>> Regards,
> > >>>>>>>>> Alex.
> > >>>>>>>>> ----
> > >>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> > >>>>>>>>>> was something that was integral to the process.
> > >>>>>>>>>>
> > >>>>>>>>>> Joel Bernstein
> > >>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>
> > >>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>>>>>>
> > >>>>>>>>>>> Hi Joel,
> > >>>>>>>>>>>
> > >>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > >>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> > >>>>>>>>>>> archive.apache.org?
> > >>>>>>>>>>>
> > >>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
> > >>>>>>>>>>> urllib):
> > >>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> > >>>>>>>>>>>
> > >>>>>>>>>>> Short term, you could turn off certificate verification. The bottom
> > >>>>>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
> > >>>>>>>>>>> which is assumed in the other answers on the page), to turn off certificate
> > >>>>>>>>>>> verification:
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> > >>>>>>>>>>>
> > >>>>>>>>>>> --
> > >>>>>>>>>>> Steve
> > >>>>>>>>>>> www.lucidworks.com
> > >>>>>>>>>>>
> > >>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> > >>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> > >>>>>>>>>>>> wrote:
> > >>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > >>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> > >>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
> > >>>>>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
> > >>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Traceback (most recent call last):
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> main()
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> checkDOAPfiles(version)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> > >>>>>>>>>>>> checkDOAPfiles
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> distpage = load(url)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File
> > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>>>>> line 223, in urlopen
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> return opener.open(url, data, timeout)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File
> > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>>>>> line 526, in open
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> response = self._open(req, data)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File
> > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>>>>> line 544, in _open
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> '_open', req)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File
> > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>>>>> line 504, in _call_chain
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> result = func(*args)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File
> > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>>>>> line 1361, in https_open
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File
> > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>>>>> line 1320, in do_open
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> raise URLError(err)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> > >>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> ---------------------------------------------------------------------
> > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> ---------------------------------------------------------------------
> > >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> ---------------------------------------------------------------------
> > >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> ---------------------------------------------------------------------
> > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>
> > >>>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>
> > >>
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
I've uploaded the RC2 here
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.5.1-RC2-revdfc0dd67f7fe45fbf62d88652952ec3e2b3e0070/
.
But the smoke test breaks with SSL error in different spot when you smoke
test from this URL. It's failing with a different command this time so the
fix I used in other sports of smoke tester doesn't work.
Steve, would you mind taking a look at this and pushing out a fix?
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
> I was thinking that if buildAndPushRelease.py can identify problems early,
> the RM won’t have to later redo work when a problem is found, e.g. by the
> smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from
> auto-running precommit would be worth it.
>
> But I agree that the smoke tester should be heavy, since it’s possible
> that the RM had weird local conditions that weren’t caught by the release
> production tools.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > They are both quite long processes. Perhaps we should look at
> eliminating some of the overlap?
> >
> > Since the smokeTesters is run by those voting on the release maybe this
> should be the heavier of the two.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
> > Also, I think buildAndPushRelease.py should invoke “precommit" too,
> (near) where it runs 'ant clean test'.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >
> > > That’s bizarre.
> > >
> > > The smoke tester runs ‘ant validate’, which does *not* include
> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
> imports are looked for).
> > >
> > > By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”,
> and “documentation-lint”.
> > >
> > > Jenkins caught this not because of the smoke tester, but rather
> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
> “precommit”, runs “check-working-copy”, “validate”, and
> “documentation-lint” (among others).
> > >
> > > I think we should change the smoke tester to look at the same things
> as precommit,
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > >> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>
> > >> Smoke testes passed as well
> > >>
> > >>
> > >> Joel Bernstein
> > >> http://joelsolr.blogspot.com/
> > >>
> > >> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >> I guess precommit is only run as part of the smoke tester.
> > >>
> > >>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>>
> > >>> Interesting the entire release process completed without complaining.
> > >>>
> > >>> Joel Bernstein
> > >>> http://joelsolr.blogspot.com/
> > >>>
> > >>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>> The unused import was the only problem; I’ve removed it on
> branch_6_5.
> > >>>
> > >>> Sorry, hope I didn’t cause a delay in the release process.
> > >>>
> > >>> --
> > >>> Steve
> > >>> www.lucidworks.com
> > >>>
> > >>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>
> > >>>> Crap, Jenkins found an unused import in my commit on branch_6_5
> :(. I forgot to run precommit. Doing so now.
> > >>>>
> > >>>> --
> > >>>> Steve
> > >>>> www.lucidworks.com
> > >>>>
> > >>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>
> > >>>>> Done.
> > >>>>>
> > >>>>> --
> > >>>>> Steve
> > >>>>> www.lucidworks.com
> > >>>>>
> > >>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>
> > >>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > >>>>>>
> > >>>>>> --
> > >>>>>> Steve
> > >>>>>> www.lucidworks.com
> > >>>>>>
> > >>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>>>>>>
> > >>>>>>> I'm OK with restarting RC2. Let me know when you finish the back
> port.
> > >>>>>>>
> > >>>>>>> Joel Bernstein
> > >>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>
> > >>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>>>>>> Joel,
> > >>>>>>>
> > >>>>>>> I know you’re in-process with RC2, but if you have to restart
> for some reason, I’d like to include SOLR-10527.
> > >>>>>>>
> > >>>>>>> --
> > >>>>>>> Steve
> > >>>>>>> www.lucidworks.com
> > >>>>>>>
> > >>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>>>>>>>
> > >>>>>>>> I also had to change the smoke tester because of the SSL issue.
> Which in theory means everyone else will have to as well. I'm pushing out
> my changes to branch_6_5, so people can just update their branch before
> running the smoke tester.
> > >>>>>>>>
> > >>>>>>>> Joel Bernstein
> > >>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>
> > >>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>> Ok, I had to push out three changes to the branch but I seemed
> to have moved passed this issue.
> > >>>>>>>>
> > >>>>>>>> Joel Bernstein
> > >>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>
> > >>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>> I'll push out the changes and then revert. Hopefully the
> changes will do the trick after they've been pushed.
> > >>>>>>>>
> > >>>>>>>> Joel Bernstein
> > >>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>
> > >>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>>>>>>> Yeah, that is a sucky part of this: you want to make
> modifications on the release branch, but you can’t test unless you commit
> (and push).
> > >>>>>>>>
> > >>>>>>>> Another alternative: make modifications in another checkout,
> then invoke the script with from an unmodified source tree.
> > >>>>>>>>
> > >>>>>>>> e.g.:
> > >>>>>>>>
> > >>>>>>>> cd ..
> > >>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your
> checkout dir
> > >>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > >>>>>>>> cd lucene-solr
> > >>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> …
> > >>>>>>>>
> > >>>>>>>> (a shorter form of that is to make a copy the script alone and
> invoke the modified version from your checkout)
> > >>>>>>>>
> > >>>>>>>> --
> > >>>>>>>> Steve
> > >>>>>>>> www.lucidworks.com
> > >>>>>>>>
> > >>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>>>
> > >>>>>>>>> Ha, that doesn't work either. Now I get this error:
> > >>>>>>>>>
> > >>>>>>>>> RuntimeError: There are unpushed commits - "git log
> origin/branch_6_5.." output is:
> > >>>>>>>>>
> > >>>>>>>>> So, I'm going to have to push this out.
> > >>>>>>>>>
> > >>>>>>>>> Let's first decide if this makes sense as the way forward.
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> Joel Bernstein
> > >>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>
> > >>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>>> Steve, when I change the script to turn off verification I get
> the following error:
> > >>>>>>>>> RuntimeError: git clone is dirty:
> > >>>>>>>>>
> > >>>>>>>>> So as part of the work around I think I'm going to have to
> commit locally and then revert locally. Does that make sense to you as the
> way forward?
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> Joel Bernstein
> > >>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>
> > >>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
> arafalov@gmail.com> wrote:
> > >>>>>>>>> Could it be anything to do with the fact that the signer is
> Semantic
> > >>>>>>>>> and they are being actively distrusted by - at least - Google:
> > >>>>>>>>> http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> > >>>>>>>>>
> > >>>>>>>>> Regards,
> > >>>>>>>>> Alex.
> > >>>>>>>>> ----
> > >>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new
> and experienced
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if
> cert verification
> > >>>>>>>>>> was something that was integral to the process.
> > >>>>>>>>>>
> > >>>>>>>>>> Joel Bernstein
> > >>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>
> > >>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>>>>>>>>>>
> > >>>>>>>>>>> Hi Joel,
> > >>>>>>>>>>>
> > >>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > >>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has
> been enabled on
> > >>>>>>>>>>> archive.apache.org?
> > >>>>>>>>>>>
> > >>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
> alternative to
> > >>>>>>>>>>> urllib):
> > >>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#
> what-are-hostname-doesn-t-match-errors>
> > >>>>>>>>>>>
> > >>>>>>>>>>> Short term, you could turn off certificate verification.
> The bottom
> > >>>>>>>>>>> answer here uses the same lib as the script (urllib instead
> of urllib2,
> > >>>>>>>>>>> which is assumed in the other answers on the page), to turn
> off certificate
> > >>>>>>>>>>> verification:
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> > >>>>>>>>>>>
> > >>>>>>>>>>> --
> > >>>>>>>>>>> Steve
> > >>>>>>>>>>> www.lucidworks.com
> > >>>>>>>>>>>
> > >>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> > >>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
> joelsolr@gmail.com>
> > >>>>>>>>>>>> wrote:
> > >>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > >>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
> --push-local
> > >>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I believe this is same basic command I used for RC1. But
> this time I got
> > >>>>>>>>>>>> a new error. At first I thought it might be incorrect
> keystore password but
> > >>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue
> is?
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Traceback (most recent call last):
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313,
> in <module>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> main()
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294,
> in main
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98,
> in prepare
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> checkDOAPfiles(version)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143,
> in
> > >>>>>>>>>>>> checkDOAPfiles
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> distpage = load(url)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67,
> in load
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> content = urllib.request.urlopen(
> urlString).read().decode('utf-8')
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File
> > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>>>>> line 223, in urlopen
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> return opener.open(url, data, timeout)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File
> > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>>>>> line 526, in open
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> response = self._open(req, data)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File
> > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>>>>> line 544, in _open
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> '_open', req)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File
> > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>>>>> line 504, in _call_chain
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> result = func(*args)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File
> > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>>>>> line 1361, in https_open
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> File
> > >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>>>>> line 1320, in do_open
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> raise URLError(err)
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> > >>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Joel Bernstein
> > >>>>>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> ------------------------------------------------------------
> ---------
> > >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> ------------------------------------------------------------
> ---------
> > >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> ------------------------------------------------------------
> ---------
> > >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> ------------------------------------------------------------
> ---------
> > >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>>
> > >>> ------------------------------------------------------------
> ---------
> > >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>
> > >>>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>
> > >>
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
And sure start the vote whenever you're ready.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 6:52 PM, Joel Bernstein <jo...@gmail.com> wrote:
> I think it's still RC2.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 4:58 PM, jim ferenczi <ji...@gmail.com>
> wrote:
>
>> Thanks Joel ! I can also start the vote when the release candidate is
>> ready if you want.
>> Is it still an RC2 or should I name it RC3 ?
>>
>> 2017-04-20 22:52 GMT+02:00 Joel Bernstein <jo...@gmail.com>:
>>
>>> Ok Jim, it's all yours. Thanks for stepping in. I'll delete RC2 from svn
>>> when it finishes uploading.
>>>
>>> Joel Bernstein
>>> http://joelsolr.blogspot.com/
>>>
>>> On Thu, Apr 20, 2017 at 4:46 PM, jim ferenczi <ji...@gmail.com>
>>> wrote:
>>>
>>>> I can do it Joel. As Mike said, this is a bad bug that can lead to data
>>>> lost...
>>>>
>>>> 2017-04-20 22:43 GMT+02:00 Joel Bernstein <jo...@gmail.com>:
>>>>
>>>>> I'm just uploading RC2 now. We can respin, but I won't be available
>>>>> for a respin this evening or tomorrow. If someone else wants to step in
>>>>> thats ok.
>>>>>
>>>>> Joel Bernstein
>>>>> http://joelsolr.blogspot.com/
>>>>>
>>>>> On Thu, Apr 20, 2017 at 4:28 PM, Michael McCandless <
>>>>> lucene@mikemccandless.com> wrote:
>>>>>
>>>>>> Hi Joel,
>>>>>>
>>>>>> LUCENE-7791 is actually quite a bad bug, and the patch looks low risk
>>>>>> and committable; maybe we should merge it for 6.5.1?
>>>>>>
>>>>>> Mike McCandless
>>>>>>
>>>>>> http://blog.mikemccandless.com
>>>>>>
>>>>>> On Thu, Apr 20, 2017 at 3:25 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>
>>>>>>> Joel,
>>>>>>>
>>>>>>> I’ve created <https://issues.apache.org/jira/browse/LUCENE-7793>
>>>>>>> and <https://issues.apache.org/jira/browse/LUCENE-7794> to add
>>>>>>> precommit checking (or the equivalent) to buildAndPushRelease.py and
>>>>>>> smokeTestRelease.py, respectively.
>>>>>>>
>>>>>>> --
>>>>>>> Steve
>>>>>>> www.lucidworks.com
>>>>>>>
>>>>>>> > On Apr 20, 2017, at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>> >
>>>>>>> > I was thinking that if buildAndPushRelease.py can identify
>>>>>>> problems early, the RM won’t have to later redo work when a problem is
>>>>>>> found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop
>>>>>>> anyway) from auto-running precommit would be worth it.
>>>>>>> >
>>>>>>> > But I agree that the smoke tester should be heavy, since it’s
>>>>>>> possible that the RM had weird local conditions that weren’t caught by the
>>>>>>> release production tools.
>>>>>>> >
>>>>>>> > --
>>>>>>> > Steve
>>>>>>> > www.lucidworks.com
>>>>>>> >
>>>>>>> >> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
>>>>>>> wrote:
>>>>>>> >>
>>>>>>> >> They are both quite long processes. Perhaps we should look at
>>>>>>> eliminating some of the overlap?
>>>>>>> >>
>>>>>>> >> Since the smokeTesters is run by those voting on the release
>>>>>>> maybe this should be the heavier of the two.
>>>>>>> >>
>>>>>>> >> Joel Bernstein
>>>>>>> >> http://joelsolr.blogspot.com/
>>>>>>> >>
>>>>>>> >> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
>>>>>>> wrote:
>>>>>>> >> Also, I think buildAndPushRelease.py should invoke “precommit"
>>>>>>> too, (near) where it runs 'ant clean test'.
>>>>>>> >>
>>>>>>> >> --
>>>>>>> >> Steve
>>>>>>> >> www.lucidworks.com
>>>>>>> >>
>>>>>>> >>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com>
>>>>>>> wrote:
>>>>>>> >>>
>>>>>>> >>> That’s bizarre.
>>>>>>> >>>
>>>>>>> >>> The smoke tester runs ‘ant validate’, which does *not* include
>>>>>>> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
>>>>>>> imports are looked for).
>>>>>>> >>>
>>>>>>> >>> By contrast, ‘ant precommit’ runs “check-working-copy”,
>>>>>>> “validate”, and “documentation-lint”.
>>>>>>> >>>
>>>>>>> >>> Jenkins caught this not because of the smoke tester, but rather
>>>>>>> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
>>>>>>> “precommit”, runs “check-working-copy”, “validate”, and
>>>>>>> “documentation-lint” (among others).
>>>>>>> >>>
>>>>>>> >>> I think we should change the smoke tester to look at the same
>>>>>>> things as precommit,
>>>>>>> >>>
>>>>>>> >>> --
>>>>>>> >>> Steve
>>>>>>> >>> www.lucidworks.com
>>>>>>> >>>
>>>>>>> >>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
>>>>>>> wrote:
>>>>>>> >>>>
>>>>>>> >>>> Smoke testes passed as well
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>> Joel Bernstein
>>>>>>> >>>> http://joelsolr.blogspot.com/
>>>>>>> >>>>
>>>>>>> >>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
>>>>>>> wrote:
>>>>>>> >>>> I guess precommit is only run as part of the smoke tester.
>>>>>>> >>>>
>>>>>>> >>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <
>>>>>>> joelsolr@gmail.com> wrote:
>>>>>>> >>>>>
>>>>>>> >>>>> Interesting the entire release process completed without
>>>>>>> complaining.
>>>>>>> >>>>>
>>>>>>> >>>>> Joel Bernstein
>>>>>>> >>>>> http://joelsolr.blogspot.com/
>>>>>>> >>>>>
>>>>>>> >>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
>>>>>>> wrote:
>>>>>>> >>>>> The unused import was the only problem; I’ve removed it on
>>>>>>> branch_6_5.
>>>>>>> >>>>>
>>>>>>> >>>>> Sorry, hope I didn’t cause a delay in the release process.
>>>>>>> >>>>>
>>>>>>> >>>>> --
>>>>>>> >>>>> Steve
>>>>>>> >>>>> www.lucidworks.com
>>>>>>> >>>>>
>>>>>>> >>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com>
>>>>>>> wrote:
>>>>>>> >>>>>>
>>>>>>> >>>>>> Crap, Jenkins found an unused import in my commit on
>>>>>>> branch_6_5 :(. I forgot to run precommit. Doing so now.
>>>>>>> >>>>>>
>>>>>>> >>>>>> --
>>>>>>> >>>>>> Steve
>>>>>>> >>>>>> www.lucidworks.com
>>>>>>> >>>>>>
>>>>>>> >>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
>>>>>>> wrote:
>>>>>>> >>>>>>>
>>>>>>> >>>>>>> Done.
>>>>>>> >>>>>>>
>>>>>>> >>>>>>> --
>>>>>>> >>>>>>> Steve
>>>>>>> >>>>>>> www.lucidworks.com
>>>>>>> >>>>>>>
>>>>>>> >>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
>>>>>>> wrote:
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>> --
>>>>>>> >>>>>>>> Steve
>>>>>>> >>>>>>>> www.lucidworks.com
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
>>>>>>> joelsolr@gmail.com> wrote:
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>> I'm OK with restarting RC2. Let me know when you finish
>>>>>>> the back port.
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>> Joel Bernstein
>>>>>>> >>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <
>>>>>>> sarowe@gmail.com> wrote:
>>>>>>> >>>>>>>>> Joel,
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>> I know you’re in-process with RC2, but if you have to
>>>>>>> restart for some reason, I’d like to include SOLR-10527.
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>> --
>>>>>>> >>>>>>>>> Steve
>>>>>>> >>>>>>>>> www.lucidworks.com
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
>>>>>>> joelsolr@gmail.com> wrote:
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> I also had to change the smoke tester because of the SSL
>>>>>>> issue. Which in theory means everyone else will have to as well. I'm
>>>>>>> pushing out my changes to branch_6_5, so people can just update their
>>>>>>> branch before running the smoke tester.
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> Joel Bernstein
>>>>>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
>>>>>>> joelsolr@gmail.com> wrote:
>>>>>>> >>>>>>>>>> Ok, I had to push out three changes to the branch but I
>>>>>>> seemed to have moved passed this issue.
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> Joel Bernstein
>>>>>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
>>>>>>> joelsolr@gmail.com> wrote:
>>>>>>> >>>>>>>>>> I'll push out the changes and then revert. Hopefully the
>>>>>>> changes will do the trick after they've been pushed.
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> Joel Bernstein
>>>>>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <
>>>>>>> sarowe@gmail.com> wrote:
>>>>>>> >>>>>>>>>> Yeah, that is a sucky part of this: you want to make
>>>>>>> modifications on the release branch, but you can’t test unless you commit
>>>>>>> (and push).
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> Another alternative: make modifications in another
>>>>>>> checkout, then invoke the script with from an unmodified source tree.
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> e.g.:
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> cd ..
>>>>>>> >>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is
>>>>>>> your checkout dir
>>>>>>> >>>>>>>>>> # edit lucene-solr-2/dev-tools/script
>>>>>>> s/buildAndPushRelease.py
>>>>>>> >>>>>>>>>> cd lucene-solr
>>>>>>> >>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>>>>>> …
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> (a shorter form of that is to make a copy the script
>>>>>>> alone and invoke the modified version from your checkout)
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> --
>>>>>>> >>>>>>>>>> Steve
>>>>>>> >>>>>>>>>> www.lucidworks.com
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
>>>>>>> joelsolr@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
>>>>>>> origin/branch_6_5.." output is:
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> So, I'm going to have to push this out.
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> Let's first decide if this makes sense as the way
>>>>>>> forward.
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> Joel Bernstein
>>>>>>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>>>>>>> joelsolr@gmail.com> wrote:
>>>>>>> >>>>>>>>>>> Steve, when I change the script to turn off verification
>>>>>>> I get the following error:
>>>>>>> >>>>>>>>>>> RuntimeError: git clone is dirty:
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> So as part of the work around I think I'm going to have
>>>>>>> to commit locally and then revert locally. Does that make sense to you as
>>>>>>> the way forward?
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> Joel Bernstein
>>>>>>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>>>>>>> arafalov@gmail.com> wrote:
>>>>>>> >>>>>>>>>>> Could it be anything to do with the fact that the signer
>>>>>>> is Semantic
>>>>>>> >>>>>>>>>>> and they are being actively distrusted by - at least -
>>>>>>> Google:
>>>>>>> >>>>>>>>>>> http://www.securityweek.com/go
>>>>>>> ogle-stops-trusting-symantec-issued-certificates
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> Regards,
>>>>>>> >>>>>>>>>>> Alex.
>>>>>>> >>>>>>>>>>> ----
>>>>>>> >>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users,
>>>>>>> new and experienced
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
>>>>>>> joelsolr@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure
>>>>>>> if cert verification
>>>>>>> >>>>>>>>>>>> was something that was integral to the process.
>>>>>>> >>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>> Joel Bernstein
>>>>>>> >>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>> >>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
>>>>>>> sarowe@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>> Hi Joel,
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>>>>>>> >>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication>
>>>>>>> has been enabled on
>>>>>>> >>>>>>>>>>>>> archive.apache.org?
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT
>>>>>>> an alternative to
>>>>>>> >>>>>>>>>>>>> urllib):
>>>>>>> >>>>>>>>>>>>> <http://docs.python-requests.o
>>>>>>> rg/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>> Short term, you could turn off certificate
>>>>>>> verification. The bottom
>>>>>>> >>>>>>>>>>>>> answer here uses the same lib as the script (urllib
>>>>>>> instead of urllib2,
>>>>>>> >>>>>>>>>>>>> which is assumed in the other answers on the page), to
>>>>>>> turn off certificate
>>>>>>> >>>>>>>>>>>>> verification:
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>> <http://stackoverflow.com/ques
>>>>>>> tions/19268548/python-ignore-certicate-validation-urllib2>
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>> --
>>>>>>> >>>>>>>>>>>>> Steve
>>>>>>> >>>>>>>>>>>>> www.lucidworks.com
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
>>>>>>> joelsolr@gmail.com> wrote:
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> It appears that it's failing on verifying the SSL
>>>>>>> cert for
>>>>>>> >>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> Joel Bernstein
>>>>>>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>>>>>>> joelsolr@gmail.com>
>>>>>>> >>>>>>>>>>>>>> wrote:
>>>>>>> >>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>>>>>>> >>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>>>>>>> --push-local
>>>>>>> >>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> I believe this is same basic command I used for RC1.
>>>>>>> But this time I got
>>>>>>> >>>>>>>>>>>>>> a new error. At first I thought it might be incorrect
>>>>>>> keystore password but
>>>>>>> >>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the
>>>>>>> issue is?
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> Traceback (most recent call last):
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>>>>>>> line 313, in <module>
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> main()
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>>>>>>> line 294, in main
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id,
>>>>>>> c.key_password)
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>>>>>>> line 98, in prepare
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> checkDOAPfiles(version)
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>>>>>>> line 143, in
>>>>>>> >>>>>>>>>>>>>> checkDOAPfiles
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> distpage = load(url)
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py",
>>>>>>> line 67, in load
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> content = urllib.request.urlopen(urlStri
>>>>>>> ng).read().decode('utf-8')
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> File
>>>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>> >>>>>>>>>>>>>> line 223, in urlopen
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> return opener.open(url, data, timeout)
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> File
>>>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>> >>>>>>>>>>>>>> line 526, in open
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> response = self._open(req, data)
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> File
>>>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>> >>>>>>>>>>>>>> line 544, in _open
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> '_open', req)
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> File
>>>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>> >>>>>>>>>>>>>> line 504, in _call_chain
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> result = func(*args)
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> File
>>>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>> >>>>>>>>>>>>>> line 1361, in https_open
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hos
>>>>>>> tname)
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> File
>>>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>> >>>>>>>>>>>>>> line 1320, in do_open
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> raise URLError(err)
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>>>>>>> CERTIFICATE_VERIFY_FAILED]
>>>>>>> >>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>> Joel Bernstein
>>>>>>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>> >>>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>> ------------------------------
>>>>>>> ---------------------------------------
>>>>>>> >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
>>>>>>> org
>>>>>>> >>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>> dev-help@lucene.apache.org
>>>>>>> >>>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>> ------------------------------
>>>>>>> ---------------------------------------
>>>>>>> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
>>>>>>> org
>>>>>>> >>>>>>>>>>> For additional commands, e-mail:
>>>>>>> dev-help@lucene.apache.org
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>>
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>> ------------------------------
>>>>>>> ---------------------------------------
>>>>>>> >>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>> >>>>>>>>>> For additional commands, e-mail:
>>>>>>> dev-help@lucene.apache.org
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>>
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>> ------------------------------
>>>>>>> ---------------------------------------
>>>>>>> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>> >>>>>>>>> For additional commands, e-mail:
>>>>>>> dev-help@lucene.apache.org
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>>
>>>>>>> >>>>>>>>
>>>>>>> >>>>>>>
>>>>>>> >>>>>>
>>>>>>> >>>>>
>>>>>>> >>>>>
>>>>>>> >>>>> ------------------------------------------------------------
>>>>>>> ---------
>>>>>>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>> >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>> >>>>>
>>>>>>> >>>>>
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>> ------------------------------------------------------------
>>>>>>> ---------
>>>>>>> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> ------------------------------------------------------------
>>>>>>> ---------
>>>>>>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>> >>
>>>>>>> >>
>>>>>>> >
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
I think it's still RC2.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 4:58 PM, jim ferenczi <ji...@gmail.com>
wrote:
> Thanks Joel ! I can also start the vote when the release candidate is
> ready if you want.
> Is it still an RC2 or should I name it RC3 ?
>
> 2017-04-20 22:52 GMT+02:00 Joel Bernstein <jo...@gmail.com>:
>
>> Ok Jim, it's all yours. Thanks for stepping in. I'll delete RC2 from svn
>> when it finishes uploading.
>>
>> Joel Bernstein
>> http://joelsolr.blogspot.com/
>>
>> On Thu, Apr 20, 2017 at 4:46 PM, jim ferenczi <ji...@gmail.com>
>> wrote:
>>
>>> I can do it Joel. As Mike said, this is a bad bug that can lead to data
>>> lost...
>>>
>>> 2017-04-20 22:43 GMT+02:00 Joel Bernstein <jo...@gmail.com>:
>>>
>>>> I'm just uploading RC2 now. We can respin, but I won't be available for
>>>> a respin this evening or tomorrow. If someone else wants to step in thats
>>>> ok.
>>>>
>>>> Joel Bernstein
>>>> http://joelsolr.blogspot.com/
>>>>
>>>> On Thu, Apr 20, 2017 at 4:28 PM, Michael McCandless <
>>>> lucene@mikemccandless.com> wrote:
>>>>
>>>>> Hi Joel,
>>>>>
>>>>> LUCENE-7791 is actually quite a bad bug, and the patch looks low risk
>>>>> and committable; maybe we should merge it for 6.5.1?
>>>>>
>>>>> Mike McCandless
>>>>>
>>>>> http://blog.mikemccandless.com
>>>>>
>>>>> On Thu, Apr 20, 2017 at 3:25 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>
>>>>>> Joel,
>>>>>>
>>>>>> I’ve created <https://issues.apache.org/jira/browse/LUCENE-7793> and
>>>>>> <https://issues.apache.org/jira/browse/LUCENE-7794> to add precommit
>>>>>> checking (or the equivalent) to buildAndPushRelease.py and
>>>>>> smokeTestRelease.py, respectively.
>>>>>>
>>>>>> --
>>>>>> Steve
>>>>>> www.lucidworks.com
>>>>>>
>>>>>> > On Apr 20, 2017, at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>> >
>>>>>> > I was thinking that if buildAndPushRelease.py can identify problems
>>>>>> early, the RM won’t have to later redo work when a problem is found, e.g.
>>>>>> by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from
>>>>>> auto-running precommit would be worth it.
>>>>>> >
>>>>>> > But I agree that the smoke tester should be heavy, since it’s
>>>>>> possible that the RM had weird local conditions that weren’t caught by the
>>>>>> release production tools.
>>>>>> >
>>>>>> > --
>>>>>> > Steve
>>>>>> > www.lucidworks.com
>>>>>> >
>>>>>> >> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
>>>>>> wrote:
>>>>>> >>
>>>>>> >> They are both quite long processes. Perhaps we should look at
>>>>>> eliminating some of the overlap?
>>>>>> >>
>>>>>> >> Since the smokeTesters is run by those voting on the release maybe
>>>>>> this should be the heavier of the two.
>>>>>> >>
>>>>>> >> Joel Bernstein
>>>>>> >> http://joelsolr.blogspot.com/
>>>>>> >>
>>>>>> >> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
>>>>>> wrote:
>>>>>> >> Also, I think buildAndPushRelease.py should invoke “precommit"
>>>>>> too, (near) where it runs 'ant clean test'.
>>>>>> >>
>>>>>> >> --
>>>>>> >> Steve
>>>>>> >> www.lucidworks.com
>>>>>> >>
>>>>>> >>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>> >>>
>>>>>> >>> That’s bizarre.
>>>>>> >>>
>>>>>> >>> The smoke tester runs ‘ant validate’, which does *not* include
>>>>>> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
>>>>>> imports are looked for).
>>>>>> >>>
>>>>>> >>> By contrast, ‘ant precommit’ runs “check-working-copy”,
>>>>>> “validate”, and “documentation-lint”.
>>>>>> >>>
>>>>>> >>> Jenkins caught this not because of the smoke tester, but rather
>>>>>> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
>>>>>> “precommit”, runs “check-working-copy”, “validate”, and
>>>>>> “documentation-lint” (among others).
>>>>>> >>>
>>>>>> >>> I think we should change the smoke tester to look at the same
>>>>>> things as precommit,
>>>>>> >>>
>>>>>> >>> --
>>>>>> >>> Steve
>>>>>> >>> www.lucidworks.com
>>>>>> >>>
>>>>>> >>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
>>>>>> wrote:
>>>>>> >>>>
>>>>>> >>>> Smoke testes passed as well
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>>> Joel Bernstein
>>>>>> >>>> http://joelsolr.blogspot.com/
>>>>>> >>>>
>>>>>> >>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
>>>>>> wrote:
>>>>>> >>>> I guess precommit is only run as part of the smoke tester.
>>>>>> >>>>
>>>>>> >>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
>>>>>> wrote:
>>>>>> >>>>>
>>>>>> >>>>> Interesting the entire release process completed without
>>>>>> complaining.
>>>>>> >>>>>
>>>>>> >>>>> Joel Bernstein
>>>>>> >>>>> http://joelsolr.blogspot.com/
>>>>>> >>>>>
>>>>>> >>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
>>>>>> wrote:
>>>>>> >>>>> The unused import was the only problem; I’ve removed it on
>>>>>> branch_6_5.
>>>>>> >>>>>
>>>>>> >>>>> Sorry, hope I didn’t cause a delay in the release process.
>>>>>> >>>>>
>>>>>> >>>>> --
>>>>>> >>>>> Steve
>>>>>> >>>>> www.lucidworks.com
>>>>>> >>>>>
>>>>>> >>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com>
>>>>>> wrote:
>>>>>> >>>>>>
>>>>>> >>>>>> Crap, Jenkins found an unused import in my commit on
>>>>>> branch_6_5 :(. I forgot to run precommit. Doing so now.
>>>>>> >>>>>>
>>>>>> >>>>>> --
>>>>>> >>>>>> Steve
>>>>>> >>>>>> www.lucidworks.com
>>>>>> >>>>>>
>>>>>> >>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
>>>>>> wrote:
>>>>>> >>>>>>>
>>>>>> >>>>>>> Done.
>>>>>> >>>>>>>
>>>>>> >>>>>>> --
>>>>>> >>>>>>> Steve
>>>>>> >>>>>>> www.lucidworks.com
>>>>>> >>>>>>>
>>>>>> >>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
>>>>>> wrote:
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>>>>>> >>>>>>>>
>>>>>> >>>>>>>> --
>>>>>> >>>>>>>> Steve
>>>>>> >>>>>>>> www.lucidworks.com
>>>>>> >>>>>>>>
>>>>>> >>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
>>>>>> joelsolr@gmail.com> wrote:
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the
>>>>>> back port.
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> Joel Bernstein
>>>>>> >>>>>>>>> http://joelsolr.blogspot.com/
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <
>>>>>> sarowe@gmail.com> wrote:
>>>>>> >>>>>>>>> Joel,
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> I know you’re in-process with RC2, but if you have to
>>>>>> restart for some reason, I’d like to include SOLR-10527.
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> --
>>>>>> >>>>>>>>> Steve
>>>>>> >>>>>>>>> www.lucidworks.com
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
>>>>>> joelsolr@gmail.com> wrote:
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> I also had to change the smoke tester because of the SSL
>>>>>> issue. Which in theory means everyone else will have to as well. I'm
>>>>>> pushing out my changes to branch_6_5, so people can just update their
>>>>>> branch before running the smoke tester.
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> Joel Bernstein
>>>>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
>>>>>> joelsolr@gmail.com> wrote:
>>>>>> >>>>>>>>>> Ok, I had to push out three changes to the branch but I
>>>>>> seemed to have moved passed this issue.
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> Joel Bernstein
>>>>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
>>>>>> joelsolr@gmail.com> wrote:
>>>>>> >>>>>>>>>> I'll push out the changes and then revert. Hopefully the
>>>>>> changes will do the trick after they've been pushed.
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> Joel Bernstein
>>>>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <
>>>>>> sarowe@gmail.com> wrote:
>>>>>> >>>>>>>>>> Yeah, that is a sucky part of this: you want to make
>>>>>> modifications on the release branch, but you can’t test unless you commit
>>>>>> (and push).
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> Another alternative: make modifications in another
>>>>>> checkout, then invoke the script with from an unmodified source tree.
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> e.g.:
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> cd ..
>>>>>> >>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is
>>>>>> your checkout dir
>>>>>> >>>>>>>>>> # edit lucene-solr-2/dev-tools/script
>>>>>> s/buildAndPushRelease.py
>>>>>> >>>>>>>>>> cd lucene-solr
>>>>>> >>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>>>>> …
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> (a shorter form of that is to make a copy the script alone
>>>>>> and invoke the modified version from your checkout)
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> --
>>>>>> >>>>>>>>>> Steve
>>>>>> >>>>>>>>>> www.lucidworks.com
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
>>>>>> joelsolr@gmail.com> wrote:
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
>>>>>> origin/branch_6_5.." output is:
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> So, I'm going to have to push this out.
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> Let's first decide if this makes sense as the way forward.
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> Joel Bernstein
>>>>>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>>>>>> joelsolr@gmail.com> wrote:
>>>>>> >>>>>>>>>>> Steve, when I change the script to turn off verification
>>>>>> I get the following error:
>>>>>> >>>>>>>>>>> RuntimeError: git clone is dirty:
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> So as part of the work around I think I'm going to have
>>>>>> to commit locally and then revert locally. Does that make sense to you as
>>>>>> the way forward?
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> Joel Bernstein
>>>>>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>>>>>> arafalov@gmail.com> wrote:
>>>>>> >>>>>>>>>>> Could it be anything to do with the fact that the signer
>>>>>> is Semantic
>>>>>> >>>>>>>>>>> and they are being actively distrusted by - at least -
>>>>>> Google:
>>>>>> >>>>>>>>>>> http://www.securityweek.com/go
>>>>>> ogle-stops-trusting-symantec-issued-certificates
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> Regards,
>>>>>> >>>>>>>>>>> Alex.
>>>>>> >>>>>>>>>>> ----
>>>>>> >>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users,
>>>>>> new and experienced
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
>>>>>> joelsolr@gmail.com> wrote:
>>>>>> >>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure
>>>>>> if cert verification
>>>>>> >>>>>>>>>>>> was something that was integral to the process.
>>>>>> >>>>>>>>>>>>
>>>>>> >>>>>>>>>>>> Joel Bernstein
>>>>>> >>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>> >>>>>>>>>>>>
>>>>>> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
>>>>>> sarowe@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> Hi Joel,
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>>>>>> >>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication>
>>>>>> has been enabled on
>>>>>> >>>>>>>>>>>>> archive.apache.org?
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT
>>>>>> an alternative to
>>>>>> >>>>>>>>>>>>> urllib):
>>>>>> >>>>>>>>>>>>> <http://docs.python-requests.o
>>>>>> rg/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> Short term, you could turn off certificate
>>>>>> verification. The bottom
>>>>>> >>>>>>>>>>>>> answer here uses the same lib as the script (urllib
>>>>>> instead of urllib2,
>>>>>> >>>>>>>>>>>>> which is assumed in the other answers on the page), to
>>>>>> turn off certificate
>>>>>> >>>>>>>>>>>>> verification:
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> <http://stackoverflow.com/ques
>>>>>> tions/19268548/python-ignore-certicate-validation-urllib2>
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> --
>>>>>> >>>>>>>>>>>>> Steve
>>>>>> >>>>>>>>>>>>> www.lucidworks.com
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
>>>>>> joelsolr@gmail.com> wrote:
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert
>>>>>> for
>>>>>> >>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Joel Bernstein
>>>>>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>>>>>> joelsolr@gmail.com>
>>>>>> >>>>>>>>>>>>>> wrote:
>>>>>> >>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>>>>>> >>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>>>>>> --push-local
>>>>>> >>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> I believe this is same basic command I used for RC1.
>>>>>> But this time I got
>>>>>> >>>>>>>>>>>>>> a new error. At first I thought it might be incorrect
>>>>>> keystore password but
>>>>>> >>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the
>>>>>> issue is?
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Traceback (most recent call last):
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>>>> 313, in <module>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> main()
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>>>> 294, in main
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id,
>>>>>> c.key_password)
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>>>> 98, in prepare
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> checkDOAPfiles(version)
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>>>> 143, in
>>>>>> >>>>>>>>>>>>>> checkDOAPfiles
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> distpage = load(url)
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>>>> 67, in load
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> content = urllib.request.urlopen(urlStri
>>>>>> ng).read().decode('utf-8')
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> File
>>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>> >>>>>>>>>>>>>> line 223, in urlopen
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> return opener.open(url, data, timeout)
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> File
>>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>> >>>>>>>>>>>>>> line 526, in open
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> response = self._open(req, data)
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> File
>>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>> >>>>>>>>>>>>>> line 544, in _open
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> '_open', req)
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> File
>>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>> >>>>>>>>>>>>>> line 504, in _call_chain
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> result = func(*args)
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> File
>>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>> >>>>>>>>>>>>>> line 1361, in https_open
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hos
>>>>>> tname)
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> File
>>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>> >>>>>>>>>>>>>> line 1320, in do_open
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> raise URLError(err)
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>>>>>> CERTIFICATE_VERIFY_FAILED]
>>>>>> >>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>> Joel Bernstein
>>>>>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>> >>>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>> ------------------------------
>>>>>> ---------------------------------------
>>>>>> >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
>>>>>> org
>>>>>> >>>>>>>>>>>>> For additional commands, e-mail:
>>>>>> dev-help@lucene.apache.org
>>>>>> >>>>>>>>>>>>>
>>>>>> >>>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>> ------------------------------
>>>>>> ---------------------------------------
>>>>>> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> >>>>>>>>>>> For additional commands, e-mail:
>>>>>> dev-help@lucene.apache.org
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>>
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>> ------------------------------
>>>>>> ---------------------------------------
>>>>>> >>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> >>>>>>>>>> For additional commands, e-mail:
>>>>>> dev-help@lucene.apache.org
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>>
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>> ------------------------------
>>>>>> ---------------------------------------
>>>>>> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> >>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>>
>>>>>> >>>>>>>>
>>>>>> >>>>>>>
>>>>>> >>>>>>
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>> ------------------------------------------------------------
>>>>>> ---------
>>>>>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>>> ------------------------------------------------------------
>>>>>> ---------
>>>>>> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>>
>>>>>> >>
>>>>>> >>
>>>>>> >> ------------------------------------------------------------
>>>>>> ---------
>>>>>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>> >>
>>>>>> >>
>>>>>> >
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by jim ferenczi <ji...@gmail.com>.
Thanks Joel ! I can also start the vote when the release candidate is ready
if you want.
Is it still an RC2 or should I name it RC3 ?
2017-04-20 22:52 GMT+02:00 Joel Bernstein <jo...@gmail.com>:
> Ok Jim, it's all yours. Thanks for stepping in. I'll delete RC2 from svn
> when it finishes uploading.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 4:46 PM, jim ferenczi <ji...@gmail.com>
> wrote:
>
>> I can do it Joel. As Mike said, this is a bad bug that can lead to data
>> lost...
>>
>> 2017-04-20 22:43 GMT+02:00 Joel Bernstein <jo...@gmail.com>:
>>
>>> I'm just uploading RC2 now. We can respin, but I won't be available for
>>> a respin this evening or tomorrow. If someone else wants to step in thats
>>> ok.
>>>
>>> Joel Bernstein
>>> http://joelsolr.blogspot.com/
>>>
>>> On Thu, Apr 20, 2017 at 4:28 PM, Michael McCandless <
>>> lucene@mikemccandless.com> wrote:
>>>
>>>> Hi Joel,
>>>>
>>>> LUCENE-7791 is actually quite a bad bug, and the patch looks low risk
>>>> and committable; maybe we should merge it for 6.5.1?
>>>>
>>>> Mike McCandless
>>>>
>>>> http://blog.mikemccandless.com
>>>>
>>>> On Thu, Apr 20, 2017 at 3:25 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>
>>>>> Joel,
>>>>>
>>>>> I’ve created <https://issues.apache.org/jira/browse/LUCENE-7793> and <
>>>>> https://issues.apache.org/jira/browse/LUCENE-7794> to add precommit
>>>>> checking (or the equivalent) to buildAndPushRelease.py and
>>>>> smokeTestRelease.py, respectively.
>>>>>
>>>>> --
>>>>> Steve
>>>>> www.lucidworks.com
>>>>>
>>>>> > On Apr 20, 2017, at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>>> >
>>>>> > I was thinking that if buildAndPushRelease.py can identify problems
>>>>> early, the RM won’t have to later redo work when a problem is found, e.g.
>>>>> by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from
>>>>> auto-running precommit would be worth it.
>>>>> >
>>>>> > But I agree that the smoke tester should be heavy, since it’s
>>>>> possible that the RM had weird local conditions that weren’t caught by the
>>>>> release production tools.
>>>>> >
>>>>> > --
>>>>> > Steve
>>>>> > www.lucidworks.com
>>>>> >
>>>>> >> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
>>>>> wrote:
>>>>> >>
>>>>> >> They are both quite long processes. Perhaps we should look at
>>>>> eliminating some of the overlap?
>>>>> >>
>>>>> >> Since the smokeTesters is run by those voting on the release maybe
>>>>> this should be the heavier of the two.
>>>>> >>
>>>>> >> Joel Bernstein
>>>>> >> http://joelsolr.blogspot.com/
>>>>> >>
>>>>> >> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
>>>>> wrote:
>>>>> >> Also, I think buildAndPushRelease.py should invoke “precommit" too,
>>>>> (near) where it runs 'ant clean test'.
>>>>> >>
>>>>> >> --
>>>>> >> Steve
>>>>> >> www.lucidworks.com
>>>>> >>
>>>>> >>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>>> >>>
>>>>> >>> That’s bizarre.
>>>>> >>>
>>>>> >>> The smoke tester runs ‘ant validate’, which does *not* include
>>>>> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
>>>>> imports are looked for).
>>>>> >>>
>>>>> >>> By contrast, ‘ant precommit’ runs “check-working-copy”,
>>>>> “validate”, and “documentation-lint”.
>>>>> >>>
>>>>> >>> Jenkins caught this not because of the smoke tester, but rather
>>>>> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
>>>>> “precommit”, runs “check-working-copy”, “validate”, and
>>>>> “documentation-lint” (among others).
>>>>> >>>
>>>>> >>> I think we should change the smoke tester to look at the same
>>>>> things as precommit,
>>>>> >>>
>>>>> >>> --
>>>>> >>> Steve
>>>>> >>> www.lucidworks.com
>>>>> >>>
>>>>> >>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
>>>>> wrote:
>>>>> >>>>
>>>>> >>>> Smoke testes passed as well
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> Joel Bernstein
>>>>> >>>> http://joelsolr.blogspot.com/
>>>>> >>>>
>>>>> >>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
>>>>> wrote:
>>>>> >>>> I guess precommit is only run as part of the smoke tester.
>>>>> >>>>
>>>>> >>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
>>>>> wrote:
>>>>> >>>>>
>>>>> >>>>> Interesting the entire release process completed without
>>>>> complaining.
>>>>> >>>>>
>>>>> >>>>> Joel Bernstein
>>>>> >>>>> http://joelsolr.blogspot.com/
>>>>> >>>>>
>>>>> >>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
>>>>> wrote:
>>>>> >>>>> The unused import was the only problem; I’ve removed it on
>>>>> branch_6_5.
>>>>> >>>>>
>>>>> >>>>> Sorry, hope I didn’t cause a delay in the release process.
>>>>> >>>>>
>>>>> >>>>> --
>>>>> >>>>> Steve
>>>>> >>>>> www.lucidworks.com
>>>>> >>>>>
>>>>> >>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com>
>>>>> wrote:
>>>>> >>>>>>
>>>>> >>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5
>>>>> :(. I forgot to run precommit. Doing so now.
>>>>> >>>>>>
>>>>> >>>>>> --
>>>>> >>>>>> Steve
>>>>> >>>>>> www.lucidworks.com
>>>>> >>>>>>
>>>>> >>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
>>>>> wrote:
>>>>> >>>>>>>
>>>>> >>>>>>> Done.
>>>>> >>>>>>>
>>>>> >>>>>>> --
>>>>> >>>>>>> Steve
>>>>> >>>>>>> www.lucidworks.com
>>>>> >>>>>>>
>>>>> >>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
>>>>> wrote:
>>>>> >>>>>>>>
>>>>> >>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>>>>> >>>>>>>>
>>>>> >>>>>>>> --
>>>>> >>>>>>>> Steve
>>>>> >>>>>>>> www.lucidworks.com
>>>>> >>>>>>>>
>>>>> >>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
>>>>> joelsolr@gmail.com> wrote:
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the
>>>>> back port.
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> Joel Bernstein
>>>>> >>>>>>>>> http://joelsolr.blogspot.com/
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <
>>>>> sarowe@gmail.com> wrote:
>>>>> >>>>>>>>> Joel,
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> I know you’re in-process with RC2, but if you have to
>>>>> restart for some reason, I’d like to include SOLR-10527.
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> --
>>>>> >>>>>>>>> Steve
>>>>> >>>>>>>>> www.lucidworks.com
>>>>> >>>>>>>>>
>>>>> >>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
>>>>> joelsolr@gmail.com> wrote:
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> I also had to change the smoke tester because of the SSL
>>>>> issue. Which in theory means everyone else will have to as well. I'm
>>>>> pushing out my changes to branch_6_5, so people can just update their
>>>>> branch before running the smoke tester.
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> Joel Bernstein
>>>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
>>>>> joelsolr@gmail.com> wrote:
>>>>> >>>>>>>>>> Ok, I had to push out three changes to the branch but I
>>>>> seemed to have moved passed this issue.
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> Joel Bernstein
>>>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
>>>>> joelsolr@gmail.com> wrote:
>>>>> >>>>>>>>>> I'll push out the changes and then revert. Hopefully the
>>>>> changes will do the trick after they've been pushed.
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> Joel Bernstein
>>>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <
>>>>> sarowe@gmail.com> wrote:
>>>>> >>>>>>>>>> Yeah, that is a sucky part of this: you want to make
>>>>> modifications on the release branch, but you can’t test unless you commit
>>>>> (and push).
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> Another alternative: make modifications in another
>>>>> checkout, then invoke the script with from an unmodified source tree.
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> e.g.:
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> cd ..
>>>>> >>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is
>>>>> your checkout dir
>>>>> >>>>>>>>>> # edit lucene-solr-2/dev-tools/script
>>>>> s/buildAndPushRelease.py
>>>>> >>>>>>>>>> cd lucene-solr
>>>>> >>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>>>> …
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> (a shorter form of that is to make a copy the script alone
>>>>> and invoke the modified version from your checkout)
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> --
>>>>> >>>>>>>>>> Steve
>>>>> >>>>>>>>>> www.lucidworks.com
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
>>>>> joelsolr@gmail.com> wrote:
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
>>>>> origin/branch_6_5.." output is:
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> So, I'm going to have to push this out.
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> Let's first decide if this makes sense as the way forward.
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> Joel Bernstein
>>>>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>>>>> joelsolr@gmail.com> wrote:
>>>>> >>>>>>>>>>> Steve, when I change the script to turn off verification I
>>>>> get the following error:
>>>>> >>>>>>>>>>> RuntimeError: git clone is dirty:
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> So as part of the work around I think I'm going to have to
>>>>> commit locally and then revert locally. Does that make sense to you as the
>>>>> way forward?
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> Joel Bernstein
>>>>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>>>>> arafalov@gmail.com> wrote:
>>>>> >>>>>>>>>>> Could it be anything to do with the fact that the signer
>>>>> is Semantic
>>>>> >>>>>>>>>>> and they are being actively distrusted by - at least -
>>>>> Google:
>>>>> >>>>>>>>>>> http://www.securityweek.com/go
>>>>> ogle-stops-trusting-symantec-issued-certificates
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> Regards,
>>>>> >>>>>>>>>>> Alex.
>>>>> >>>>>>>>>>> ----
>>>>> >>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users,
>>>>> new and experienced
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
>>>>> joelsolr@gmail.com> wrote:
>>>>> >>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if
>>>>> cert verification
>>>>> >>>>>>>>>>>> was something that was integral to the process.
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>> Joel Bernstein
>>>>> >>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
>>>>> sarowe@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> Hi Joel,
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>>>>> >>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication>
>>>>> has been enabled on
>>>>> >>>>>>>>>>>>> archive.apache.org?
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
>>>>> alternative to
>>>>> >>>>>>>>>>>>> urllib):
>>>>> >>>>>>>>>>>>> <http://docs.python-requests.o
>>>>> rg/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> Short term, you could turn off certificate
>>>>> verification. The bottom
>>>>> >>>>>>>>>>>>> answer here uses the same lib as the script (urllib
>>>>> instead of urllib2,
>>>>> >>>>>>>>>>>>> which is assumed in the other answers on the page), to
>>>>> turn off certificate
>>>>> >>>>>>>>>>>>> verification:
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> <http://stackoverflow.com/ques
>>>>> tions/19268548/python-ignore-certicate-validation-urllib2>
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> --
>>>>> >>>>>>>>>>>>> Steve
>>>>> >>>>>>>>>>>>> www.lucidworks.com
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
>>>>> joelsolr@gmail.com> wrote:
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert
>>>>> for
>>>>> >>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Joel Bernstein
>>>>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>>>>> joelsolr@gmail.com>
>>>>> >>>>>>>>>>>>>> wrote:
>>>>> >>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>>>>> >>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>>>>> --push-local
>>>>> >>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> I believe this is same basic command I used for RC1.
>>>>> But this time I got
>>>>> >>>>>>>>>>>>>> a new error. At first I thought it might be incorrect
>>>>> keystore password but
>>>>> >>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the
>>>>> issue is?
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Traceback (most recent call last):
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>>> 313, in <module>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> main()
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>>> 294, in main
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id,
>>>>> c.key_password)
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>>> 98, in prepare
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> checkDOAPfiles(version)
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>>> 143, in
>>>>> >>>>>>>>>>>>>> checkDOAPfiles
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> distpage = load(url)
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>>> 67, in load
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> content = urllib.request.urlopen(urlStri
>>>>> ng).read().decode('utf-8')
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> File
>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>> >>>>>>>>>>>>>> line 223, in urlopen
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> return opener.open(url, data, timeout)
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> File
>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>> >>>>>>>>>>>>>> line 526, in open
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> response = self._open(req, data)
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> File
>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>> >>>>>>>>>>>>>> line 544, in _open
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> '_open', req)
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> File
>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>> >>>>>>>>>>>>>> line 504, in _call_chain
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> result = func(*args)
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> File
>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>> >>>>>>>>>>>>>> line 1361, in https_open
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hos
>>>>> tname)
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> File
>>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>> >>>>>>>>>>>>>> line 1320, in do_open
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> raise URLError(err)
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>>>>> CERTIFICATE_VERIFY_FAILED]
>>>>> >>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>> Joel Bernstein
>>>>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>> >>>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>> ------------------------------
>>>>> ---------------------------------------
>>>>> >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.
>>>>> org
>>>>> >>>>>>>>>>>>> For additional commands, e-mail:
>>>>> dev-help@lucene.apache.org
>>>>> >>>>>>>>>>>>>
>>>>> >>>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>> ------------------------------
>>>>> ---------------------------------------
>>>>> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> >>>>>>>>>>> For additional commands, e-mail:
>>>>> dev-help@lucene.apache.org
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>> ------------------------------
>>>>> ---------------------------------------
>>>>> >>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> >>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>>
>>>>> >>>>>>>>>
>>>>> >>>>>>>>>
>>>>> >>>>>>>>> ------------------------------------------------------------
>>>>> ---------
>>>>> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> >>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>> >>>>>>>>>
>>>>> >>>>>>>>>
>>>>> >>>>>>>>
>>>>> >>>>>>>
>>>>> >>>>>>
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> ------------------------------------------------------------
>>>>> ---------
>>>>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> ------------------------------------------------------------
>>>>> ---------
>>>>> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>> >>>>
>>>>> >>>>
>>>>> >>>
>>>>> >>
>>>>> >>
>>>>> >> ------------------------------------------------------------
>>>>> ---------
>>>>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>> >>
>>>>> >>
>>>>> >
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
Ok Jim, it's all yours. Thanks for stepping in. I'll delete RC2 from svn
when it finishes uploading.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 4:46 PM, jim ferenczi <ji...@gmail.com>
wrote:
> I can do it Joel. As Mike said, this is a bad bug that can lead to data
> lost...
>
> 2017-04-20 22:43 GMT+02:00 Joel Bernstein <jo...@gmail.com>:
>
>> I'm just uploading RC2 now. We can respin, but I won't be available for a
>> respin this evening or tomorrow. If someone else wants to step in thats ok.
>>
>> Joel Bernstein
>> http://joelsolr.blogspot.com/
>>
>> On Thu, Apr 20, 2017 at 4:28 PM, Michael McCandless <
>> lucene@mikemccandless.com> wrote:
>>
>>> Hi Joel,
>>>
>>> LUCENE-7791 is actually quite a bad bug, and the patch looks low risk
>>> and committable; maybe we should merge it for 6.5.1?
>>>
>>> Mike McCandless
>>>
>>> http://blog.mikemccandless.com
>>>
>>> On Thu, Apr 20, 2017 at 3:25 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>
>>>> Joel,
>>>>
>>>> I’ve created <https://issues.apache.org/jira/browse/LUCENE-7793> and <
>>>> https://issues.apache.org/jira/browse/LUCENE-7794> to add precommit
>>>> checking (or the equivalent) to buildAndPushRelease.py and
>>>> smokeTestRelease.py, respectively.
>>>>
>>>> --
>>>> Steve
>>>> www.lucidworks.com
>>>>
>>>> > On Apr 20, 2017, at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>> >
>>>> > I was thinking that if buildAndPushRelease.py can identify problems
>>>> early, the RM won’t have to later redo work when a problem is found, e.g.
>>>> by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from
>>>> auto-running precommit would be worth it.
>>>> >
>>>> > But I agree that the smoke tester should be heavy, since it’s
>>>> possible that the RM had weird local conditions that weren’t caught by the
>>>> release production tools.
>>>> >
>>>> > --
>>>> > Steve
>>>> > www.lucidworks.com
>>>> >
>>>> >> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
>>>> wrote:
>>>> >>
>>>> >> They are both quite long processes. Perhaps we should look at
>>>> eliminating some of the overlap?
>>>> >>
>>>> >> Since the smokeTesters is run by those voting on the release maybe
>>>> this should be the heavier of the two.
>>>> >>
>>>> >> Joel Bernstein
>>>> >> http://joelsolr.blogspot.com/
>>>> >>
>>>> >> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
>>>> wrote:
>>>> >> Also, I think buildAndPushRelease.py should invoke “precommit" too,
>>>> (near) where it runs 'ant clean test'.
>>>> >>
>>>> >> --
>>>> >> Steve
>>>> >> www.lucidworks.com
>>>> >>
>>>> >>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>> >>>
>>>> >>> That’s bizarre.
>>>> >>>
>>>> >>> The smoke tester runs ‘ant validate’, which does *not* include
>>>> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
>>>> imports are looked for).
>>>> >>>
>>>> >>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”,
>>>> and “documentation-lint”.
>>>> >>>
>>>> >>> Jenkins caught this not because of the smoke tester, but rather
>>>> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
>>>> “precommit”, runs “check-working-copy”, “validate”, and
>>>> “documentation-lint” (among others).
>>>> >>>
>>>> >>> I think we should change the smoke tester to look at the same
>>>> things as precommit,
>>>> >>>
>>>> >>> --
>>>> >>> Steve
>>>> >>> www.lucidworks.com
>>>> >>>
>>>> >>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
>>>> wrote:
>>>> >>>>
>>>> >>>> Smoke testes passed as well
>>>> >>>>
>>>> >>>>
>>>> >>>> Joel Bernstein
>>>> >>>> http://joelsolr.blogspot.com/
>>>> >>>>
>>>> >>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
>>>> wrote:
>>>> >>>> I guess precommit is only run as part of the smoke tester.
>>>> >>>>
>>>> >>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
>>>> wrote:
>>>> >>>>>
>>>> >>>>> Interesting the entire release process completed without
>>>> complaining.
>>>> >>>>>
>>>> >>>>> Joel Bernstein
>>>> >>>>> http://joelsolr.blogspot.com/
>>>> >>>>>
>>>> >>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
>>>> wrote:
>>>> >>>>> The unused import was the only problem; I’ve removed it on
>>>> branch_6_5.
>>>> >>>>>
>>>> >>>>> Sorry, hope I didn’t cause a delay in the release process.
>>>> >>>>>
>>>> >>>>> --
>>>> >>>>> Steve
>>>> >>>>> www.lucidworks.com
>>>> >>>>>
>>>> >>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com>
>>>> wrote:
>>>> >>>>>>
>>>> >>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5
>>>> :(. I forgot to run precommit. Doing so now.
>>>> >>>>>>
>>>> >>>>>> --
>>>> >>>>>> Steve
>>>> >>>>>> www.lucidworks.com
>>>> >>>>>>
>>>> >>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
>>>> wrote:
>>>> >>>>>>>
>>>> >>>>>>> Done.
>>>> >>>>>>>
>>>> >>>>>>> --
>>>> >>>>>>> Steve
>>>> >>>>>>> www.lucidworks.com
>>>> >>>>>>>
>>>> >>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
>>>> wrote:
>>>> >>>>>>>>
>>>> >>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>>>> >>>>>>>>
>>>> >>>>>>>> --
>>>> >>>>>>>> Steve
>>>> >>>>>>>> www.lucidworks.com
>>>> >>>>>>>>
>>>> >>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
>>>> joelsolr@gmail.com> wrote:
>>>> >>>>>>>>>
>>>> >>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the
>>>> back port.
>>>> >>>>>>>>>
>>>> >>>>>>>>> Joel Bernstein
>>>> >>>>>>>>> http://joelsolr.blogspot.com/
>>>> >>>>>>>>>
>>>> >>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
>>>> wrote:
>>>> >>>>>>>>> Joel,
>>>> >>>>>>>>>
>>>> >>>>>>>>> I know you’re in-process with RC2, but if you have to restart
>>>> for some reason, I’d like to include SOLR-10527.
>>>> >>>>>>>>>
>>>> >>>>>>>>> --
>>>> >>>>>>>>> Steve
>>>> >>>>>>>>> www.lucidworks.com
>>>> >>>>>>>>>
>>>> >>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
>>>> joelsolr@gmail.com> wrote:
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> I also had to change the smoke tester because of the SSL
>>>> issue. Which in theory means everyone else will have to as well. I'm
>>>> pushing out my changes to branch_6_5, so people can just update their
>>>> branch before running the smoke tester.
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> Joel Bernstein
>>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
>>>> joelsolr@gmail.com> wrote:
>>>> >>>>>>>>>> Ok, I had to push out three changes to the branch but I
>>>> seemed to have moved passed this issue.
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> Joel Bernstein
>>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
>>>> joelsolr@gmail.com> wrote:
>>>> >>>>>>>>>> I'll push out the changes and then revert. Hopefully the
>>>> changes will do the trick after they've been pushed.
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> Joel Bernstein
>>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <
>>>> sarowe@gmail.com> wrote:
>>>> >>>>>>>>>> Yeah, that is a sucky part of this: you want to make
>>>> modifications on the release branch, but you can’t test unless you commit
>>>> (and push).
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> Another alternative: make modifications in another checkout,
>>>> then invoke the script with from an unmodified source tree.
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> e.g.:
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> cd ..
>>>> >>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is
>>>> your checkout dir
>>>> >>>>>>>>>> # edit lucene-solr-2/dev-tools/script
>>>> s/buildAndPushRelease.py
>>>> >>>>>>>>>> cd lucene-solr
>>>> >>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>>> …
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> (a shorter form of that is to make a copy the script alone
>>>> and invoke the modified version from your checkout)
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> --
>>>> >>>>>>>>>> Steve
>>>> >>>>>>>>>> www.lucidworks.com
>>>> >>>>>>>>>>
>>>> >>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
>>>> joelsolr@gmail.com> wrote:
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
>>>> origin/branch_6_5.." output is:
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> So, I'm going to have to push this out.
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> Let's first decide if this makes sense as the way forward.
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> Joel Bernstein
>>>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>>>> joelsolr@gmail.com> wrote:
>>>> >>>>>>>>>>> Steve, when I change the script to turn off verification I
>>>> get the following error:
>>>> >>>>>>>>>>> RuntimeError: git clone is dirty:
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> So as part of the work around I think I'm going to have to
>>>> commit locally and then revert locally. Does that make sense to you as the
>>>> way forward?
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> Joel Bernstein
>>>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>>>> arafalov@gmail.com> wrote:
>>>> >>>>>>>>>>> Could it be anything to do with the fact that the signer is
>>>> Semantic
>>>> >>>>>>>>>>> and they are being actively distrusted by - at least -
>>>> Google:
>>>> >>>>>>>>>>> http://www.securityweek.com/go
>>>> ogle-stops-trusting-symantec-issued-certificates
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> Regards,
>>>> >>>>>>>>>>> Alex.
>>>> >>>>>>>>>>> ----
>>>> >>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new
>>>> and experienced
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
>>>> joelsolr@gmail.com> wrote:
>>>> >>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if
>>>> cert verification
>>>> >>>>>>>>>>>> was something that was integral to the process.
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>> Joel Bernstein
>>>> >>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
>>>> sarowe@gmail.com> wrote:
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> Hi Joel,
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>>>> >>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication>
>>>> has been enabled on
>>>> >>>>>>>>>>>>> archive.apache.org?
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
>>>> alternative to
>>>> >>>>>>>>>>>>> urllib):
>>>> >>>>>>>>>>>>> <http://docs.python-requests.o
>>>> rg/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> Short term, you could turn off certificate verification.
>>>> The bottom
>>>> >>>>>>>>>>>>> answer here uses the same lib as the script (urllib
>>>> instead of urllib2,
>>>> >>>>>>>>>>>>> which is assumed in the other answers on the page), to
>>>> turn off certificate
>>>> >>>>>>>>>>>>> verification:
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> <http://stackoverflow.com/ques
>>>> tions/19268548/python-ignore-certicate-validation-urllib2>
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> --
>>>> >>>>>>>>>>>>> Steve
>>>> >>>>>>>>>>>>> www.lucidworks.com
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
>>>> joelsolr@gmail.com> wrote:
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert
>>>> for
>>>> >>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Joel Bernstein
>>>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>>>> joelsolr@gmail.com>
>>>> >>>>>>>>>>>>>> wrote:
>>>> >>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>>>> >>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>>>> --push-local
>>>> >>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But
>>>> this time I got
>>>> >>>>>>>>>>>>>> a new error. At first I thought it might be incorrect
>>>> keystore password but
>>>> >>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the
>>>> issue is?
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Traceback (most recent call last):
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>> 313, in <module>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> main()
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>> 294, in main
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id,
>>>> c.key_password)
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>> 98, in prepare
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> checkDOAPfiles(version)
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>> 143, in
>>>> >>>>>>>>>>>>>> checkDOAPfiles
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> distpage = load(url)
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>>> 67, in load
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> content = urllib.request.urlopen(urlStri
>>>> ng).read().decode('utf-8')
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> File
>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>> >>>>>>>>>>>>>> line 223, in urlopen
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> return opener.open(url, data, timeout)
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> File
>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>> >>>>>>>>>>>>>> line 526, in open
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> response = self._open(req, data)
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> File
>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>> >>>>>>>>>>>>>> line 544, in _open
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> '_open', req)
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> File
>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>> >>>>>>>>>>>>>> line 504, in _call_chain
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> result = func(*args)
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> File
>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>> >>>>>>>>>>>>>> line 1361, in https_open
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hos
>>>> tname)
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> File
>>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>> >>>>>>>>>>>>>> line 1320, in do_open
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> raise URLError(err)
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>>>> CERTIFICATE_VERIFY_FAILED]
>>>> >>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>> Joel Bernstein
>>>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>> >>>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>> ------------------------------
>>>> ---------------------------------------
>>>> >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> >>>>>>>>>>>>> For additional commands, e-mail:
>>>> dev-help@lucene.apache.org
>>>> >>>>>>>>>>>>>
>>>> >>>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> ------------------------------
>>>> ---------------------------------------
>>>> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> ------------------------------------------------------------
>>>> ---------
>>>> >>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> >>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>> >>>>>>>>>>
>>>> >>>>>>>>>>
>>>> >>>>>>>>>>
>>>> >>>>>>>>>>
>>>> >>>>>>>>>
>>>> >>>>>>>>>
>>>> >>>>>>>>> ------------------------------------------------------------
>>>> ---------
>>>> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> >>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>> >>>>>>>>>
>>>> >>>>>>>>>
>>>> >>>>>>>>
>>>> >>>>>>>
>>>> >>>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> ------------------------------------------------------------
>>>> ---------
>>>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>> >>>>>
>>>> >>>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> ------------------------------------------------------------
>>>> ---------
>>>> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>> >>>>
>>>> >>>>
>>>> >>>
>>>> >>
>>>> >>
>>>> >> ------------------------------------------------------------
>>>> ---------
>>>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>>>> >>
>>>> >>
>>>> >
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>>
>>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by jim ferenczi <ji...@gmail.com>.
I can do it Joel. As Mike said, this is a bad bug that can lead to data
lost...
2017-04-20 22:43 GMT+02:00 Joel Bernstein <jo...@gmail.com>:
> I'm just uploading RC2 now. We can respin, but I won't be available for a
> respin this evening or tomorrow. If someone else wants to step in thats ok.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 4:28 PM, Michael McCandless <
> lucene@mikemccandless.com> wrote:
>
>> Hi Joel,
>>
>> LUCENE-7791 is actually quite a bad bug, and the patch looks low risk and
>> committable; maybe we should merge it for 6.5.1?
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>> On Thu, Apr 20, 2017 at 3:25 PM, Steve Rowe <sa...@gmail.com> wrote:
>>
>>> Joel,
>>>
>>> I’ve created <https://issues.apache.org/jira/browse/LUCENE-7793> and <
>>> https://issues.apache.org/jira/browse/LUCENE-7794> to add precommit
>>> checking (or the equivalent) to buildAndPushRelease.py and
>>> smokeTestRelease.py, respectively.
>>>
>>> --
>>> Steve
>>> www.lucidworks.com
>>>
>>> > On Apr 20, 2017, at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
>>> >
>>> > I was thinking that if buildAndPushRelease.py can identify problems
>>> early, the RM won’t have to later redo work when a problem is found, e.g.
>>> by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from
>>> auto-running precommit would be worth it.
>>> >
>>> > But I agree that the smoke tester should be heavy, since it’s possible
>>> that the RM had weird local conditions that weren’t caught by the release
>>> production tools.
>>> >
>>> > --
>>> > Steve
>>> > www.lucidworks.com
>>> >
>>> >> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> >>
>>> >> They are both quite long processes. Perhaps we should look at
>>> eliminating some of the overlap?
>>> >>
>>> >> Since the smokeTesters is run by those voting on the release maybe
>>> this should be the heavier of the two.
>>> >>
>>> >> Joel Bernstein
>>> >> http://joelsolr.blogspot.com/
>>> >>
>>> >> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >> Also, I think buildAndPushRelease.py should invoke “precommit" too,
>>> (near) where it runs 'ant clean test'.
>>> >>
>>> >> --
>>> >> Steve
>>> >> www.lucidworks.com
>>> >>
>>> >>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
>>> >>>
>>> >>> That’s bizarre.
>>> >>>
>>> >>> The smoke tester runs ‘ant validate’, which does *not* include
>>> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
>>> imports are looked for).
>>> >>>
>>> >>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”,
>>> and “documentation-lint”.
>>> >>>
>>> >>> Jenkins caught this not because of the smoke tester, but rather
>>> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
>>> “precommit”, runs “check-working-copy”, “validate”, and
>>> “documentation-lint” (among others).
>>> >>>
>>> >>> I think we should change the smoke tester to look at the same things
>>> as precommit,
>>> >>>
>>> >>> --
>>> >>> Steve
>>> >>> www.lucidworks.com
>>> >>>
>>> >>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> >>>>
>>> >>>> Smoke testes passed as well
>>> >>>>
>>> >>>>
>>> >>>> Joel Bernstein
>>> >>>> http://joelsolr.blogspot.com/
>>> >>>>
>>> >>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>>> I guess precommit is only run as part of the smoke tester.
>>> >>>>
>>> >>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> >>>>>
>>> >>>>> Interesting the entire release process completed without
>>> complaining.
>>> >>>>>
>>> >>>>> Joel Bernstein
>>> >>>>> http://joelsolr.blogspot.com/
>>> >>>>>
>>> >>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>>>> The unused import was the only problem; I’ve removed it on
>>> branch_6_5.
>>> >>>>>
>>> >>>>> Sorry, hope I didn’t cause a delay in the release process.
>>> >>>>>
>>> >>>>> --
>>> >>>>> Steve
>>> >>>>> www.lucidworks.com
>>> >>>>>
>>> >>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
>>> >>>>>>
>>> >>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5
>>> :(. I forgot to run precommit. Doing so now.
>>> >>>>>>
>>> >>>>>> --
>>> >>>>>> Steve
>>> >>>>>> www.lucidworks.com
>>> >>>>>>
>>> >>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>>>>>>
>>> >>>>>>> Done.
>>> >>>>>>>
>>> >>>>>>> --
>>> >>>>>>> Steve
>>> >>>>>>> www.lucidworks.com
>>> >>>>>>>
>>> >>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>>>>>>>
>>> >>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>>> >>>>>>>>
>>> >>>>>>>> --
>>> >>>>>>>> Steve
>>> >>>>>>>> www.lucidworks.com
>>> >>>>>>>>
>>> >>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>
>>> >>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the
>>> back port.
>>> >>>>>>>>>
>>> >>>>>>>>> Joel Bernstein
>>> >>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>
>>> >>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>>>>>>>> Joel,
>>> >>>>>>>>>
>>> >>>>>>>>> I know you’re in-process with RC2, but if you have to restart
>>> for some reason, I’d like to include SOLR-10527.
>>> >>>>>>>>>
>>> >>>>>>>>> --
>>> >>>>>>>>> Steve
>>> >>>>>>>>> www.lucidworks.com
>>> >>>>>>>>>
>>> >>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>
>>> >>>>>>>>>> I also had to change the smoke tester because of the SSL
>>> issue. Which in theory means everyone else will have to as well. I'm
>>> pushing out my changes to branch_6_5, so people can just update their
>>> branch before running the smoke tester.
>>> >>>>>>>>>>
>>> >>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>
>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>> Ok, I had to push out three changes to the branch but I
>>> seemed to have moved passed this issue.
>>> >>>>>>>>>>
>>> >>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>
>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>> I'll push out the changes and then revert. Hopefully the
>>> changes will do the trick after they've been pushed.
>>> >>>>>>>>>>
>>> >>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>
>>> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> >>>>>>>>>> Yeah, that is a sucky part of this: you want to make
>>> modifications on the release branch, but you can’t test unless you commit
>>> (and push).
>>> >>>>>>>>>>
>>> >>>>>>>>>> Another alternative: make modifications in another checkout,
>>> then invoke the script with from an unmodified source tree.
>>> >>>>>>>>>>
>>> >>>>>>>>>> e.g.:
>>> >>>>>>>>>>
>>> >>>>>>>>>> cd ..
>>> >>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is
>>> your checkout dir
>>> >>>>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>> >>>>>>>>>> cd lucene-solr
>>> >>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>> …
>>> >>>>>>>>>>
>>> >>>>>>>>>> (a shorter form of that is to make a copy the script alone
>>> and invoke the modified version from your checkout)
>>> >>>>>>>>>>
>>> >>>>>>>>>> --
>>> >>>>>>>>>> Steve
>>> >>>>>>>>>> www.lucidworks.com
>>> >>>>>>>>>>
>>> >>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
>>> origin/branch_6_5.." output is:
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> So, I'm going to have to push this out.
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> Let's first decide if this makes sense as the way forward.
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>> Steve, when I change the script to turn off verification I
>>> get the following error:
>>> >>>>>>>>>>> RuntimeError: git clone is dirty:
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> So as part of the work around I think I'm going to have to
>>> commit locally and then revert locally. Does that make sense to you as the
>>> way forward?
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>>> arafalov@gmail.com> wrote:
>>> >>>>>>>>>>> Could it be anything to do with the fact that the signer is
>>> Semantic
>>> >>>>>>>>>>> and they are being actively distrusted by - at least -
>>> Google:
>>> >>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-i
>>> ssued-certificates
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> Regards,
>>> >>>>>>>>>>> Alex.
>>> >>>>>>>>>>> ----
>>> >>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new
>>> and experienced
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if
>>> cert verification
>>> >>>>>>>>>>>> was something that was integral to the process.
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
>>> sarowe@gmail.com> wrote:
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Hi Joel,
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>>> >>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication>
>>> has been enabled on
>>> >>>>>>>>>>>>> archive.apache.org?
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
>>> alternative to
>>> >>>>>>>>>>>>> urllib):
>>> >>>>>>>>>>>>> <http://docs.python-requests.o
>>> rg/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> Short term, you could turn off certificate verification.
>>> The bottom
>>> >>>>>>>>>>>>> answer here uses the same lib as the script (urllib
>>> instead of urllib2,
>>> >>>>>>>>>>>>> which is assumed in the other answers on the page), to
>>> turn off certificate
>>> >>>>>>>>>>>>> verification:
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> <http://stackoverflow.com/ques
>>> tions/19268548/python-ignore-certicate-validation-urllib2>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> --
>>> >>>>>>>>>>>>> Steve
>>> >>>>>>>>>>>>> www.lucidworks.com
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
>>> joelsolr@gmail.com> wrote:
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
>>> >>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>>> joelsolr@gmail.com>
>>> >>>>>>>>>>>>>> wrote:
>>> >>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>>> >>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>>> --push-local
>>> >>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But
>>> this time I got
>>> >>>>>>>>>>>>>> a new error. At first I thought it might be incorrect
>>> keystore password but
>>> >>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the
>>> issue is?
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Traceback (most recent call last):
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>> 313, in <module>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> main()
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>> 294, in main
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>> 98, in prepare
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> checkDOAPfiles(version)
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>> 143, in
>>> >>>>>>>>>>>>>> checkDOAPfiles
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> distpage = load(url)
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>>> 67, in load
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> content = urllib.request.urlopen(urlStri
>>> ng).read().decode('utf-8')
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> File
>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> >>>>>>>>>>>>>> line 223, in urlopen
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> return opener.open(url, data, timeout)
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> File
>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> >>>>>>>>>>>>>> line 526, in open
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> response = self._open(req, data)
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> File
>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> >>>>>>>>>>>>>> line 544, in _open
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> '_open', req)
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> File
>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> >>>>>>>>>>>>>> line 504, in _call_chain
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> result = func(*args)
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> File
>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> >>>>>>>>>>>>>> line 1361, in https_open
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hos
>>> tname)
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> File
>>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>>> >>>>>>>>>>>>>> line 1320, in do_open
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> raise URLError(err)
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>>> CERTIFICATE_VERIFY_FAILED]
>>> >>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>> Joel Bernstein
>>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>> >>>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>> ------------------------------
>>> ---------------------------------------
>>> >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>>>>>>>>>>>> For additional commands, e-mail:
>>> dev-help@lucene.apache.org
>>> >>>>>>>>>>>>>
>>> >>>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>> ------------------------------------------------------------
>>> ---------
>>> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>>
>>> >>>>>>>>>>
>>> >>>>>>>>>>
>>> >>>>>>>>>> ------------------------------------------------------------
>>> ---------
>>> >>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>>>>>>>>>
>>> >>>>>>>>>>
>>> >>>>>>>>>>
>>> >>>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>> ------------------------------------------------------------
>>> ---------
>>> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>
>>> >>>>>>>
>>> >>>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> ------------------------------------------------------------
>>> ---------
>>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>>>>
>>> >>>>>
>>> >>>>
>>> >>>>
>>> >>>> ------------------------------------------------------------
>>> ---------
>>> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>>>
>>> >>>>
>>> >>>
>>> >>
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>>> >>
>>> >>
>>> >
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
I'm just uploading RC2 now. We can respin, but I won't be available for a
respin this evening or tomorrow. If someone else wants to step in thats ok.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 4:28 PM, Michael McCandless <
lucene@mikemccandless.com> wrote:
> Hi Joel,
>
> LUCENE-7791 is actually quite a bad bug, and the patch looks low risk and
> committable; maybe we should merge it for 6.5.1?
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Thu, Apr 20, 2017 at 3:25 PM, Steve Rowe <sa...@gmail.com> wrote:
>
>> Joel,
>>
>> I’ve created <https://issues.apache.org/jira/browse/LUCENE-7793> and <
>> https://issues.apache.org/jira/browse/LUCENE-7794> to add precommit
>> checking (or the equivalent) to buildAndPushRelease.py and
>> smokeTestRelease.py, respectively.
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>> > On Apr 20, 2017, at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
>> >
>> > I was thinking that if buildAndPushRelease.py can identify problems
>> early, the RM won’t have to later redo work when a problem is found, e.g.
>> by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from
>> auto-running precommit would be worth it.
>> >
>> > But I agree that the smoke tester should be heavy, since it’s possible
>> that the RM had weird local conditions that weren’t caught by the release
>> production tools.
>> >
>> > --
>> > Steve
>> > www.lucidworks.com
>> >
>> >> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>
>> >> They are both quite long processes. Perhaps we should look at
>> eliminating some of the overlap?
>> >>
>> >> Since the smokeTesters is run by those voting on the release maybe
>> this should be the heavier of the two.
>> >>
>> >> Joel Bernstein
>> >> http://joelsolr.blogspot.com/
>> >>
>> >> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
>> >> Also, I think buildAndPushRelease.py should invoke “precommit" too,
>> (near) where it runs 'ant clean test'.
>> >>
>> >> --
>> >> Steve
>> >> www.lucidworks.com
>> >>
>> >>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
>> >>>
>> >>> That’s bizarre.
>> >>>
>> >>> The smoke tester runs ‘ant validate’, which does *not* include
>> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
>> imports are looked for).
>> >>>
>> >>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”,
>> and “documentation-lint”.
>> >>>
>> >>> Jenkins caught this not because of the smoke tester, but rather
>> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
>> “precommit”, runs “check-working-copy”, “validate”, and
>> “documentation-lint” (among others).
>> >>>
>> >>> I think we should change the smoke tester to look at the same things
>> as precommit,
>> >>>
>> >>> --
>> >>> Steve
>> >>> www.lucidworks.com
>> >>>
>> >>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>
>> >>>> Smoke testes passed as well
>> >>>>
>> >>>>
>> >>>> Joel Bernstein
>> >>>> http://joelsolr.blogspot.com/
>> >>>>
>> >>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>> I guess precommit is only run as part of the smoke tester.
>> >>>>
>> >>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>>
>> >>>>> Interesting the entire release process completed without
>> complaining.
>> >>>>>
>> >>>>> Joel Bernstein
>> >>>>> http://joelsolr.blogspot.com/
>> >>>>>
>> >>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>>> The unused import was the only problem; I’ve removed it on
>> branch_6_5.
>> >>>>>
>> >>>>> Sorry, hope I didn’t cause a delay in the release process.
>> >>>>>
>> >>>>> --
>> >>>>> Steve
>> >>>>> www.lucidworks.com
>> >>>>>
>> >>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
>> >>>>>>
>> >>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5
>> :(. I forgot to run precommit. Doing so now.
>> >>>>>>
>> >>>>>> --
>> >>>>>> Steve
>> >>>>>> www.lucidworks.com
>> >>>>>>
>> >>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
>> >>>>>>>
>> >>>>>>> Done.
>> >>>>>>>
>> >>>>>>> --
>> >>>>>>> Steve
>> >>>>>>> www.lucidworks.com
>> >>>>>>>
>> >>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>>>>>>
>> >>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>> Steve
>> >>>>>>>> www.lucidworks.com
>> >>>>>>>>
>> >>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>>>>>>
>> >>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the
>> back port.
>> >>>>>>>>>
>> >>>>>>>>> Joel Bernstein
>> >>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>
>> >>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>>>>>>> Joel,
>> >>>>>>>>>
>> >>>>>>>>> I know you’re in-process with RC2, but if you have to restart
>> for some reason, I’d like to include SOLR-10527.
>> >>>>>>>>>
>> >>>>>>>>> --
>> >>>>>>>>> Steve
>> >>>>>>>>> www.lucidworks.com
>> >>>>>>>>>
>> >>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> I also had to change the smoke tester because of the SSL
>> issue. Which in theory means everyone else will have to as well. I'm
>> pushing out my changes to branch_6_5, so people can just update their
>> branch before running the smoke tester.
>> >>>>>>>>>>
>> >>>>>>>>>> Joel Bernstein
>> >>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>
>> >>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>> Ok, I had to push out three changes to the branch but I seemed
>> to have moved passed this issue.
>> >>>>>>>>>>
>> >>>>>>>>>> Joel Bernstein
>> >>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>
>> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>> I'll push out the changes and then revert. Hopefully the
>> changes will do the trick after they've been pushed.
>> >>>>>>>>>>
>> >>>>>>>>>> Joel Bernstein
>> >>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>
>> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> >>>>>>>>>> Yeah, that is a sucky part of this: you want to make
>> modifications on the release branch, but you can’t test unless you commit
>> (and push).
>> >>>>>>>>>>
>> >>>>>>>>>> Another alternative: make modifications in another checkout,
>> then invoke the script with from an unmodified source tree.
>> >>>>>>>>>>
>> >>>>>>>>>> e.g.:
>> >>>>>>>>>>
>> >>>>>>>>>> cd ..
>> >>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your
>> checkout dir
>> >>>>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>> >>>>>>>>>> cd lucene-solr
>> >>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>> …
>> >>>>>>>>>>
>> >>>>>>>>>> (a shorter form of that is to make a copy the script alone and
>> invoke the modified version from your checkout)
>> >>>>>>>>>>
>> >>>>>>>>>> --
>> >>>>>>>>>> Steve
>> >>>>>>>>>> www.lucidworks.com
>> >>>>>>>>>>
>> >>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>>>
>> >>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>> >>>>>>>>>>>
>> >>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
>> origin/branch_6_5.." output is:
>> >>>>>>>>>>>
>> >>>>>>>>>>> So, I'm going to have to push this out.
>> >>>>>>>>>>>
>> >>>>>>>>>>> Let's first decide if this makes sense as the way forward.
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>>> Steve, when I change the script to turn off verification I
>> get the following error:
>> >>>>>>>>>>> RuntimeError: git clone is dirty:
>> >>>>>>>>>>>
>> >>>>>>>>>>> So as part of the work around I think I'm going to have to
>> commit locally and then revert locally. Does that make sense to you as the
>> way forward?
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>> arafalov@gmail.com> wrote:
>> >>>>>>>>>>> Could it be anything to do with the fact that the signer is
>> Semantic
>> >>>>>>>>>>> and they are being actively distrusted by - at least - Google:
>> >>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-
>> issued-certificates
>> >>>>>>>>>>>
>> >>>>>>>>>>> Regards,
>> >>>>>>>>>>> Alex.
>> >>>>>>>>>>> ----
>> >>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new
>> and experienced
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if
>> cert verification
>> >>>>>>>>>>>> was something that was integral to the process.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <
>> sarowe@gmail.com> wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Hi Joel,
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>> >>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has
>> been enabled on
>> >>>>>>>>>>>>> archive.apache.org?
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
>> alternative to
>> >>>>>>>>>>>>> urllib):
>> >>>>>>>>>>>>> <http://docs.python-requests.o
>> rg/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Short term, you could turn off certificate verification.
>> The bottom
>> >>>>>>>>>>>>> answer here uses the same lib as the script (urllib instead
>> of urllib2,
>> >>>>>>>>>>>>> which is assumed in the other answers on the page), to turn
>> off certificate
>> >>>>>>>>>>>>> verification:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-
>> certicate-validation-urllib2>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> --
>> >>>>>>>>>>>>> Steve
>> >>>>>>>>>>>>> www.lucidworks.com
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
>> >>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>> joelsolr@gmail.com>
>> >>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>> >>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>> --push-local
>> >>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But
>> this time I got
>> >>>>>>>>>>>>>> a new error. At first I thought it might be incorrect
>> keystore password but
>> >>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the
>> issue is?
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Traceback (most recent call last):
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>> 313, in <module>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> main()
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>> 294, in main
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98,
>> in prepare
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> checkDOAPfiles(version)
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line
>> 143, in
>> >>>>>>>>>>>>>> checkDOAPfiles
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> distpage = load(url)
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67,
>> in load
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> content = urllib.request.urlopen(urlStri
>> ng).read().decode('utf-8')
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> File
>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> >>>>>>>>>>>>>> line 223, in urlopen
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> return opener.open(url, data, timeout)
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> File
>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> >>>>>>>>>>>>>> line 526, in open
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> response = self._open(req, data)
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> File
>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> >>>>>>>>>>>>>> line 544, in _open
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> '_open', req)
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> File
>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> >>>>>>>>>>>>>> line 504, in _call_chain
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> result = func(*args)
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> File
>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> >>>>>>>>>>>>>> line 1361, in https_open
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hos
>> tname)
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> File
>> >>>>>>>>>>>>>> "/Library/Frameworks/Python.fr
>> amework/Versions/3.6/lib/python3.6/urllib/request.py",
>> >>>>>>>>>>>>>> line 1320, in do_open
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> raise URLError(err)
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>> CERTIFICATE_VERIFY_FAILED]
>> >>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Joel Bernstein
>> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> ------------------------------
>> ---------------------------------------
>> >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> ------------------------------------------------------------
>> ---------
>> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> ------------------------------------------------------------
>> ---------
>> >>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> ------------------------------------------------------------
>> ---------
>> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>> ------------------------------------------------------------
>> ---------
>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>> ------------------------------------------------------------
>> ---------
>> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>>>
>> >>>>
>> >>>
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>
>> >>
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Michael McCandless <lu...@mikemccandless.com>.
Hi Joel,
LUCENE-7791 is actually quite a bad bug, and the patch looks low risk and
committable; maybe we should merge it for 6.5.1?
Mike McCandless
http://blog.mikemccandless.com
On Thu, Apr 20, 2017 at 3:25 PM, Steve Rowe <sa...@gmail.com> wrote:
> Joel,
>
> I’ve created <https://issues.apache.org/jira/browse/LUCENE-7793> and <
> https://issues.apache.org/jira/browse/LUCENE-7794> to add precommit
> checking (or the equivalent) to buildAndPushRelease.py and
> smokeTestRelease.py, respectively.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
> >
> > I was thinking that if buildAndPushRelease.py can identify problems
> early, the RM won’t have to later redo work when a problem is found, e.g.
> by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from
> auto-running precommit would be worth it.
> >
> > But I agree that the smoke tester should be heavy, since it’s possible
> that the RM had weird local conditions that weren’t caught by the release
> production tools.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> >> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>
> >> They are both quite long processes. Perhaps we should look at
> eliminating some of the overlap?
> >>
> >> Since the smokeTesters is run by those voting on the release maybe this
> should be the heavier of the two.
> >>
> >> Joel Bernstein
> >> http://joelsolr.blogspot.com/
> >>
> >> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
> >> Also, I think buildAndPushRelease.py should invoke “precommit" too,
> (near) where it runs 'ant clean test'.
> >>
> >> --
> >> Steve
> >> www.lucidworks.com
> >>
> >>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>>
> >>> That’s bizarre.
> >>>
> >>> The smoke tester runs ‘ant validate’, which does *not* include
> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
> imports are looked for).
> >>>
> >>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”,
> and “documentation-lint”.
> >>>
> >>> Jenkins caught this not because of the smoke tester, but rather
> because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
> “precommit”, runs “check-working-copy”, “validate”, and
> “documentation-lint” (among others).
> >>>
> >>> I think we should change the smoke tester to look at the same things
> as precommit,
> >>>
> >>> --
> >>> Steve
> >>> www.lucidworks.com
> >>>
> >>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>
> >>>> Smoke testes passed as well
> >>>>
> >>>>
> >>>> Joel Bernstein
> >>>> http://joelsolr.blogspot.com/
> >>>>
> >>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>>> I guess precommit is only run as part of the smoke tester.
> >>>>
> >>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>
> >>>>> Interesting the entire release process completed without complaining.
> >>>>>
> >>>>> Joel Bernstein
> >>>>> http://joelsolr.blogspot.com/
> >>>>>
> >>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>> The unused import was the only problem; I’ve removed it on
> branch_6_5.
> >>>>>
> >>>>> Sorry, hope I didn’t cause a delay in the release process.
> >>>>>
> >>>>> --
> >>>>> Steve
> >>>>> www.lucidworks.com
> >>>>>
> >>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>
> >>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5
> :(. I forgot to run precommit. Doing so now.
> >>>>>>
> >>>>>> --
> >>>>>> Steve
> >>>>>> www.lucidworks.com
> >>>>>>
> >>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> Done.
> >>>>>>>
> >>>>>>> --
> >>>>>>> Steve
> >>>>>>> www.lucidworks.com
> >>>>>>>
> >>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Steve
> >>>>>>>> www.lucidworks.com
> >>>>>>>>
> >>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>>>>>
> >>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the back
> port.
> >>>>>>>>>
> >>>>>>>>> Joel Bernstein
> >>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>
> >>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>>>>> Joel,
> >>>>>>>>>
> >>>>>>>>> I know you’re in-process with RC2, but if you have to restart
> for some reason, I’d like to include SOLR-10527.
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Steve
> >>>>>>>>> www.lucidworks.com
> >>>>>>>>>
> >>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>>>>>>
> >>>>>>>>>> I also had to change the smoke tester because of the SSL issue.
> Which in theory means everyone else will have to as well. I'm pushing out
> my changes to branch_6_5, so people can just update their branch before
> running the smoke tester.
> >>>>>>>>>>
> >>>>>>>>>> Joel Bernstein
> >>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>> Ok, I had to push out three changes to the branch but I seemed
> to have moved passed this issue.
> >>>>>>>>>>
> >>>>>>>>>> Joel Bernstein
> >>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>> I'll push out the changes and then revert. Hopefully the
> changes will do the trick after they've been pushed.
> >>>>>>>>>>
> >>>>>>>>>> Joel Bernstein
> >>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>>>>>> Yeah, that is a sucky part of this: you want to make
> modifications on the release branch, but you can’t test unless you commit
> (and push).
> >>>>>>>>>>
> >>>>>>>>>> Another alternative: make modifications in another checkout,
> then invoke the script with from an unmodified source tree.
> >>>>>>>>>>
> >>>>>>>>>> e.g.:
> >>>>>>>>>>
> >>>>>>>>>> cd ..
> >>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your
> checkout dir
> >>>>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> >>>>>>>>>> cd lucene-solr
> >>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> …
> >>>>>>>>>>
> >>>>>>>>>> (a shorter form of that is to make a copy the script alone and
> invoke the modified version from your checkout)
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Steve
> >>>>>>>>>> www.lucidworks.com
> >>>>>>>>>>
> >>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
> >>>>>>>>>>>
> >>>>>>>>>>> RuntimeError: There are unpushed commits - "git log
> origin/branch_6_5.." output is:
> >>>>>>>>>>>
> >>>>>>>>>>> So, I'm going to have to push this out.
> >>>>>>>>>>>
> >>>>>>>>>>> Let's first decide if this makes sense as the way forward.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>
> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>>> Steve, when I change the script to turn off verification I get
> the following error:
> >>>>>>>>>>> RuntimeError: git clone is dirty:
> >>>>>>>>>>>
> >>>>>>>>>>> So as part of the work around I think I'm going to have to
> commit locally and then revert locally. Does that make sense to you as the
> way forward?
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>
> >>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
> arafalov@gmail.com> wrote:
> >>>>>>>>>>> Could it be anything to do with the fact that the signer is
> Semantic
> >>>>>>>>>>> and they are being actively distrusted by - at least - Google:
> >>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> >>>>>>>>>>>
> >>>>>>>>>>> Regards,
> >>>>>>>>>>> Alex.
> >>>>>>>>>>> ----
> >>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new
> and experienced
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if
> cert verification
> >>>>>>>>>>>> was something that was integral to the process.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Hi Joel,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> >>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has
> been enabled on
> >>>>>>>>>>>>> archive.apache.org?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
> alternative to
> >>>>>>>>>>>>> urllib):
> >>>>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#
> what-are-hostname-doesn-t-match-errors>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Short term, you could turn off certificate verification.
> The bottom
> >>>>>>>>>>>>> answer here uses the same lib as the script (urllib instead
> of urllib2,
> >>>>>>>>>>>>> which is assumed in the other answers on the page), to turn
> off certificate
> >>>>>>>>>>>>> verification:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> --
> >>>>>>>>>>>>> Steve
> >>>>>>>>>>>>> www.lucidworks.com
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> >>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
> joelsolr@gmail.com>
> >>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> >>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
> --push-local
> >>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But
> this time I got
> >>>>>>>>>>>>>> a new error. At first I thought it might be incorrect
> keystore password but
> >>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue
> is?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Traceback (most recent call last):
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313,
> in <module>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> main()
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294,
> in main
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98,
> in prepare
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> checkDOAPfiles(version)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143,
> in
> >>>>>>>>>>>>>> checkDOAPfiles
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> distpage = load(url)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67,
> in load
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> content = urllib.request.urlopen(
> urlString).read().decode('utf-8')
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> File
> >>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>>>> line 223, in urlopen
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> return opener.open(url, data, timeout)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> File
> >>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>>>> line 526, in open
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> response = self._open(req, data)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> File
> >>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>>>> line 544, in _open
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> '_open', req)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> File
> >>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>>>> line 504, in _call_chain
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> result = func(*args)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> File
> >>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>>>> line 1361, in https_open
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> File
> >>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>>>> line 1320, in do_open
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> raise URLError(err)
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> >>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------------------------------------
> ---------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>
> >>>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: dev-help@lucene.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
Joel,
I’ve created <https://issues.apache.org/jira/browse/LUCENE-7793> and <https://issues.apache.org/jira/browse/LUCENE-7794> to add precommit checking (or the equivalent) to buildAndPushRelease.py and smokeTestRelease.py, respectively.
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 10:29 AM, Steve Rowe <sa...@gmail.com> wrote:
>
> I was thinking that if buildAndPushRelease.py can identify problems early, the RM won’t have to later redo work when a problem is found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from auto-running precommit would be worth it.
>
> But I agree that the smoke tester should be heavy, since it’s possible that the RM had weird local conditions that weren’t caught by the release production tools.
>
> --
> Steve
> www.lucidworks.com
>
>> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com> wrote:
>>
>> They are both quite long processes. Perhaps we should look at eliminating some of the overlap?
>>
>> Since the smokeTesters is run by those voting on the release maybe this should be the heavier of the two.
>>
>> Joel Bernstein
>> http://joelsolr.blogspot.com/
>>
>> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
>> Also, I think buildAndPushRelease.py should invoke “precommit" too, (near) where it runs 'ant clean test'.
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>>> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>
>>> That’s bizarre.
>>>
>>> The smoke tester runs ‘ant validate’, which does *not* include "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused imports are looked for).
>>>
>>> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and “documentation-lint”.
>>>
>>> Jenkins caught this not because of the smoke tester, but rather because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like “precommit”, runs “check-working-copy”, “validate”, and “documentation-lint” (among others).
>>>
>>> I think we should change the smoke tester to look at the same things as precommit,
>>>
>>> --
>>> Steve
>>> www.lucidworks.com
>>>
>>>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>
>>>> Smoke testes passed as well
>>>>
>>>>
>>>> Joel Bernstein
>>>> http://joelsolr.blogspot.com/
>>>>
>>>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>> I guess precommit is only run as part of the smoke tester.
>>>>
>>>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>
>>>>> Interesting the entire release process completed without complaining.
>>>>>
>>>>> Joel Bernstein
>>>>> http://joelsolr.blogspot.com/
>>>>>
>>>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>>> The unused import was the only problem; I’ve removed it on branch_6_5.
>>>>>
>>>>> Sorry, hope I didn’t cause a delay in the release process.
>>>>>
>>>>> --
>>>>> Steve
>>>>> www.lucidworks.com
>>>>>
>>>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>
>>>>>> Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
>>>>>>
>>>>>> --
>>>>>> Steve
>>>>>> www.lucidworks.com
>>>>>>
>>>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>
>>>>>>> Done.
>>>>>>>
>>>>>>> --
>>>>>>> Steve
>>>>>>> www.lucidworks.com
>>>>>>>
>>>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Steve
>>>>>>>> www.lucidworks.com
>>>>>>>>
>>>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> I'm OK with restarting RC2. Let me know when you finish the back port.
>>>>>>>>>
>>>>>>>>> Joel Bernstein
>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>
>>>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>>> Joel,
>>>>>>>>>
>>>>>>>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Steve
>>>>>>>>> www.lucidworks.com
>>>>>>>>>
>>>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
>>>>>>>>>>
>>>>>>>>>> Joel Bernstein
>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>
>>>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
>>>>>>>>>>
>>>>>>>>>> Joel Bernstein
>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>
>>>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
>>>>>>>>>>
>>>>>>>>>> Joel Bernstein
>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>
>>>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
>>>>>>>>>>
>>>>>>>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
>>>>>>>>>>
>>>>>>>>>> e.g.:
>>>>>>>>>>
>>>>>>>>>> cd ..
>>>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
>>>>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>>>>>>>>> cd lucene-solr
>>>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
>>>>>>>>>>
>>>>>>>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Steve
>>>>>>>>>> www.lucidworks.com
>>>>>>>>>>
>>>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>>>>>>>>>>>
>>>>>>>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
>>>>>>>>>>>
>>>>>>>>>>> So, I'm going to have to push this out.
>>>>>>>>>>>
>>>>>>>>>>> Let's first decide if this makes sense as the way forward.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>> Steve, when I change the script to turn off verification I get the following error:
>>>>>>>>>>> RuntimeError: git clone is dirty:
>>>>>>>>>>>
>>>>>>>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
>>>>>>>>>>> Could it be anything to do with the fact that the signer is Semantic
>>>>>>>>>>> and they are being actively distrusted by - at least - Google:
>>>>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Alex.
>>>>>>>>>>> ----
>>>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
>>>>>>>>>>>> was something that was integral to the process.
>>>>>>>>>>>>
>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Joel,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>>>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
>>>>>>>>>>>>> archive.apache.org?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
>>>>>>>>>>>>> urllib):
>>>>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Short term, you could turn off certificate verification. The bottom
>>>>>>>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
>>>>>>>>>>>>> which is assumed in the other answers on the page), to turn off certificate
>>>>>>>>>>>>> verification:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Steve
>>>>>>>>>>>>> www.lucidworks.com
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
>>>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>>>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
>>>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
>>>>>>>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
>>>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Traceback (most recent call last):
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> main()
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> checkDOAPfiles(version)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
>>>>>>>>>>>>>> checkDOAPfiles
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> distpage = load(url)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> File
>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>>>> line 223, in urlopen
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> return opener.open(url, data, timeout)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> File
>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>>>> line 526, in open
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> response = self._open(req, data)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> File
>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>>>> line 544, in _open
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> '_open', req)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> File
>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>>>> line 504, in _call_chain
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> result = func(*args)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> File
>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>>>> line 1361, in https_open
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> File
>>>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>>>> line 1320, in do_open
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> raise URLError(err)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
>>>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
I was thinking that if buildAndPushRelease.py can identify problems early, the RM won’t have to later redo work when a problem is found, e.g. by the smoke tester. IMHO the extra 10 minutes (on my laptop anyway) from auto-running precommit would be worth it.
But I agree that the smoke tester should be heavy, since it’s possible that the RM had weird local conditions that weren’t caught by the release production tools.
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 10:23 AM, Joel Bernstein <jo...@gmail.com> wrote:
>
> They are both quite long processes. Perhaps we should look at eliminating some of the overlap?
>
> Since the smokeTesters is run by those voting on the release maybe this should be the heavier of the two.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
> Also, I think buildAndPushRelease.py should invoke “precommit" too, (near) where it runs 'ant clean test'.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> >
> > That’s bizarre.
> >
> > The smoke tester runs ‘ant validate’, which does *not* include "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused imports are looked for).
> >
> > By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and “documentation-lint”.
> >
> > Jenkins caught this not because of the smoke tester, but rather because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like “precommit”, runs “check-working-copy”, “validate”, and “documentation-lint” (among others).
> >
> > I think we should change the smoke tester to look at the same things as precommit,
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> >> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
> >>
> >> Smoke testes passed as well
> >>
> >>
> >> Joel Bernstein
> >> http://joelsolr.blogspot.com/
> >>
> >> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> >> I guess precommit is only run as part of the smoke tester.
> >>
> >>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>
> >>> Interesting the entire release process completed without complaining.
> >>>
> >>> Joel Bernstein
> >>> http://joelsolr.blogspot.com/
> >>>
> >>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>> The unused import was the only problem; I’ve removed it on branch_6_5.
> >>>
> >>> Sorry, hope I didn’t cause a delay in the release process.
> >>>
> >>> --
> >>> Steve
> >>> www.lucidworks.com
> >>>
> >>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>
> >>>> Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
> >>>>
> >>>> --
> >>>> Steve
> >>>> www.lucidworks.com
> >>>>
> >>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>
> >>>>> Done.
> >>>>>
> >>>>> --
> >>>>> Steve
> >>>>> www.lucidworks.com
> >>>>>
> >>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>
> >>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> >>>>>>
> >>>>>> --
> >>>>>> Steve
> >>>>>> www.lucidworks.com
> >>>>>>
> >>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> I'm OK with restarting RC2. Let me know when you finish the back port.
> >>>>>>>
> >>>>>>> Joel Bernstein
> >>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>
> >>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>> Joel,
> >>>>>>>
> >>>>>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
> >>>>>>>
> >>>>>>> --
> >>>>>>> Steve
> >>>>>>> www.lucidworks.com
> >>>>>>>
> >>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
> >>>>>>>>
> >>>>>>>> Joel Bernstein
> >>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>
> >>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
> >>>>>>>>
> >>>>>>>> Joel Bernstein
> >>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>
> >>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
> >>>>>>>>
> >>>>>>>> Joel Bernstein
> >>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>
> >>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
> >>>>>>>>
> >>>>>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
> >>>>>>>>
> >>>>>>>> e.g.:
> >>>>>>>>
> >>>>>>>> cd ..
> >>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> >>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> >>>>>>>> cd lucene-solr
> >>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
> >>>>>>>>
> >>>>>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Steve
> >>>>>>>> www.lucidworks.com
> >>>>>>>>
> >>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>> Ha, that doesn't work either. Now I get this error:
> >>>>>>>>>
> >>>>>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
> >>>>>>>>>
> >>>>>>>>> So, I'm going to have to push this out.
> >>>>>>>>>
> >>>>>>>>> Let's first decide if this makes sense as the way forward.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Joel Bernstein
> >>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>
> >>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>> Steve, when I change the script to turn off verification I get the following error:
> >>>>>>>>> RuntimeError: git clone is dirty:
> >>>>>>>>>
> >>>>>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Joel Bernstein
> >>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>
> >>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> >>>>>>>>> Could it be anything to do with the fact that the signer is Semantic
> >>>>>>>>> and they are being actively distrusted by - at least - Google:
> >>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>> Alex.
> >>>>>>>>> ----
> >>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> >>>>>>>>>> was something that was integral to the process.
> >>>>>>>>>>
> >>>>>>>>>> Joel Bernstein
> >>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Hi Joel,
> >>>>>>>>>>>
> >>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> >>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> >>>>>>>>>>> archive.apache.org?
> >>>>>>>>>>>
> >>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
> >>>>>>>>>>> urllib):
> >>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> >>>>>>>>>>>
> >>>>>>>>>>> Short term, you could turn off certificate verification. The bottom
> >>>>>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
> >>>>>>>>>>> which is assumed in the other answers on the page), to turn off certificate
> >>>>>>>>>>> verification:
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Steve
> >>>>>>>>>>> www.lucidworks.com
> >>>>>>>>>>>
> >>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> >>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> >>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> >>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> >>>>>>>>>>>>
> >>>>>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
> >>>>>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
> >>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
> >>>>>>>>>>>>
> >>>>>>>>>>>> Traceback (most recent call last):
> >>>>>>>>>>>>
> >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> >>>>>>>>>>>>
> >>>>>>>>>>>> main()
> >>>>>>>>>>>>
> >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> >>>>>>>>>>>>
> >>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> >>>>>>>>>>>>
> >>>>>>>>>>>> checkDOAPfiles(version)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> >>>>>>>>>>>> checkDOAPfiles
> >>>>>>>>>>>>
> >>>>>>>>>>>> distpage = load(url)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> >>>>>>>>>>>>
> >>>>>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
> >>>>>>>>>>>>
> >>>>>>>>>>>> File
> >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>>>>> line 223, in urlopen
> >>>>>>>>>>>>
> >>>>>>>>>>>> return opener.open(url, data, timeout)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File
> >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>>>>> line 526, in open
> >>>>>>>>>>>>
> >>>>>>>>>>>> response = self._open(req, data)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File
> >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>>>>> line 544, in _open
> >>>>>>>>>>>>
> >>>>>>>>>>>> '_open', req)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File
> >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>>>>> line 504, in _call_chain
> >>>>>>>>>>>>
> >>>>>>>>>>>> result = func(*args)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File
> >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>>>>> line 1361, in https_open
> >>>>>>>>>>>>
> >>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File
> >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>>>>> line 1320, in do_open
> >>>>>>>>>>>>
> >>>>>>>>>>>> raise URLError(err)
> >>>>>>>>>>>>
> >>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> >>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> ---------------------------------------------------------------------
> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> ---------------------------------------------------------------------
> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> ---------------------------------------------------------------------
> >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: dev-help@lucene.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
They are both quite long processes. Perhaps we should look at eliminating
some of the overlap?
Since the smokeTesters is run by those voting on the release maybe this
should be the heavier of the two.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 10:00 AM, Steve Rowe <sa...@gmail.com> wrote:
> Also, I think buildAndPushRelease.py should invoke “precommit" too, (near)
> where it runs 'ant clean test'.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> >
> > That’s bizarre.
> >
> > The smoke tester runs ‘ant validate’, which does *not* include
> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
> imports are looked for).
> >
> > By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and
> “documentation-lint”.
> >
> > Jenkins caught this not because of the smoke tester, but rather because
> the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
> “precommit”, runs “check-working-copy”, “validate”, and
> “documentation-lint” (among others).
> >
> > I think we should change the smoke tester to look at the same things as
> precommit,
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> >> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
> >>
> >> Smoke testes passed as well
> >>
> >>
> >> Joel Bernstein
> >> http://joelsolr.blogspot.com/
> >>
> >> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> >> I guess precommit is only run as part of the smoke tester.
> >>
> >>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>
> >>> Interesting the entire release process completed without complaining.
> >>>
> >>> Joel Bernstein
> >>> http://joelsolr.blogspot.com/
> >>>
> >>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>> The unused import was the only problem; I’ve removed it on branch_6_5.
> >>>
> >>> Sorry, hope I didn’t cause a delay in the release process.
> >>>
> >>> --
> >>> Steve
> >>> www.lucidworks.com
> >>>
> >>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>
> >>>> Crap, Jenkins found an unused import in my commit on branch_6_5 :(.
> I forgot to run precommit. Doing so now.
> >>>>
> >>>> --
> >>>> Steve
> >>>> www.lucidworks.com
> >>>>
> >>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>
> >>>>> Done.
> >>>>>
> >>>>> --
> >>>>> Steve
> >>>>> www.lucidworks.com
> >>>>>
> >>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>
> >>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> >>>>>>
> >>>>>> --
> >>>>>> Steve
> >>>>>> www.lucidworks.com
> >>>>>>
> >>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>>>
> >>>>>>> I'm OK with restarting RC2. Let me know when you finish the back
> port.
> >>>>>>>
> >>>>>>> Joel Bernstein
> >>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>
> >>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>>> Joel,
> >>>>>>>
> >>>>>>> I know you’re in-process with RC2, but if you have to restart for
> some reason, I’d like to include SOLR-10527.
> >>>>>>>
> >>>>>>> --
> >>>>>>> Steve
> >>>>>>> www.lucidworks.com
> >>>>>>>
> >>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>>>>
> >>>>>>>> I also had to change the smoke tester because of the SSL issue.
> Which in theory means everyone else will have to as well. I'm pushing out
> my changes to branch_6_5, so people can just update their branch before
> running the smoke tester.
> >>>>>>>>
> >>>>>>>> Joel Bernstein
> >>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>
> >>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>> Ok, I had to push out three changes to the branch but I seemed to
> have moved passed this issue.
> >>>>>>>>
> >>>>>>>> Joel Bernstein
> >>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>
> >>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>> I'll push out the changes and then revert. Hopefully the changes
> will do the trick after they've been pushed.
> >>>>>>>>
> >>>>>>>> Joel Bernstein
> >>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>
> >>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>>>> Yeah, that is a sucky part of this: you want to make
> modifications on the release branch, but you can’t test unless you commit
> (and push).
> >>>>>>>>
> >>>>>>>> Another alternative: make modifications in another checkout, then
> invoke the script with from an unmodified source tree.
> >>>>>>>>
> >>>>>>>> e.g.:
> >>>>>>>>
> >>>>>>>> cd ..
> >>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your
> checkout dir
> >>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> >>>>>>>> cd lucene-solr
> >>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> …
> >>>>>>>>
> >>>>>>>> (a shorter form of that is to make a copy the script alone and
> invoke the modified version from your checkout)
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Steve
> >>>>>>>> www.lucidworks.com
> >>>>>>>>
> >>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>>>>>
> >>>>>>>>> Ha, that doesn't work either. Now I get this error:
> >>>>>>>>>
> >>>>>>>>> RuntimeError: There are unpushed commits - "git log
> origin/branch_6_5.." output is:
> >>>>>>>>>
> >>>>>>>>> So, I'm going to have to push this out.
> >>>>>>>>>
> >>>>>>>>> Let's first decide if this makes sense as the way forward.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Joel Bernstein
> >>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>
> >>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>> Steve, when I change the script to turn off verification I get
> the following error:
> >>>>>>>>> RuntimeError: git clone is dirty:
> >>>>>>>>>
> >>>>>>>>> So as part of the work around I think I'm going to have to
> commit locally and then revert locally. Does that make sense to you as the
> way forward?
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Joel Bernstein
> >>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>
> >>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
> arafalov@gmail.com> wrote:
> >>>>>>>>> Could it be anything to do with the fact that the signer is
> Semantic
> >>>>>>>>> and they are being actively distrusted by - at least - Google:
> >>>>>>>>> http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>> Alex.
> >>>>>>>>> ----
> >>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and
> experienced
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert
> verification
> >>>>>>>>>> was something that was integral to the process.
> >>>>>>>>>>
> >>>>>>>>>> Joel Bernstein
> >>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Hi Joel,
> >>>>>>>>>>>
> >>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> >>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has
> been enabled on
> >>>>>>>>>>> archive.apache.org?
> >>>>>>>>>>>
> >>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
> alternative to
> >>>>>>>>>>> urllib):
> >>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#
> what-are-hostname-doesn-t-match-errors>
> >>>>>>>>>>>
> >>>>>>>>>>> Short term, you could turn off certificate verification. The
> bottom
> >>>>>>>>>>> answer here uses the same lib as the script (urllib instead of
> urllib2,
> >>>>>>>>>>> which is assumed in the other answers on the page), to turn
> off certificate
> >>>>>>>>>>> verification:
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Steve
> >>>>>>>>>>> www.lucidworks.com
> >>>>>>>>>>>
> >>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
> >>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
> joelsolr@gmail.com>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> >>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
> --push-local
> >>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> >>>>>>>>>>>>
> >>>>>>>>>>>> I believe this is same basic command I used for RC1. But this
> time I got
> >>>>>>>>>>>> a new error. At first I thought it might be incorrect
> keystore password but
> >>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue
> is?
> >>>>>>>>>>>>
> >>>>>>>>>>>> Traceback (most recent call last):
> >>>>>>>>>>>>
> >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313,
> in <module>
> >>>>>>>>>>>>
> >>>>>>>>>>>> main()
> >>>>>>>>>>>>
> >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294,
> in main
> >>>>>>>>>>>>
> >>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in
> prepare
> >>>>>>>>>>>>
> >>>>>>>>>>>> checkDOAPfiles(version)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> >>>>>>>>>>>> checkDOAPfiles
> >>>>>>>>>>>>
> >>>>>>>>>>>> distpage = load(url)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in
> load
> >>>>>>>>>>>>
> >>>>>>>>>>>> content = urllib.request.urlopen(
> urlString).read().decode('utf-8')
> >>>>>>>>>>>>
> >>>>>>>>>>>> File
> >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>> line 223, in urlopen
> >>>>>>>>>>>>
> >>>>>>>>>>>> return opener.open(url, data, timeout)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File
> >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>> line 526, in open
> >>>>>>>>>>>>
> >>>>>>>>>>>> response = self._open(req, data)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File
> >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>> line 544, in _open
> >>>>>>>>>>>>
> >>>>>>>>>>>> '_open', req)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File
> >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>> line 504, in _call_chain
> >>>>>>>>>>>>
> >>>>>>>>>>>> result = func(*args)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File
> >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>> line 1361, in https_open
> >>>>>>>>>>>>
> >>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> >>>>>>>>>>>>
> >>>>>>>>>>>> File
> >>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>>>>> line 1320, in do_open
> >>>>>>>>>>>>
> >>>>>>>>>>>> raise URLError(err)
> >>>>>>>>>>>>
> >>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> >>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Joel Bernstein
> >>>>>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: dev-help@lucene.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
Also, I think buildAndPushRelease.py should invoke “precommit" too, (near) where it runs 'ant clean test'.
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
>
> That’s bizarre.
>
> The smoke tester runs ‘ant validate’, which does *not* include "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused imports are looked for).
>
> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and “documentation-lint”.
>
> Jenkins caught this not because of the smoke tester, but rather because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like “precommit”, runs “check-working-copy”, “validate”, and “documentation-lint” (among others).
>
> I think we should change the smoke tester to look at the same things as precommit,
>
> --
> Steve
> www.lucidworks.com
>
>> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
>>
>> Smoke testes passed as well
>>
>>
>> Joel Bernstein
>> http://joelsolr.blogspot.com/
>>
>> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
>> I guess precommit is only run as part of the smoke tester.
>>
>>> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
>>>
>>> Interesting the entire release process completed without complaining.
>>>
>>> Joel Bernstein
>>> http://joelsolr.blogspot.com/
>>>
>>> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
>>> The unused import was the only problem; I’ve removed it on branch_6_5.
>>>
>>> Sorry, hope I didn’t cause a delay in the release process.
>>>
>>> --
>>> Steve
>>> www.lucidworks.com
>>>
>>>> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
>>>>
>>>> Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
>>>>
>>>> --
>>>> Steve
>>>> www.lucidworks.com
>>>>
>>>>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>
>>>>> Done.
>>>>>
>>>>> --
>>>>> Steve
>>>>> www.lucidworks.com
>>>>>
>>>>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>
>>>>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>>>>>>
>>>>>> --
>>>>>> Steve
>>>>>> www.lucidworks.com
>>>>>>
>>>>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>
>>>>>>> I'm OK with restarting RC2. Let me know when you finish the back port.
>>>>>>>
>>>>>>> Joel Bernstein
>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>
>>>>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>> Joel,
>>>>>>>
>>>>>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
>>>>>>>
>>>>>>> --
>>>>>>> Steve
>>>>>>> www.lucidworks.com
>>>>>>>
>>>>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
>>>>>>>>
>>>>>>>> Joel Bernstein
>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>
>>>>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
>>>>>>>>
>>>>>>>> Joel Bernstein
>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>
>>>>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
>>>>>>>>
>>>>>>>> Joel Bernstein
>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>
>>>>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
>>>>>>>>
>>>>>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
>>>>>>>>
>>>>>>>> e.g.:
>>>>>>>>
>>>>>>>> cd ..
>>>>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
>>>>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>>>>>>> cd lucene-solr
>>>>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
>>>>>>>>
>>>>>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
>>>>>>>>
>>>>>>>> --
>>>>>>>> Steve
>>>>>>>> www.lucidworks.com
>>>>>>>>
>>>>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Ha, that doesn't work either. Now I get this error:
>>>>>>>>>
>>>>>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
>>>>>>>>>
>>>>>>>>> So, I'm going to have to push this out.
>>>>>>>>>
>>>>>>>>> Let's first decide if this makes sense as the way forward.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Joel Bernstein
>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>
>>>>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>> Steve, when I change the script to turn off verification I get the following error:
>>>>>>>>> RuntimeError: git clone is dirty:
>>>>>>>>>
>>>>>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Joel Bernstein
>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>
>>>>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
>>>>>>>>> Could it be anything to do with the fact that the signer is Semantic
>>>>>>>>> and they are being actively distrusted by - at least - Google:
>>>>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Alex.
>>>>>>>>> ----
>>>>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
>>>>>>>>>> was something that was integral to the process.
>>>>>>>>>>
>>>>>>>>>> Joel Bernstein
>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>
>>>>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Joel,
>>>>>>>>>>>
>>>>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>>>>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
>>>>>>>>>>> archive.apache.org?
>>>>>>>>>>>
>>>>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
>>>>>>>>>>> urllib):
>>>>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>>>>>>>>>>
>>>>>>>>>>> Short term, you could turn off certificate verification. The bottom
>>>>>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
>>>>>>>>>>> which is assumed in the other answers on the page), to turn off certificate
>>>>>>>>>>> verification:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Steve
>>>>>>>>>>> www.lucidworks.com
>>>>>>>>>>>
>>>>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> It appears that it's failing on verifying the SSL cert for
>>>>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>>>>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
>>>>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>>>>>>>>>>>
>>>>>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
>>>>>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
>>>>>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
>>>>>>>>>>>>
>>>>>>>>>>>> Traceback (most recent call last):
>>>>>>>>>>>>
>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
>>>>>>>>>>>>
>>>>>>>>>>>> main()
>>>>>>>>>>>>
>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
>>>>>>>>>>>>
>>>>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
>>>>>>>>>>>>
>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
>>>>>>>>>>>>
>>>>>>>>>>>> checkDOAPfiles(version)
>>>>>>>>>>>>
>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
>>>>>>>>>>>> checkDOAPfiles
>>>>>>>>>>>>
>>>>>>>>>>>> distpage = load(url)
>>>>>>>>>>>>
>>>>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
>>>>>>>>>>>>
>>>>>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
>>>>>>>>>>>>
>>>>>>>>>>>> File
>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>> line 223, in urlopen
>>>>>>>>>>>>
>>>>>>>>>>>> return opener.open(url, data, timeout)
>>>>>>>>>>>>
>>>>>>>>>>>> File
>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>> line 526, in open
>>>>>>>>>>>>
>>>>>>>>>>>> response = self._open(req, data)
>>>>>>>>>>>>
>>>>>>>>>>>> File
>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>> line 544, in _open
>>>>>>>>>>>>
>>>>>>>>>>>> '_open', req)
>>>>>>>>>>>>
>>>>>>>>>>>> File
>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>> line 504, in _call_chain
>>>>>>>>>>>>
>>>>>>>>>>>> result = func(*args)
>>>>>>>>>>>>
>>>>>>>>>>>> File
>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>> line 1361, in https_open
>>>>>>>>>>>>
>>>>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
>>>>>>>>>>>>
>>>>>>>>>>>> File
>>>>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>>>>> line 1320, in do_open
>>>>>>>>>>>>
>>>>>>>>>>>> raise URLError(err)
>>>>>>>>>>>>
>>>>>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
>>>>>>>>>>>> certificate verify failed (_ssl.c:749)>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Joel Bernstein
>>>>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
yep
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 9:51 AM, Steve Rowe <sa...@gmail.com> wrote:
> That’s bizarre.
>
> The smoke tester runs ‘ant validate’, which does *not* include
> "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused
> imports are looked for).
>
> By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and
> “documentation-lint”.
>
> Jenkins caught this not because of the smoke tester, but rather because
> the “nightly-smoke” task it uses runs “-jenkins-base”, which, like
> “precommit”, runs “check-working-copy”, “validate”, and
> “documentation-lint” (among others).
>
> I think we should change the smoke tester to look at the same things as
> precommit,
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > Smoke testes passed as well
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> > I guess precommit is only run as part of the smoke tester.
> >
> > > On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >
> > > Interesting the entire release process completed without complaining.
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > The unused import was the only problem; I’ve removed it on branch_6_5.
> > >
> > > Sorry, hope I didn’t cause a delay in the release process.
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > > > On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> > > >
> > > > Crap, Jenkins found an unused import in my commit on branch_6_5 :(.
> I forgot to run precommit. Doing so now.
> > > >
> > > > --
> > > > Steve
> > > > www.lucidworks.com
> > > >
> > > >> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>
> > > >> Done.
> > > >>
> > > >> --
> > > >> Steve
> > > >> www.lucidworks.com
> > > >>
> > > >>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>>
> > > >>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > > >>>
> > > >>> --
> > > >>> Steve
> > > >>> www.lucidworks.com
> > > >>>
> > > >>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > >>>>
> > > >>>> I'm OK with restarting RC2. Let me know when you finish the back
> port.
> > > >>>>
> > > >>>> Joel Bernstein
> > > >>>> http://joelsolr.blogspot.com/
> > > >>>>
> > > >>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>> Joel,
> > > >>>>
> > > >>>> I know you’re in-process with RC2, but if you have to restart for
> some reason, I’d like to include SOLR-10527.
> > > >>>>
> > > >>>> --
> > > >>>> Steve
> > > >>>> www.lucidworks.com
> > > >>>>
> > > >>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > >>>>>
> > > >>>>> I also had to change the smoke tester because of the SSL issue.
> Which in theory means everyone else will have to as well. I'm pushing out
> my changes to branch_6_5, so people can just update their branch before
> running the smoke tester.
> > > >>>>>
> > > >>>>> Joel Bernstein
> > > >>>>> http://joelsolr.blogspot.com/
> > > >>>>>
> > > >>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>> Ok, I had to push out three changes to the branch but I seemed
> to have moved passed this issue.
> > > >>>>>
> > > >>>>> Joel Bernstein
> > > >>>>> http://joelsolr.blogspot.com/
> > > >>>>>
> > > >>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>> I'll push out the changes and then revert. Hopefully the changes
> will do the trick after they've been pushed.
> > > >>>>>
> > > >>>>> Joel Bernstein
> > > >>>>> http://joelsolr.blogspot.com/
> > > >>>>>
> > > >>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>>> Yeah, that is a sucky part of this: you want to make
> modifications on the release branch, but you can’t test unless you commit
> (and push).
> > > >>>>>
> > > >>>>> Another alternative: make modifications in another checkout,
> then invoke the script with from an unmodified source tree.
> > > >>>>>
> > > >>>>> e.g.:
> > > >>>>>
> > > >>>>> cd ..
> > > >>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your
> checkout dir
> > > >>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > > >>>>> cd lucene-solr
> > > >>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> …
> > > >>>>>
> > > >>>>> (a shorter form of that is to make a copy the script alone and
> invoke the modified version from your checkout)
> > > >>>>>
> > > >>>>> --
> > > >>>>> Steve
> > > >>>>> www.lucidworks.com
> > > >>>>>
> > > >>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > >>>>>>
> > > >>>>>> Ha, that doesn't work either. Now I get this error:
> > > >>>>>>
> > > >>>>>> RuntimeError: There are unpushed commits - "git log
> origin/branch_6_5.." output is:
> > > >>>>>>
> > > >>>>>> So, I'm going to have to push this out.
> > > >>>>>>
> > > >>>>>> Let's first decide if this makes sense as the way forward.
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> Joel Bernstein
> > > >>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>
> > > >>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>> Steve, when I change the script to turn off verification I get
> the following error:
> > > >>>>>> RuntimeError: git clone is dirty:
> > > >>>>>>
> > > >>>>>> So as part of the work around I think I'm going to have to
> commit locally and then revert locally. Does that make sense to you as the
> way forward?
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> Joel Bernstein
> > > >>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>
> > > >>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
> arafalov@gmail.com> wrote:
> > > >>>>>> Could it be anything to do with the fact that the signer is
> Semantic
> > > >>>>>> and they are being actively distrusted by - at least - Google:
> > > >>>>>> http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> > > >>>>>>
> > > >>>>>> Regards,
> > > >>>>>> Alex.
> > > >>>>>> ----
> > > >>>>>> http://www.solr-start.com/ - Resources for Solr users, new and
> experienced
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > >>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert
> verification
> > > >>>>>>> was something that was integral to the process.
> > > >>>>>>>
> > > >>>>>>> Joel Bernstein
> > > >>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>
> > > >>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>>>>>>>
> > > >>>>>>>> Hi Joel,
> > > >>>>>>>>
> > > >>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > > >>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has
> been enabled on
> > > >>>>>>>> archive.apache.org?
> > > >>>>>>>>
> > > >>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
> alternative to
> > > >>>>>>>> urllib):
> > > >>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#
> what-are-hostname-doesn-t-match-errors>
> > > >>>>>>>>
> > > >>>>>>>> Short term, you could turn off certificate verification. The
> bottom
> > > >>>>>>>> answer here uses the same lib as the script (urllib instead
> of urllib2,
> > > >>>>>>>> which is assumed in the other answers on the page), to turn
> off certificate
> > > >>>>>>>> verification:
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> > > >>>>>>>>
> > > >>>>>>>> --
> > > >>>>>>>> Steve
> > > >>>>>>>> www.lucidworks.com
> > > >>>>>>>>
> > > >>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > > >>>>>>>>>
> > > >>>>>>>>> It appears that it's failing on verifying the SSL cert for
> > > >>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> Joel Bernstein
> > > >>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>
> > > >>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
> joelsolr@gmail.com>
> > > >>>>>>>>> wrote:
> > > >>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > > >>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
> --push-local
> > > >>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > > >>>>>>>>>
> > > >>>>>>>>> I believe this is same basic command I used for RC1. But
> this time I got
> > > >>>>>>>>> a new error. At first I thought it might be incorrect
> keystore password but
> > > >>>>>>>>> I changed it and it is correct. Any thoughts what the issue
> is?
> > > >>>>>>>>>
> > > >>>>>>>>> Traceback (most recent call last):
> > > >>>>>>>>>
> > > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313,
> in <module>
> > > >>>>>>>>>
> > > >>>>>>>>> main()
> > > >>>>>>>>>
> > > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294,
> in main
> > > >>>>>>>>>
> > > >>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > > >>>>>>>>>
> > > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98,
> in prepare
> > > >>>>>>>>>
> > > >>>>>>>>> checkDOAPfiles(version)
> > > >>>>>>>>>
> > > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143,
> in
> > > >>>>>>>>> checkDOAPfiles
> > > >>>>>>>>>
> > > >>>>>>>>> distpage = load(url)
> > > >>>>>>>>>
> > > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67,
> in load
> > > >>>>>>>>>
> > > >>>>>>>>> content = urllib.request.urlopen(
> urlString).read().decode('utf-8')
> > > >>>>>>>>>
> > > >>>>>>>>> File
> > > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >>>>>>>>> line 223, in urlopen
> > > >>>>>>>>>
> > > >>>>>>>>> return opener.open(url, data, timeout)
> > > >>>>>>>>>
> > > >>>>>>>>> File
> > > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >>>>>>>>> line 526, in open
> > > >>>>>>>>>
> > > >>>>>>>>> response = self._open(req, data)
> > > >>>>>>>>>
> > > >>>>>>>>> File
> > > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >>>>>>>>> line 544, in _open
> > > >>>>>>>>>
> > > >>>>>>>>> '_open', req)
> > > >>>>>>>>>
> > > >>>>>>>>> File
> > > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >>>>>>>>> line 504, in _call_chain
> > > >>>>>>>>>
> > > >>>>>>>>> result = func(*args)
> > > >>>>>>>>>
> > > >>>>>>>>> File
> > > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >>>>>>>>> line 1361, in https_open
> > > >>>>>>>>>
> > > >>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> > > >>>>>>>>>
> > > >>>>>>>>> File
> > > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >>>>>>>>> line 1320, in do_open
> > > >>>>>>>>>
> > > >>>>>>>>> raise URLError(err)
> > > >>>>>>>>>
> > > >>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> > > >>>>>>>>> certificate verify failed (_ssl.c:749)>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> Joel Bernstein
> > > >>>>>>>>> http://joelsolr.blogspot.com/
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>> ------------------------------------------------------------
> ---------
> > > >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>>>
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>> ------------------------------------------------------------
> ---------
> > > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> ------------------------------------------------------------
> ---------
> > > >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>
> > > >>>>
> > > >>>> ------------------------------------------------------------
> ---------
> > > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>>>
> > > >>>>
> > > >>>
> > > >>
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: dev-help@lucene.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
That’s bizarre.
The smoke tester runs ‘ant validate’, which does *not* include "documentation-lint” (which includes "-ecj-javadoc-lint”, where unused imports are looked for).
By contrast, ‘ant precommit’ runs “check-working-copy”, “validate”, and “documentation-lint”.
Jenkins caught this not because of the smoke tester, but rather because the “nightly-smoke” task it uses runs “-jenkins-base”, which, like “precommit”, runs “check-working-copy”, “validate”, and “documentation-lint” (among others).
I think we should change the smoke tester to look at the same things as precommit,
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
>
> Smoke testes passed as well
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> I guess precommit is only run as part of the smoke tester.
>
> > On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > Interesting the entire release process completed without complaining.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> > The unused import was the only problem; I’ve removed it on branch_6_5.
> >
> > Sorry, hope I didn’t cause a delay in the release process.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >
> > > Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > >> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>
> > >> Done.
> > >>
> > >> --
> > >> Steve
> > >> www.lucidworks.com
> > >>
> > >>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>
> > >>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > >>>
> > >>> --
> > >>> Steve
> > >>> www.lucidworks.com
> > >>>
> > >>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>
> > >>>> I'm OK with restarting RC2. Let me know when you finish the back port.
> > >>>>
> > >>>> Joel Bernstein
> > >>>> http://joelsolr.blogspot.com/
> > >>>>
> > >>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>> Joel,
> > >>>>
> > >>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
> > >>>>
> > >>>> --
> > >>>> Steve
> > >>>> www.lucidworks.com
> > >>>>
> > >>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>
> > >>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
> > >>>>>
> > >>>>> Joel Bernstein
> > >>>>> http://joelsolr.blogspot.com/
> > >>>>>
> > >>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
> > >>>>>
> > >>>>> Joel Bernstein
> > >>>>> http://joelsolr.blogspot.com/
> > >>>>>
> > >>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
> > >>>>>
> > >>>>> Joel Bernstein
> > >>>>> http://joelsolr.blogspot.com/
> > >>>>>
> > >>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
> > >>>>>
> > >>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
> > >>>>>
> > >>>>> e.g.:
> > >>>>>
> > >>>>> cd ..
> > >>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> > >>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > >>>>> cd lucene-solr
> > >>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
> > >>>>>
> > >>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
> > >>>>>
> > >>>>> --
> > >>>>> Steve
> > >>>>> www.lucidworks.com
> > >>>>>
> > >>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>
> > >>>>>> Ha, that doesn't work either. Now I get this error:
> > >>>>>>
> > >>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
> > >>>>>>
> > >>>>>> So, I'm going to have to push this out.
> > >>>>>>
> > >>>>>> Let's first decide if this makes sense as the way forward.
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> Joel Bernstein
> > >>>>>> http://joelsolr.blogspot.com/
> > >>>>>>
> > >>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>> Steve, when I change the script to turn off verification I get the following error:
> > >>>>>> RuntimeError: git clone is dirty:
> > >>>>>>
> > >>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> Joel Bernstein
> > >>>>>> http://joelsolr.blogspot.com/
> > >>>>>>
> > >>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> > >>>>>> Could it be anything to do with the fact that the signer is Semantic
> > >>>>>> and they are being actively distrusted by - at least - Google:
> > >>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
> > >>>>>>
> > >>>>>> Regards,
> > >>>>>> Alex.
> > >>>>>> ----
> > >>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
> > >>>>>>
> > >>>>>>
> > >>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> > >>>>>>> was something that was integral to the process.
> > >>>>>>>
> > >>>>>>> Joel Bernstein
> > >>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>
> > >>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>>>>>>
> > >>>>>>>> Hi Joel,
> > >>>>>>>>
> > >>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > >>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> > >>>>>>>> archive.apache.org?
> > >>>>>>>>
> > >>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
> > >>>>>>>> urllib):
> > >>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> > >>>>>>>>
> > >>>>>>>> Short term, you could turn off certificate verification. The bottom
> > >>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
> > >>>>>>>> which is assumed in the other answers on the page), to turn off certificate
> > >>>>>>>> verification:
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> > >>>>>>>>
> > >>>>>>>> --
> > >>>>>>>> Steve
> > >>>>>>>> www.lucidworks.com
> > >>>>>>>>
> > >>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >>>>>>>>>
> > >>>>>>>>> It appears that it's failing on verifying the SSL cert for
> > >>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> Joel Bernstein
> > >>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>
> > >>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> > >>>>>>>>> wrote:
> > >>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > >>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> > >>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > >>>>>>>>>
> > >>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
> > >>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
> > >>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
> > >>>>>>>>>
> > >>>>>>>>> Traceback (most recent call last):
> > >>>>>>>>>
> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> > >>>>>>>>>
> > >>>>>>>>> main()
> > >>>>>>>>>
> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> > >>>>>>>>>
> > >>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > >>>>>>>>>
> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> > >>>>>>>>>
> > >>>>>>>>> checkDOAPfiles(version)
> > >>>>>>>>>
> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> > >>>>>>>>> checkDOAPfiles
> > >>>>>>>>>
> > >>>>>>>>> distpage = load(url)
> > >>>>>>>>>
> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> > >>>>>>>>>
> > >>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
> > >>>>>>>>>
> > >>>>>>>>> File
> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>> line 223, in urlopen
> > >>>>>>>>>
> > >>>>>>>>> return opener.open(url, data, timeout)
> > >>>>>>>>>
> > >>>>>>>>> File
> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>> line 526, in open
> > >>>>>>>>>
> > >>>>>>>>> response = self._open(req, data)
> > >>>>>>>>>
> > >>>>>>>>> File
> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>> line 544, in _open
> > >>>>>>>>>
> > >>>>>>>>> '_open', req)
> > >>>>>>>>>
> > >>>>>>>>> File
> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>> line 504, in _call_chain
> > >>>>>>>>>
> > >>>>>>>>> result = func(*args)
> > >>>>>>>>>
> > >>>>>>>>> File
> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>> line 1361, in https_open
> > >>>>>>>>>
> > >>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> > >>>>>>>>>
> > >>>>>>>>> File
> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >>>>>>>>> line 1320, in do_open
> > >>>>>>>>>
> > >>>>>>>>> raise URLError(err)
> > >>>>>>>>>
> > >>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> > >>>>>>>>> certificate verify failed (_ssl.c:749)>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> Joel Bernstein
> > >>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> ---------------------------------------------------------------------
> > >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>> ---------------------------------------------------------------------
> > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>> ---------------------------------------------------------------------
> > >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>
> > >>>>
> > >>>
> > >>
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
OK, I've pulled the branch again and starting rebuilding the RC.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 9:29 AM, Joel Bernstein <jo...@gmail.com> wrote:
> Smoke testes passed as well
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
>
>> I guess precommit is only run as part of the smoke tester.
>>
>> > On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
>> >
>> > Interesting the entire release process completed without complaining.
>> >
>> > Joel Bernstein
>> > http://joelsolr.blogspot.com/
>> >
>> > On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
>> > The unused import was the only problem; I’ve removed it on branch_6_5.
>> >
>> > Sorry, hope I didn’t cause a delay in the release process.
>> >
>> > --
>> > Steve
>> > www.lucidworks.com
>> >
>> > > On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
>> > >
>> > > Crap, Jenkins found an unused import in my commit on branch_6_5 :(.
>> I forgot to run precommit. Doing so now.
>> > >
>> > > --
>> > > Steve
>> > > www.lucidworks.com
>> > >
>> > >> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
>> > >>
>> > >> Done.
>> > >>
>> > >> --
>> > >> Steve
>> > >> www.lucidworks.com
>> > >>
>> > >>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
>> > >>>
>> > >>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>> > >>>
>> > >>> --
>> > >>> Steve
>> > >>> www.lucidworks.com
>> > >>>
>> > >>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > >>>>
>> > >>>> I'm OK with restarting RC2. Let me know when you finish the back
>> port.
>> > >>>>
>> > >>>> Joel Bernstein
>> > >>>> http://joelsolr.blogspot.com/
>> > >>>>
>> > >>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > >>>> Joel,
>> > >>>>
>> > >>>> I know you’re in-process with RC2, but if you have to restart for
>> some reason, I’d like to include SOLR-10527.
>> > >>>>
>> > >>>> --
>> > >>>> Steve
>> > >>>> www.lucidworks.com
>> > >>>>
>> > >>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > >>>>>
>> > >>>>> I also had to change the smoke tester because of the SSL issue.
>> Which in theory means everyone else will have to as well. I'm pushing out
>> my changes to branch_6_5, so people can just update their branch before
>> running the smoke tester.
>> > >>>>>
>> > >>>>> Joel Bernstein
>> > >>>>> http://joelsolr.blogspot.com/
>> > >>>>>
>> > >>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > >>>>> Ok, I had to push out three changes to the branch but I seemed to
>> have moved passed this issue.
>> > >>>>>
>> > >>>>> Joel Bernstein
>> > >>>>> http://joelsolr.blogspot.com/
>> > >>>>>
>> > >>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > >>>>> I'll push out the changes and then revert. Hopefully the changes
>> will do the trick after they've been pushed.
>> > >>>>>
>> > >>>>> Joel Bernstein
>> > >>>>> http://joelsolr.blogspot.com/
>> > >>>>>
>> > >>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > >>>>> Yeah, that is a sucky part of this: you want to make
>> modifications on the release branch, but you can’t test unless you commit
>> (and push).
>> > >>>>>
>> > >>>>> Another alternative: make modifications in another checkout, then
>> invoke the script with from an unmodified source tree.
>> > >>>>>
>> > >>>>> e.g.:
>> > >>>>>
>> > >>>>> cd ..
>> > >>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your
>> checkout dir
>> > >>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>> > >>>>> cd lucene-solr
>> > >>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>> …
>> > >>>>>
>> > >>>>> (a shorter form of that is to make a copy the script alone and
>> invoke the modified version from your checkout)
>> > >>>>>
>> > >>>>> --
>> > >>>>> Steve
>> > >>>>> www.lucidworks.com
>> > >>>>>
>> > >>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > >>>>>>
>> > >>>>>> Ha, that doesn't work either. Now I get this error:
>> > >>>>>>
>> > >>>>>> RuntimeError: There are unpushed commits - "git log
>> origin/branch_6_5.." output is:
>> > >>>>>>
>> > >>>>>> So, I'm going to have to push this out.
>> > >>>>>>
>> > >>>>>> Let's first decide if this makes sense as the way forward.
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>> Joel Bernstein
>> > >>>>>> http://joelsolr.blogspot.com/
>> > >>>>>>
>> > >>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > >>>>>> Steve, when I change the script to turn off verification I get
>> the following error:
>> > >>>>>> RuntimeError: git clone is dirty:
>> > >>>>>>
>> > >>>>>> So as part of the work around I think I'm going to have to
>> commit locally and then revert locally. Does that make sense to you as the
>> way forward?
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>> Joel Bernstein
>> > >>>>>> http://joelsolr.blogspot.com/
>> > >>>>>>
>> > >>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>> arafalov@gmail.com> wrote:
>> > >>>>>> Could it be anything to do with the fact that the signer is
>> Semantic
>> > >>>>>> and they are being actively distrusted by - at least - Google:
>> > >>>>>> http://www.securityweek.com/google-stops-trusting-symantec-
>> issued-certificates
>> > >>>>>>
>> > >>>>>> Regards,
>> > >>>>>> Alex.
>> > >>>>>> ----
>> > >>>>>> http://www.solr-start.com/ - Resources for Solr users, new and
>> experienced
>> > >>>>>>
>> > >>>>>>
>> > >>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > >>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert
>> verification
>> > >>>>>>> was something that was integral to the process.
>> > >>>>>>>
>> > >>>>>>> Joel Bernstein
>> > >>>>>>> http://joelsolr.blogspot.com/
>> > >>>>>>>
>> > >>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com>
>> wrote:
>> > >>>>>>>>
>> > >>>>>>>> Hi Joel,
>> > >>>>>>>>
>> > >>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>> > >>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has
>> been enabled on
>> > >>>>>>>> archive.apache.org?
>> > >>>>>>>>
>> > >>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
>> alternative to
>> > >>>>>>>> urllib):
>> > >>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#wh
>> at-are-hostname-doesn-t-match-errors>
>> > >>>>>>>>
>> > >>>>>>>> Short term, you could turn off certificate verification. The
>> bottom
>> > >>>>>>>> answer here uses the same lib as the script (urllib instead of
>> urllib2,
>> > >>>>>>>> which is assumed in the other answers on the page), to turn
>> off certificate
>> > >>>>>>>> verification:
>> > >>>>>>>>
>> > >>>>>>>>
>> > >>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-
>> certicate-validation-urllib2>
>> > >>>>>>>>
>> > >>>>>>>> --
>> > >>>>>>>> Steve
>> > >>>>>>>> www.lucidworks.com
>> > >>>>>>>>
>> > >>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
>> joelsolr@gmail.com> wrote:
>> > >>>>>>>>>
>> > >>>>>>>>> It appears that it's failing on verifying the SSL cert for
>> > >>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>> > >>>>>>>>>
>> > >>>>>>>>>
>> > >>>>>>>>>
>> > >>>>>>>>> Joel Bernstein
>> > >>>>>>>>> http://joelsolr.blogspot.com/
>> > >>>>>>>>>
>> > >>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>> joelsolr@gmail.com>
>> > >>>>>>>>> wrote:
>> > >>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>> > >>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
>> --push-local
>> > >>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>> > >>>>>>>>>
>> > >>>>>>>>> I believe this is same basic command I used for RC1. But this
>> time I got
>> > >>>>>>>>> a new error. At first I thought it might be incorrect
>> keystore password but
>> > >>>>>>>>> I changed it and it is correct. Any thoughts what the issue
>> is?
>> > >>>>>>>>>
>> > >>>>>>>>> Traceback (most recent call last):
>> > >>>>>>>>>
>> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313,
>> in <module>
>> > >>>>>>>>>
>> > >>>>>>>>> main()
>> > >>>>>>>>>
>> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294,
>> in main
>> > >>>>>>>>>
>> > >>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
>> > >>>>>>>>>
>> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in
>> prepare
>> > >>>>>>>>>
>> > >>>>>>>>> checkDOAPfiles(version)
>> > >>>>>>>>>
>> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
>> > >>>>>>>>> checkDOAPfiles
>> > >>>>>>>>>
>> > >>>>>>>>> distpage = load(url)
>> > >>>>>>>>>
>> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in
>> load
>> > >>>>>>>>>
>> > >>>>>>>>> content = urllib.request.urlopen(urlStri
>> ng).read().decode('utf-8')
>> > >>>>>>>>>
>> > >>>>>>>>> File
>> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> > >>>>>>>>> line 223, in urlopen
>> > >>>>>>>>>
>> > >>>>>>>>> return opener.open(url, data, timeout)
>> > >>>>>>>>>
>> > >>>>>>>>> File
>> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> > >>>>>>>>> line 526, in open
>> > >>>>>>>>>
>> > >>>>>>>>> response = self._open(req, data)
>> > >>>>>>>>>
>> > >>>>>>>>> File
>> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> > >>>>>>>>> line 544, in _open
>> > >>>>>>>>>
>> > >>>>>>>>> '_open', req)
>> > >>>>>>>>>
>> > >>>>>>>>> File
>> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> > >>>>>>>>> line 504, in _call_chain
>> > >>>>>>>>>
>> > >>>>>>>>> result = func(*args)
>> > >>>>>>>>>
>> > >>>>>>>>> File
>> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> > >>>>>>>>> line 1361, in https_open
>> > >>>>>>>>>
>> > >>>>>>>>> context=self._context, check_hostname=self._check_hostname)
>> > >>>>>>>>>
>> > >>>>>>>>> File
>> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> > >>>>>>>>> line 1320, in do_open
>> > >>>>>>>>>
>> > >>>>>>>>> raise URLError(err)
>> > >>>>>>>>>
>> > >>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
>> CERTIFICATE_VERIFY_FAILED]
>> > >>>>>>>>> certificate verify failed (_ssl.c:749)>
>> > >>>>>>>>>
>> > >>>>>>>>>
>> > >>>>>>>>>
>> > >>>>>>>>>
>> > >>>>>>>>> Joel Bernstein
>> > >>>>>>>>> http://joelsolr.blogspot.com/
>> > >>>>>>>>>
>> > >>>>>>>>
>> > >>>>>>>>
>> > >>>>>>>> ------------------------------------------------------------
>> ---------
>> > >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > >>>>>>>>
>> > >>>>>>>
>> > >>>>>>
>> > >>>>>> ------------------------------------------------------------
>> ---------
>> > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>
>> > >>>>>
>> > >>>>> ------------------------------------------------------------
>> ---------
>> > >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > >>>>>
>> > >>>>>
>> > >>>>>
>> > >>>>>
>> > >>>>
>> > >>>>
>> > >>>> ------------------------------------------------------------
>> ---------
>> > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
>> > >>>>
>> > >>>>
>> > >>>
>> > >>
>> > >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > For additional commands, e-mail: dev-help@lucene.apache.org
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
Smoke testes passed as well
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 9:21 AM, Steve Rowe <sa...@gmail.com> wrote:
> I guess precommit is only run as part of the smoke tester.
>
> > On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > Interesting the entire release process completed without complaining.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> > The unused import was the only problem; I’ve removed it on branch_6_5.
> >
> > Sorry, hope I didn’t cause a delay in the release process.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> > >
> > > Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I
> forgot to run precommit. Doing so now.
> > >
> > > --
> > > Steve
> > > www.lucidworks.com
> > >
> > >> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>
> > >> Done.
> > >>
> > >> --
> > >> Steve
> > >> www.lucidworks.com
> > >>
> > >>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>>
> > >>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> > >>>
> > >>> --
> > >>> Steve
> > >>> www.lucidworks.com
> > >>>
> > >>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>>>
> > >>>> I'm OK with restarting RC2. Let me know when you finish the back
> port.
> > >>>>
> > >>>> Joel Bernstein
> > >>>> http://joelsolr.blogspot.com/
> > >>>>
> > >>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>>> Joel,
> > >>>>
> > >>>> I know you’re in-process with RC2, but if you have to restart for
> some reason, I’d like to include SOLR-10527.
> > >>>>
> > >>>> --
> > >>>> Steve
> > >>>> www.lucidworks.com
> > >>>>
> > >>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>>>>
> > >>>>> I also had to change the smoke tester because of the SSL issue.
> Which in theory means everyone else will have to as well. I'm pushing out
> my changes to branch_6_5, so people can just update their branch before
> running the smoke tester.
> > >>>>>
> > >>>>> Joel Bernstein
> > >>>>> http://joelsolr.blogspot.com/
> > >>>>>
> > >>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>> Ok, I had to push out three changes to the branch but I seemed to
> have moved passed this issue.
> > >>>>>
> > >>>>> Joel Bernstein
> > >>>>> http://joelsolr.blogspot.com/
> > >>>>>
> > >>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>> I'll push out the changes and then revert. Hopefully the changes
> will do the trick after they've been pushed.
> > >>>>>
> > >>>>> Joel Bernstein
> > >>>>> http://joelsolr.blogspot.com/
> > >>>>>
> > >>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>>>> Yeah, that is a sucky part of this: you want to make modifications
> on the release branch, but you can’t test unless you commit (and push).
> > >>>>>
> > >>>>> Another alternative: make modifications in another checkout, then
> invoke the script with from an unmodified source tree.
> > >>>>>
> > >>>>> e.g.:
> > >>>>>
> > >>>>> cd ..
> > >>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your
> checkout dir
> > >>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > >>>>> cd lucene-solr
> > >>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> …
> > >>>>>
> > >>>>> (a shorter form of that is to make a copy the script alone and
> invoke the modified version from your checkout)
> > >>>>>
> > >>>>> --
> > >>>>> Steve
> > >>>>> www.lucidworks.com
> > >>>>>
> > >>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>>>>>
> > >>>>>> Ha, that doesn't work either. Now I get this error:
> > >>>>>>
> > >>>>>> RuntimeError: There are unpushed commits - "git log
> origin/branch_6_5.." output is:
> > >>>>>>
> > >>>>>> So, I'm going to have to push this out.
> > >>>>>>
> > >>>>>> Let's first decide if this makes sense as the way forward.
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> Joel Bernstein
> > >>>>>> http://joelsolr.blogspot.com/
> > >>>>>>
> > >>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>> Steve, when I change the script to turn off verification I get
> the following error:
> > >>>>>> RuntimeError: git clone is dirty:
> > >>>>>>
> > >>>>>> So as part of the work around I think I'm going to have to commit
> locally and then revert locally. Does that make sense to you as the way
> forward?
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> Joel Bernstein
> > >>>>>> http://joelsolr.blogspot.com/
> > >>>>>>
> > >>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
> arafalov@gmail.com> wrote:
> > >>>>>> Could it be anything to do with the fact that the signer is
> Semantic
> > >>>>>> and they are being actively distrusted by - at least - Google:
> > >>>>>> http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> > >>>>>>
> > >>>>>> Regards,
> > >>>>>> Alex.
> > >>>>>> ----
> > >>>>>> http://www.solr-start.com/ - Resources for Solr users, new and
> experienced
> > >>>>>>
> > >>>>>>
> > >>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert
> verification
> > >>>>>>> was something that was integral to the process.
> > >>>>>>>
> > >>>>>>> Joel Bernstein
> > >>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>
> > >>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > >>>>>>>>
> > >>>>>>>> Hi Joel,
> > >>>>>>>>
> > >>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> > >>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has
> been enabled on
> > >>>>>>>> archive.apache.org?
> > >>>>>>>>
> > >>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
> alternative to
> > >>>>>>>> urllib):
> > >>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#
> what-are-hostname-doesn-t-match-errors>
> > >>>>>>>>
> > >>>>>>>> Short term, you could turn off certificate verification. The
> bottom
> > >>>>>>>> answer here uses the same lib as the script (urllib instead of
> urllib2,
> > >>>>>>>> which is assumed in the other answers on the page), to turn off
> certificate
> > >>>>>>>> verification:
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> > >>>>>>>>
> > >>>>>>>> --
> > >>>>>>>> Steve
> > >>>>>>>> www.lucidworks.com
> > >>>>>>>>
> > >>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <
> joelsolr@gmail.com> wrote:
> > >>>>>>>>>
> > >>>>>>>>> It appears that it's failing on verifying the SSL cert for
> > >>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> Joel Bernstein
> > >>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>
> > >>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
> joelsolr@gmail.com>
> > >>>>>>>>> wrote:
> > >>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> > >>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py
> --push-local
> > >>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > >>>>>>>>>
> > >>>>>>>>> I believe this is same basic command I used for RC1. But this
> time I got
> > >>>>>>>>> a new error. At first I thought it might be incorrect keystore
> password but
> > >>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
> > >>>>>>>>>
> > >>>>>>>>> Traceback (most recent call last):
> > >>>>>>>>>
> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in
> <module>
> > >>>>>>>>>
> > >>>>>>>>> main()
> > >>>>>>>>>
> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in
> main
> > >>>>>>>>>
> > >>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > >>>>>>>>>
> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in
> prepare
> > >>>>>>>>>
> > >>>>>>>>> checkDOAPfiles(version)
> > >>>>>>>>>
> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> > >>>>>>>>> checkDOAPfiles
> > >>>>>>>>>
> > >>>>>>>>> distpage = load(url)
> > >>>>>>>>>
> > >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in
> load
> > >>>>>>>>>
> > >>>>>>>>> content = urllib.request.urlopen(
> urlString).read().decode('utf-8')
> > >>>>>>>>>
> > >>>>>>>>> File
> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>> line 223, in urlopen
> > >>>>>>>>>
> > >>>>>>>>> return opener.open(url, data, timeout)
> > >>>>>>>>>
> > >>>>>>>>> File
> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>> line 526, in open
> > >>>>>>>>>
> > >>>>>>>>> response = self._open(req, data)
> > >>>>>>>>>
> > >>>>>>>>> File
> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>> line 544, in _open
> > >>>>>>>>>
> > >>>>>>>>> '_open', req)
> > >>>>>>>>>
> > >>>>>>>>> File
> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>> line 504, in _call_chain
> > >>>>>>>>>
> > >>>>>>>>> result = func(*args)
> > >>>>>>>>>
> > >>>>>>>>> File
> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>> line 1361, in https_open
> > >>>>>>>>>
> > >>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> > >>>>>>>>>
> > >>>>>>>>> File
> > >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >>>>>>>>> line 1320, in do_open
> > >>>>>>>>>
> > >>>>>>>>> raise URLError(err)
> > >>>>>>>>>
> > >>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> > >>>>>>>>> certificate verify failed (_ssl.c:749)>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> Joel Bernstein
> > >>>>>>>>> http://joelsolr.blogspot.com/
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> ------------------------------------------------------------
> ---------
> > >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>> ------------------------------------------------------------
> ---------
> > >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>> ------------------------------------------------------------
> ---------
> > >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>> ------------------------------------------------------------
> ---------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>>>
> > >>>>
> > >>>
> > >>
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
I guess precommit is only run as part of the smoke tester.
> On Apr 20, 2017, at 9:20 AM, Joel Bernstein <jo...@gmail.com> wrote:
>
> Interesting the entire release process completed without complaining.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> The unused import was the only problem; I’ve removed it on branch_6_5.
>
> Sorry, hope I didn’t cause a delay in the release process.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> >
> > Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> >> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>
> >> Done.
> >>
> >> --
> >> Steve
> >> www.lucidworks.com
> >>
> >>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>
> >>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> >>>
> >>> --
> >>> Steve
> >>> www.lucidworks.com
> >>>
> >>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>
> >>>> I'm OK with restarting RC2. Let me know when you finish the back port.
> >>>>
> >>>> Joel Bernstein
> >>>> http://joelsolr.blogspot.com/
> >>>>
> >>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>> Joel,
> >>>>
> >>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
> >>>>
> >>>> --
> >>>> Steve
> >>>> www.lucidworks.com
> >>>>
> >>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>
> >>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
> >>>>>
> >>>>> Joel Bernstein
> >>>>> http://joelsolr.blogspot.com/
> >>>>>
> >>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
> >>>>>
> >>>>> Joel Bernstein
> >>>>> http://joelsolr.blogspot.com/
> >>>>>
> >>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
> >>>>>
> >>>>> Joel Bernstein
> >>>>> http://joelsolr.blogspot.com/
> >>>>>
> >>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
> >>>>>
> >>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
> >>>>>
> >>>>> e.g.:
> >>>>>
> >>>>> cd ..
> >>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> >>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> >>>>> cd lucene-solr
> >>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
> >>>>>
> >>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
> >>>>>
> >>>>> --
> >>>>> Steve
> >>>>> www.lucidworks.com
> >>>>>
> >>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>
> >>>>>> Ha, that doesn't work either. Now I get this error:
> >>>>>>
> >>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
> >>>>>>
> >>>>>> So, I'm going to have to push this out.
> >>>>>>
> >>>>>> Let's first decide if this makes sense as the way forward.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Joel Bernstein
> >>>>>> http://joelsolr.blogspot.com/
> >>>>>>
> >>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>> Steve, when I change the script to turn off verification I get the following error:
> >>>>>> RuntimeError: git clone is dirty:
> >>>>>>
> >>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Joel Bernstein
> >>>>>> http://joelsolr.blogspot.com/
> >>>>>>
> >>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> >>>>>> Could it be anything to do with the fact that the signer is Semantic
> >>>>>> and they are being actively distrusted by - at least - Google:
> >>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
> >>>>>>
> >>>>>> Regards,
> >>>>>> Alex.
> >>>>>> ----
> >>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
> >>>>>>
> >>>>>>
> >>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> >>>>>>> was something that was integral to the process.
> >>>>>>>
> >>>>>>> Joel Bernstein
> >>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>
> >>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> Hi Joel,
> >>>>>>>>
> >>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> >>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> >>>>>>>> archive.apache.org?
> >>>>>>>>
> >>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
> >>>>>>>> urllib):
> >>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> >>>>>>>>
> >>>>>>>> Short term, you could turn off certificate verification. The bottom
> >>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
> >>>>>>>> which is assumed in the other answers on the page), to turn off certificate
> >>>>>>>> verification:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Steve
> >>>>>>>> www.lucidworks.com
> >>>>>>>>
> >>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>> It appears that it's failing on verifying the SSL cert for
> >>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Joel Bernstein
> >>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>
> >>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> >>>>>>>>> wrote:
> >>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> >>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> >>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> >>>>>>>>>
> >>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
> >>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
> >>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
> >>>>>>>>>
> >>>>>>>>> Traceback (most recent call last):
> >>>>>>>>>
> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> >>>>>>>>>
> >>>>>>>>> main()
> >>>>>>>>>
> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> >>>>>>>>>
> >>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> >>>>>>>>>
> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> >>>>>>>>>
> >>>>>>>>> checkDOAPfiles(version)
> >>>>>>>>>
> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> >>>>>>>>> checkDOAPfiles
> >>>>>>>>>
> >>>>>>>>> distpage = load(url)
> >>>>>>>>>
> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> >>>>>>>>>
> >>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
> >>>>>>>>>
> >>>>>>>>> File
> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>> line 223, in urlopen
> >>>>>>>>>
> >>>>>>>>> return opener.open(url, data, timeout)
> >>>>>>>>>
> >>>>>>>>> File
> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>> line 526, in open
> >>>>>>>>>
> >>>>>>>>> response = self._open(req, data)
> >>>>>>>>>
> >>>>>>>>> File
> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>> line 544, in _open
> >>>>>>>>>
> >>>>>>>>> '_open', req)
> >>>>>>>>>
> >>>>>>>>> File
> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>> line 504, in _call_chain
> >>>>>>>>>
> >>>>>>>>> result = func(*args)
> >>>>>>>>>
> >>>>>>>>> File
> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>> line 1361, in https_open
> >>>>>>>>>
> >>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> >>>>>>>>>
> >>>>>>>>> File
> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >>>>>>>>> line 1320, in do_open
> >>>>>>>>>
> >>>>>>>>> raise URLError(err)
> >>>>>>>>>
> >>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> >>>>>>>>> certificate verify failed (_ssl.c:749)>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Joel Bernstein
> >>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> ---------------------------------------------------------------------
> >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>
> >>>>
> >>>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
Interesting the entire release process completed without complaining.
Joel Bernstein
http://joelsolr.blogspot.com/
On Thu, Apr 20, 2017 at 9:10 AM, Steve Rowe <sa...@gmail.com> wrote:
> The unused import was the only problem; I’ve removed it on branch_6_5.
>
> Sorry, hope I didn’t cause a delay in the release process.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
> >
> > Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I
> forgot to run precommit. Doing so now.
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> >> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>
> >> Done.
> >>
> >> --
> >> Steve
> >> www.lucidworks.com
> >>
> >>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>
> >>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
> >>>
> >>> --
> >>> Steve
> >>> www.lucidworks.com
> >>>
> >>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>
> >>>> I'm OK with restarting RC2. Let me know when you finish the back port.
> >>>>
> >>>> Joel Bernstein
> >>>> http://joelsolr.blogspot.com/
> >>>>
> >>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>>> Joel,
> >>>>
> >>>> I know you’re in-process with RC2, but if you have to restart for
> some reason, I’d like to include SOLR-10527.
> >>>>
> >>>> --
> >>>> Steve
> >>>> www.lucidworks.com
> >>>>
> >>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>
> >>>>> I also had to change the smoke tester because of the SSL issue.
> Which in theory means everyone else will have to as well. I'm pushing out
> my changes to branch_6_5, so people can just update their branch before
> running the smoke tester.
> >>>>>
> >>>>> Joel Bernstein
> >>>>> http://joelsolr.blogspot.com/
> >>>>>
> >>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>> Ok, I had to push out three changes to the branch but I seemed to
> have moved passed this issue.
> >>>>>
> >>>>> Joel Bernstein
> >>>>> http://joelsolr.blogspot.com/
> >>>>>
> >>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>> I'll push out the changes and then revert. Hopefully the changes
> will do the trick after they've been pushed.
> >>>>>
> >>>>> Joel Bernstein
> >>>>> http://joelsolr.blogspot.com/
> >>>>>
> >>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>> Yeah, that is a sucky part of this: you want to make modifications
> on the release branch, but you can’t test unless you commit (and push).
> >>>>>
> >>>>> Another alternative: make modifications in another checkout, then
> invoke the script with from an unmodified source tree.
> >>>>>
> >>>>> e.g.:
> >>>>>
> >>>>> cd ..
> >>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your
> checkout dir
> >>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> >>>>> cd lucene-solr
> >>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> …
> >>>>>
> >>>>> (a shorter form of that is to make a copy the script alone and
> invoke the modified version from your checkout)
> >>>>>
> >>>>> --
> >>>>> Steve
> >>>>> www.lucidworks.com
> >>>>>
> >>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>>
> >>>>>> Ha, that doesn't work either. Now I get this error:
> >>>>>>
> >>>>>> RuntimeError: There are unpushed commits - "git log
> origin/branch_6_5.." output is:
> >>>>>>
> >>>>>> So, I'm going to have to push this out.
> >>>>>>
> >>>>>> Let's first decide if this makes sense as the way forward.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Joel Bernstein
> >>>>>> http://joelsolr.blogspot.com/
> >>>>>>
> >>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>> Steve, when I change the script to turn off verification I get the
> following error:
> >>>>>> RuntimeError: git clone is dirty:
> >>>>>>
> >>>>>> So as part of the work around I think I'm going to have to commit
> locally and then revert locally. Does that make sense to you as the way
> forward?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Joel Bernstein
> >>>>>> http://joelsolr.blogspot.com/
> >>>>>>
> >>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
> arafalov@gmail.com> wrote:
> >>>>>> Could it be anything to do with the fact that the signer is Semantic
> >>>>>> and they are being actively distrusted by - at least - Google:
> >>>>>> http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> >>>>>>
> >>>>>> Regards,
> >>>>>> Alex.
> >>>>>> ----
> >>>>>> http://www.solr-start.com/ - Resources for Solr users, new and
> experienced
> >>>>>>
> >>>>>>
> >>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert
> verification
> >>>>>>> was something that was integral to the process.
> >>>>>>>
> >>>>>>> Joel Bernstein
> >>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>
> >>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> >>>>>>>>
> >>>>>>>> Hi Joel,
> >>>>>>>>
> >>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
> >>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been
> enabled on
> >>>>>>>> archive.apache.org?
> >>>>>>>>
> >>>>>>>> Some useful info here (about a “requests” lib, AFAICT an
> alternative to
> >>>>>>>> urllib):
> >>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#
> what-are-hostname-doesn-t-match-errors>
> >>>>>>>>
> >>>>>>>> Short term, you could turn off certificate verification. The
> bottom
> >>>>>>>> answer here uses the same lib as the script (urllib instead of
> urllib2,
> >>>>>>>> which is assumed in the other answers on the page), to turn off
> certificate
> >>>>>>>> verification:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Steve
> >>>>>>>> www.lucidworks.com
> >>>>>>>>
> >>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >>>>>>>>>
> >>>>>>>>> It appears that it's failing on verifying the SSL cert for
> >>>>>>>>> https://archive.apache.org/dist/lucene/java/.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Joel Bernstein
> >>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>
> >>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
> joelsolr@gmail.com>
> >>>>>>>>> wrote:
> >>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
> >>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> >>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> >>>>>>>>>
> >>>>>>>>> I believe this is same basic command I used for RC1. But this
> time I got
> >>>>>>>>> a new error. At first I thought it might be incorrect keystore
> password but
> >>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
> >>>>>>>>>
> >>>>>>>>> Traceback (most recent call last):
> >>>>>>>>>
> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in
> <module>
> >>>>>>>>>
> >>>>>>>>> main()
> >>>>>>>>>
> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in
> main
> >>>>>>>>>
> >>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
> >>>>>>>>>
> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in
> prepare
> >>>>>>>>>
> >>>>>>>>> checkDOAPfiles(version)
> >>>>>>>>>
> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> >>>>>>>>> checkDOAPfiles
> >>>>>>>>>
> >>>>>>>>> distpage = load(url)
> >>>>>>>>>
> >>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in
> load
> >>>>>>>>>
> >>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-
> 8')
> >>>>>>>>>
> >>>>>>>>> File
> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>> line 223, in urlopen
> >>>>>>>>>
> >>>>>>>>> return opener.open(url, data, timeout)
> >>>>>>>>>
> >>>>>>>>> File
> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>> line 526, in open
> >>>>>>>>>
> >>>>>>>>> response = self._open(req, data)
> >>>>>>>>>
> >>>>>>>>> File
> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>> line 544, in _open
> >>>>>>>>>
> >>>>>>>>> '_open', req)
> >>>>>>>>>
> >>>>>>>>> File
> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>> line 504, in _call_chain
> >>>>>>>>>
> >>>>>>>>> result = func(*args)
> >>>>>>>>>
> >>>>>>>>> File
> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>> line 1361, in https_open
> >>>>>>>>>
> >>>>>>>>> context=self._context, check_hostname=self._check_hostname)
> >>>>>>>>>
> >>>>>>>>> File
> >>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >>>>>>>>> line 1320, in do_open
> >>>>>>>>>
> >>>>>>>>> raise URLError(err)
> >>>>>>>>>
> >>>>>>>>> urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> >>>>>>>>> certificate verify failed (_ssl.c:749)>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Joel Bernstein
> >>>>>>>>> http://joelsolr.blogspot.com/
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> ------------------------------------------------------------
> ---------
> >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> ------------------------------------------------------------
> ---------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------------------------------------
> ---------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>>> For additional commands, e-mail: dev-help@lucene.apache.org
> >>>>
> >>>>
> >>>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
The unused import was the only problem; I’ve removed it on branch_6_5.
Sorry, hope I didn’t cause a delay in the release process.
--
Steve
www.lucidworks.com
> On Apr 20, 2017, at 8:57 AM, Steve Rowe <sa...@gmail.com> wrote:
>
> Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
>
> --
> Steve
> www.lucidworks.com
>
>> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
>>
>> Done.
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>
>>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>>>
>>> --
>>> Steve
>>> www.lucidworks.com
>>>
>>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>
>>>> I'm OK with restarting RC2. Let me know when you finish the back port.
>>>>
>>>> Joel Bernstein
>>>> http://joelsolr.blogspot.com/
>>>>
>>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>> Joel,
>>>>
>>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
>>>>
>>>> --
>>>> Steve
>>>> www.lucidworks.com
>>>>
>>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>
>>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
>>>>>
>>>>> Joel Bernstein
>>>>> http://joelsolr.blogspot.com/
>>>>>
>>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
>>>>>
>>>>> Joel Bernstein
>>>>> http://joelsolr.blogspot.com/
>>>>>
>>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
>>>>>
>>>>> Joel Bernstein
>>>>> http://joelsolr.blogspot.com/
>>>>>
>>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
>>>>>
>>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
>>>>>
>>>>> e.g.:
>>>>>
>>>>> cd ..
>>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
>>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>>>> cd lucene-solr
>>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
>>>>>
>>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
>>>>>
>>>>> --
>>>>> Steve
>>>>> www.lucidworks.com
>>>>>
>>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>
>>>>>> Ha, that doesn't work either. Now I get this error:
>>>>>>
>>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
>>>>>>
>>>>>> So, I'm going to have to push this out.
>>>>>>
>>>>>> Let's first decide if this makes sense as the way forward.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Joel Bernstein
>>>>>> http://joelsolr.blogspot.com/
>>>>>>
>>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>> Steve, when I change the script to turn off verification I get the following error:
>>>>>> RuntimeError: git clone is dirty:
>>>>>>
>>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Joel Bernstein
>>>>>> http://joelsolr.blogspot.com/
>>>>>>
>>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
>>>>>> Could it be anything to do with the fact that the signer is Semantic
>>>>>> and they are being actively distrusted by - at least - Google:
>>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
>>>>>>
>>>>>> Regards,
>>>>>> Alex.
>>>>>> ----
>>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
>>>>>>
>>>>>>
>>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
>>>>>>> was something that was integral to the process.
>>>>>>>
>>>>>>> Joel Bernstein
>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>
>>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> Hi Joel,
>>>>>>>>
>>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
>>>>>>>> archive.apache.org?
>>>>>>>>
>>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
>>>>>>>> urllib):
>>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>>>>>>>
>>>>>>>> Short term, you could turn off certificate verification. The bottom
>>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
>>>>>>>> which is assumed in the other answers on the page), to turn off certificate
>>>>>>>> verification:
>>>>>>>>
>>>>>>>>
>>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Steve
>>>>>>>> www.lucidworks.com
>>>>>>>>
>>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> It appears that it's failing on verifying the SSL cert for
>>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Joel Bernstein
>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>
>>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
>>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>>>>>>>>
>>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
>>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
>>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
>>>>>>>>>
>>>>>>>>> Traceback (most recent call last):
>>>>>>>>>
>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
>>>>>>>>>
>>>>>>>>> main()
>>>>>>>>>
>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
>>>>>>>>>
>>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
>>>>>>>>>
>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
>>>>>>>>>
>>>>>>>>> checkDOAPfiles(version)
>>>>>>>>>
>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
>>>>>>>>> checkDOAPfiles
>>>>>>>>>
>>>>>>>>> distpage = load(url)
>>>>>>>>>
>>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
>>>>>>>>>
>>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
>>>>>>>>>
>>>>>>>>> File
>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>> line 223, in urlopen
>>>>>>>>>
>>>>>>>>> return opener.open(url, data, timeout)
>>>>>>>>>
>>>>>>>>> File
>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>> line 526, in open
>>>>>>>>>
>>>>>>>>> response = self._open(req, data)
>>>>>>>>>
>>>>>>>>> File
>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>> line 544, in _open
>>>>>>>>>
>>>>>>>>> '_open', req)
>>>>>>>>>
>>>>>>>>> File
>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>> line 504, in _call_chain
>>>>>>>>>
>>>>>>>>> result = func(*args)
>>>>>>>>>
>>>>>>>>> File
>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>> line 1361, in https_open
>>>>>>>>>
>>>>>>>>> context=self._context, check_hostname=self._check_hostname)
>>>>>>>>>
>>>>>>>>> File
>>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>>> line 1320, in do_open
>>>>>>>>>
>>>>>>>>> raise URLError(err)
>>>>>>>>>
>>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
>>>>>>>>> certificate verify failed (_ssl.c:749)>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Joel Bernstein
>>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
Crap, Jenkins found an unused import in my commit on branch_6_5 :(. I forgot to run precommit. Doing so now.
--
Steve
www.lucidworks.com
> On Apr 19, 2017, at 8:07 PM, Steve Rowe <sa...@gmail.com> wrote:
>
> Done.
>
> --
> Steve
> www.lucidworks.com
>
>> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
>>
>> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>
>>> I'm OK with restarting RC2. Let me know when you finish the back port.
>>>
>>> Joel Bernstein
>>> http://joelsolr.blogspot.com/
>>>
>>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
>>> Joel,
>>>
>>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
>>>
>>> --
>>> Steve
>>> www.lucidworks.com
>>>
>>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>
>>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
>>>>
>>>> Joel Bernstein
>>>> http://joelsolr.blogspot.com/
>>>>
>>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
>>>>
>>>> Joel Bernstein
>>>> http://joelsolr.blogspot.com/
>>>>
>>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
>>>>
>>>> Joel Bernstein
>>>> http://joelsolr.blogspot.com/
>>>>
>>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
>>>>
>>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
>>>>
>>>> e.g.:
>>>>
>>>> cd ..
>>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
>>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>>> cd lucene-solr
>>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
>>>>
>>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
>>>>
>>>> --
>>>> Steve
>>>> www.lucidworks.com
>>>>
>>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>
>>>>> Ha, that doesn't work either. Now I get this error:
>>>>>
>>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
>>>>>
>>>>> So, I'm going to have to push this out.
>>>>>
>>>>> Let's first decide if this makes sense as the way forward.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Joel Bernstein
>>>>> http://joelsolr.blogspot.com/
>>>>>
>>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>> Steve, when I change the script to turn off verification I get the following error:
>>>>> RuntimeError: git clone is dirty:
>>>>>
>>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Joel Bernstein
>>>>> http://joelsolr.blogspot.com/
>>>>>
>>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
>>>>> Could it be anything to do with the fact that the signer is Semantic
>>>>> and they are being actively distrusted by - at least - Google:
>>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
>>>>>
>>>>> Regards,
>>>>> Alex.
>>>>> ----
>>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
>>>>>
>>>>>
>>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
>>>>>> was something that was integral to the process.
>>>>>>
>>>>>> Joel Bernstein
>>>>>> http://joelsolr.blogspot.com/
>>>>>>
>>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>>
>>>>>>> Hi Joel,
>>>>>>>
>>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
>>>>>>> archive.apache.org?
>>>>>>>
>>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
>>>>>>> urllib):
>>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>>>>>>
>>>>>>> Short term, you could turn off certificate verification. The bottom
>>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
>>>>>>> which is assumed in the other answers on the page), to turn off certificate
>>>>>>> verification:
>>>>>>>
>>>>>>>
>>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
>>>>>>>
>>>>>>> --
>>>>>>> Steve
>>>>>>> www.lucidworks.com
>>>>>>>
>>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> It appears that it's failing on verifying the SSL cert for
>>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Joel Bernstein
>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>
>>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
>>>>>>>> wrote:
>>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
>>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>>>>>>>
>>>>>>>> I believe this is same basic command I used for RC1. But this time I got
>>>>>>>> a new error. At first I thought it might be incorrect keystore password but
>>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
>>>>>>>>
>>>>>>>> Traceback (most recent call last):
>>>>>>>>
>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
>>>>>>>>
>>>>>>>> main()
>>>>>>>>
>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
>>>>>>>>
>>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
>>>>>>>>
>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
>>>>>>>>
>>>>>>>> checkDOAPfiles(version)
>>>>>>>>
>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
>>>>>>>> checkDOAPfiles
>>>>>>>>
>>>>>>>> distpage = load(url)
>>>>>>>>
>>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
>>>>>>>>
>>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
>>>>>>>>
>>>>>>>> File
>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>> line 223, in urlopen
>>>>>>>>
>>>>>>>> return opener.open(url, data, timeout)
>>>>>>>>
>>>>>>>> File
>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>> line 526, in open
>>>>>>>>
>>>>>>>> response = self._open(req, data)
>>>>>>>>
>>>>>>>> File
>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>> line 544, in _open
>>>>>>>>
>>>>>>>> '_open', req)
>>>>>>>>
>>>>>>>> File
>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>> line 504, in _call_chain
>>>>>>>>
>>>>>>>> result = func(*args)
>>>>>>>>
>>>>>>>> File
>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>> line 1361, in https_open
>>>>>>>>
>>>>>>>> context=self._context, check_hostname=self._check_hostname)
>>>>>>>>
>>>>>>>> File
>>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>>> line 1320, in do_open
>>>>>>>>
>>>>>>>> raise URLError(err)
>>>>>>>>
>>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
>>>>>>>> certificate verify failed (_ssl.c:749)>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Joel Bernstein
>>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
Done.
--
Steve
www.lucidworks.com
> On Apr 19, 2017, at 7:49 PM, Steve Rowe <sa...@gmail.com> wrote:
>
> Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
>
> --
> Steve
> www.lucidworks.com
>
>> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>
>> I'm OK with restarting RC2. Let me know when you finish the back port.
>>
>> Joel Bernstein
>> http://joelsolr.blogspot.com/
>>
>> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
>> Joel,
>>
>> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>>> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>
>>> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
>>>
>>> Joel Bernstein
>>> http://joelsolr.blogspot.com/
>>>
>>> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
>>>
>>> Joel Bernstein
>>> http://joelsolr.blogspot.com/
>>>
>>> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
>>>
>>> Joel Bernstein
>>> http://joelsolr.blogspot.com/
>>>
>>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
>>> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
>>>
>>> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
>>>
>>> e.g.:
>>>
>>> cd ..
>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>> cd lucene-solr
>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
>>>
>>> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
>>>
>>> --
>>> Steve
>>> www.lucidworks.com
>>>
>>>> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>
>>>> Ha, that doesn't work either. Now I get this error:
>>>>
>>>> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
>>>>
>>>> So, I'm going to have to push this out.
>>>>
>>>> Let's first decide if this makes sense as the way forward.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Joel Bernstein
>>>> http://joelsolr.blogspot.com/
>>>>
>>>> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>> Steve, when I change the script to turn off verification I get the following error:
>>>> RuntimeError: git clone is dirty:
>>>>
>>>> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Joel Bernstein
>>>> http://joelsolr.blogspot.com/
>>>>
>>>> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
>>>> Could it be anything to do with the fact that the signer is Semantic
>>>> and they are being actively distrusted by - at least - Google:
>>>> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
>>>>
>>>> Regards,
>>>> Alex.
>>>> ----
>>>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
>>>>
>>>>
>>>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
>>>>> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
>>>>> was something that was integral to the process.
>>>>>
>>>>> Joel Bernstein
>>>>> http://joelsolr.blogspot.com/
>>>>>
>>>>> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
>>>>>>
>>>>>> Hi Joel,
>>>>>>
>>>>>> Not sure why this is suddenly an issue - I guess “SNI”
>>>>>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
>>>>>> archive.apache.org?
>>>>>>
>>>>>> Some useful info here (about a “requests” lib, AFAICT an alternative to
>>>>>> urllib):
>>>>>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>>>>>
>>>>>> Short term, you could turn off certificate verification. The bottom
>>>>>> answer here uses the same lib as the script (urllib instead of urllib2,
>>>>>> which is assumed in the other answers on the page), to turn off certificate
>>>>>> verification:
>>>>>>
>>>>>>
>>>>>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
>>>>>>
>>>>>> --
>>>>>> Steve
>>>>>> www.lucidworks.com
>>>>>>
>>>>>>> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
>>>>>>>
>>>>>>> It appears that it's failing on verifying the SSL cert for
>>>>>>> https://archive.apache.org/dist/lucene/java/.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Joel Bernstein
>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>
>>>>>>> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
>>>>>>> wrote:
>>>>>>> I started working on 6.5.1 RC2. I ran the following:
>>>>>>> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
>>>>>>> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>>>>>>
>>>>>>> I believe this is same basic command I used for RC1. But this time I got
>>>>>>> a new error. At first I thought it might be incorrect keystore password but
>>>>>>> I changed it and it is correct. Any thoughts what the issue is?
>>>>>>>
>>>>>>> Traceback (most recent call last):
>>>>>>>
>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
>>>>>>>
>>>>>>> main()
>>>>>>>
>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
>>>>>>>
>>>>>>> rev = prepare(c.root, c.version, c.key_id, c.key_password)
>>>>>>>
>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
>>>>>>>
>>>>>>> checkDOAPfiles(version)
>>>>>>>
>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
>>>>>>> checkDOAPfiles
>>>>>>>
>>>>>>> distpage = load(url)
>>>>>>>
>>>>>>> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
>>>>>>>
>>>>>>> content = urllib.request.urlopen(urlString).read().decode('utf-8')
>>>>>>>
>>>>>>> File
>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>> line 223, in urlopen
>>>>>>>
>>>>>>> return opener.open(url, data, timeout)
>>>>>>>
>>>>>>> File
>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>> line 526, in open
>>>>>>>
>>>>>>> response = self._open(req, data)
>>>>>>>
>>>>>>> File
>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>> line 544, in _open
>>>>>>>
>>>>>>> '_open', req)
>>>>>>>
>>>>>>> File
>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>> line 504, in _call_chain
>>>>>>>
>>>>>>> result = func(*args)
>>>>>>>
>>>>>>> File
>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>> line 1361, in https_open
>>>>>>>
>>>>>>> context=self._context, check_hostname=self._check_hostname)
>>>>>>>
>>>>>>> File
>>>>>>> "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>>>>>>> line 1320, in do_open
>>>>>>>
>>>>>>> raise URLError(err)
>>>>>>>
>>>>>>> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
>>>>>>> certificate verify failed (_ssl.c:749)>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Joel Bernstein
>>>>>>> http://joelsolr.blogspot.com/
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
Woohoo! Thanks Joel. Running all tests on branch_6_5 now.
--
Steve
www.lucidworks.com
> On Apr 19, 2017, at 7:20 PM, Joel Bernstein <jo...@gmail.com> wrote:
>
> I'm OK with restarting RC2. Let me know when you finish the back port.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> Joel,
>
> I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> > Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
> >
> > Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
> >
> > e.g.:
> >
> > cd ..
> > cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> > # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > cd lucene-solr
> > python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
> >
> > (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >
> > > Ha, that doesn't work either. Now I get this error:
> > >
> > > RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
> > >
> > > So, I'm going to have to push this out.
> > >
> > > Let's first decide if this makes sense as the way forward.
> > >
> > >
> > >
> > >
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > Steve, when I change the script to turn off verification I get the following error:
> > > RuntimeError: git clone is dirty:
> > >
> > > So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
> > >
> > >
> > >
> > >
> > >
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> > > Could it be anything to do with the fact that the signer is Semantic
> > > and they are being actively distrusted by - at least - Google:
> > > http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
> > >
> > > Regards,
> > > Alex.
> > > ----
> > > http://www.solr-start.com/ - Resources for Solr users, new and experienced
> > >
> > >
> > > On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > > > Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> > > > was something that was integral to the process.
> > > >
> > > > Joel Bernstein
> > > > http://joelsolr.blogspot.com/
> > > >
> > > > On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> > > >>
> > > >> Hi Joel,
> > > >>
> > > >> Not sure why this is suddenly an issue - I guess “SNI”
> > > >> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> > > >> archive.apache.org?
> > > >>
> > > >> Some useful info here (about a “requests” lib, AFAICT an alternative to
> > > >> urllib):
> > > >> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> > > >>
> > > >> Short term, you could turn off certificate verification. The bottom
> > > >> answer here uses the same lib as the script (urllib instead of urllib2,
> > > >> which is assumed in the other answers on the page), to turn off certificate
> > > >> verification:
> > > >>
> > > >>
> > > >> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> > > >>
> > > >> --
> > > >> Steve
> > > >> www.lucidworks.com
> > > >>
> > > >> > On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > > >> >
> > > >> > It appears that it's failing on verifying the SSL cert for
> > > >> > https://archive.apache.org/dist/lucene/java/.
> > > >> >
> > > >> >
> > > >> >
> > > >> > Joel Bernstein
> > > >> > http://joelsolr.blogspot.com/
> > > >> >
> > > >> > On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> > > >> > wrote:
> > > >> > I started working on 6.5.1 RC2. I ran the following:
> > > >> > python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> > > >> > /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > > >> >
> > > >> > I believe this is same basic command I used for RC1. But this time I got
> > > >> > a new error. At first I thought it might be incorrect keystore password but
> > > >> > I changed it and it is correct. Any thoughts what the issue is?
> > > >> >
> > > >> > Traceback (most recent call last):
> > > >> >
> > > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> > > >> >
> > > >> > main()
> > > >> >
> > > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> > > >> >
> > > >> > rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > > >> >
> > > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> > > >> >
> > > >> > checkDOAPfiles(version)
> > > >> >
> > > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> > > >> > checkDOAPfiles
> > > >> >
> > > >> > distpage = load(url)
> > > >> >
> > > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> > > >> >
> > > >> > content = urllib.request.urlopen(urlString).read().decode('utf-8')
> > > >> >
> > > >> > File
> > > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >> > line 223, in urlopen
> > > >> >
> > > >> > return opener.open(url, data, timeout)
> > > >> >
> > > >> > File
> > > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >> > line 526, in open
> > > >> >
> > > >> > response = self._open(req, data)
> > > >> >
> > > >> > File
> > > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >> > line 544, in _open
> > > >> >
> > > >> > '_open', req)
> > > >> >
> > > >> > File
> > > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >> > line 504, in _call_chain
> > > >> >
> > > >> > result = func(*args)
> > > >> >
> > > >> > File
> > > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >> > line 1361, in https_open
> > > >> >
> > > >> > context=self._context, check_hostname=self._check_hostname)
> > > >> >
> > > >> > File
> > > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > > >> > line 1320, in do_open
> > > >> >
> > > >> > raise URLError(err)
> > > >> >
> > > >> > urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> > > >> > certificate verify failed (_ssl.c:749)>
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > Joel Bernstein
> > > >> > http://joelsolr.blogspot.com/
> > > >> >
> > > >>
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: dev-help@lucene.apache.org
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
I'm OK with restarting RC2. Let me know when you finish the back port.
Joel Bernstein
http://joelsolr.blogspot.com/
On Wed, Apr 19, 2017 at 7:11 PM, Steve Rowe <sa...@gmail.com> wrote:
> Joel,
>
> I know you’re in-process with RC2, but if you have to restart for some
> reason, I’d like to include SOLR-10527.
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > I also had to change the smoke tester because of the SSL issue. Which in
> theory means everyone else will have to as well. I'm pushing out my changes
> to branch_6_5, so people can just update their branch before running the
> smoke tester.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > Ok, I had to push out three changes to the branch but I seemed to have
> moved passed this issue.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > I'll push out the changes and then revert. Hopefully the changes will do
> the trick after they've been pushed.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> > Yeah, that is a sucky part of this: you want to make modifications on
> the release branch, but you can’t test unless you commit (and push).
> >
> > Another alternative: make modifications in another checkout, then invoke
> the script with from an unmodified source tree.
> >
> > e.g.:
> >
> > cd ..
> > cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout
> dir
> > # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> > cd lucene-solr
> > python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
> >
> > (a shorter form of that is to make a copy the script alone and invoke
> the modified version from your checkout)
> >
> > --
> > Steve
> > www.lucidworks.com
> >
> > > On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >
> > > Ha, that doesn't work either. Now I get this error:
> > >
> > > RuntimeError: There are unpushed commits - "git log
> origin/branch_6_5.." output is:
> > >
> > > So, I'm going to have to push this out.
> > >
> > > Let's first decide if this makes sense as the way forward.
> > >
> > >
> > >
> > >
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > Steve, when I change the script to turn off verification I get the
> following error:
> > > RuntimeError: git clone is dirty:
> > >
> > > So as part of the work around I think I'm going to have to commit
> locally and then revert locally. Does that make sense to you as the way
> forward?
> > >
> > >
> > >
> > >
> > >
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
> arafalov@gmail.com> wrote:
> > > Could it be anything to do with the fact that the signer is Semantic
> > > and they are being actively distrusted by - at least - Google:
> > > http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> > >
> > > Regards,
> > > Alex.
> > > ----
> > > http://www.solr-start.com/ - Resources for Solr users, new and
> experienced
> > >
> > >
> > > On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > > > Ok, I'll turn off the cert verification. I wasn't sure if cert
> verification
> > > > was something that was integral to the process.
> > > >
> > > > Joel Bernstein
> > > > http://joelsolr.blogspot.com/
> > > >
> > > > On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com>
> wrote:
> > > >>
> > > >> Hi Joel,
> > > >>
> > > >> Not sure why this is suddenly an issue - I guess “SNI”
> > > >> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been
> enabled on
> > > >> archive.apache.org?
> > > >>
> > > >> Some useful info here (about a “requests” lib, AFAICT an
> alternative to
> > > >> urllib):
> > > >> <http://docs.python-requests.org/en/master/community/faq/#
> what-are-hostname-doesn-t-match-errors>
> > > >>
> > > >> Short term, you could turn off certificate verification. The bottom
> > > >> answer here uses the same lib as the script (urllib instead of
> urllib2,
> > > >> which is assumed in the other answers on the page), to turn off
> certificate
> > > >> verification:
> > > >>
> > > >>
> > > >> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> > > >>
> > > >> --
> > > >> Steve
> > > >> www.lucidworks.com
> > > >>
> > > >> > On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > > >> >
> > > >> > It appears that it's failing on verifying the SSL cert for
> > > >> > https://archive.apache.org/dist/lucene/java/.
> > > >> >
> > > >> >
> > > >> >
> > > >> > Joel Bernstein
> > > >> > http://joelsolr.blogspot.com/
> > > >> >
> > > >> > On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
> joelsolr@gmail.com>
> > > >> > wrote:
> > > >> > I started working on 6.5.1 RC2. I ran the following:
> > > >> > python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> > > >> > /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > > >> >
> > > >> > I believe this is same basic command I used for RC1. But this
> time I got
> > > >> > a new error. At first I thought it might be incorrect keystore
> password but
> > > >> > I changed it and it is correct. Any thoughts what the issue is?
> > > >> >
> > > >> > Traceback (most recent call last):
> > > >> >
> > > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 313, in
> <module>
> > > >> >
> > > >> > main()
> > > >> >
> > > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 294, in
> main
> > > >> >
> > > >> > rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > > >> >
> > > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 98, in
> prepare
> > > >> >
> > > >> > checkDOAPfiles(version)
> > > >> >
> > > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> > > >> > checkDOAPfiles
> > > >> >
> > > >> > distpage = load(url)
> > > >> >
> > > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 67, in
> load
> > > >> >
> > > >> > content = urllib.request.urlopen(
> urlString).read().decode('utf-8')
> > > >> >
> > > >> > File
> > > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >> > line 223, in urlopen
> > > >> >
> > > >> > return opener.open(url, data, timeout)
> > > >> >
> > > >> > File
> > > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >> > line 526, in open
> > > >> >
> > > >> > response = self._open(req, data)
> > > >> >
> > > >> > File
> > > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >> > line 544, in _open
> > > >> >
> > > >> > '_open', req)
> > > >> >
> > > >> > File
> > > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >> > line 504, in _call_chain
> > > >> >
> > > >> > result = func(*args)
> > > >> >
> > > >> > File
> > > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >> > line 1361, in https_open
> > > >> >
> > > >> > context=self._context, check_hostname=self._check_hostname)
> > > >> >
> > > >> > File
> > > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > > >> > line 1320, in do_open
> > > >> >
> > > >> > raise URLError(err)
> > > >> >
> > > >> > urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> > > >> > certificate verify failed (_ssl.c:749)>
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > Joel Bernstein
> > > >> > http://joelsolr.blogspot.com/
> > > >> >
> > > >>
> > > >>
> > > >> ------------------------------------------------------------
> ---------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > > >>
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: dev-help@lucene.apache.org
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
Joel,
I know you’re in-process with RC2, but if you have to restart for some reason, I’d like to include SOLR-10527.
--
Steve
www.lucidworks.com
> On Apr 19, 2017, at 6:57 PM, Joel Bernstein <jo...@gmail.com> wrote:
>
> I also had to change the smoke tester because of the SSL issue. Which in theory means everyone else will have to as well. I'm pushing out my changes to branch_6_5, so people can just update their branch before running the smoke tester.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> Ok, I had to push out three changes to the branch but I seemed to have moved passed this issue.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> I'll push out the changes and then revert. Hopefully the changes will do the trick after they've been pushed.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
>
> Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
>
> e.g.:
>
> cd ..
> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> cd lucene-solr
> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
>
> (a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > Ha, that doesn't work either. Now I get this error:
> >
> > RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
> >
> > So, I'm going to have to push this out.
> >
> > Let's first decide if this makes sense as the way forward.
> >
> >
> >
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > Steve, when I change the script to turn off verification I get the following error:
> > RuntimeError: git clone is dirty:
> >
> > So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
> >
> >
> >
> >
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> > Could it be anything to do with the fact that the signer is Semantic
> > and they are being actively distrusted by - at least - Google:
> > http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
> >
> > Regards,
> > Alex.
> > ----
> > http://www.solr-start.com/ - Resources for Solr users, new and experienced
> >
> >
> > On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > > Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> > > was something that was integral to the process.
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>
> > >> Hi Joel,
> > >>
> > >> Not sure why this is suddenly an issue - I guess “SNI”
> > >> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> > >> archive.apache.org?
> > >>
> > >> Some useful info here (about a “requests” lib, AFAICT an alternative to
> > >> urllib):
> > >> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> > >>
> > >> Short term, you could turn off certificate verification. The bottom
> > >> answer here uses the same lib as the script (urllib instead of urllib2,
> > >> which is assumed in the other answers on the page), to turn off certificate
> > >> verification:
> > >>
> > >>
> > >> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> > >>
> > >> --
> > >> Steve
> > >> www.lucidworks.com
> > >>
> > >> > On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> > >> >
> > >> > It appears that it's failing on verifying the SSL cert for
> > >> > https://archive.apache.org/dist/lucene/java/.
> > >> >
> > >> >
> > >> >
> > >> > Joel Bernstein
> > >> > http://joelsolr.blogspot.com/
> > >> >
> > >> > On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> > >> > wrote:
> > >> > I started working on 6.5.1 RC2. I ran the following:
> > >> > python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> > >> > /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > >> >
> > >> > I believe this is same basic command I used for RC1. But this time I got
> > >> > a new error. At first I thought it might be incorrect keystore password but
> > >> > I changed it and it is correct. Any thoughts what the issue is?
> > >> >
> > >> > Traceback (most recent call last):
> > >> >
> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> > >> >
> > >> > main()
> > >> >
> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> > >> >
> > >> > rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > >> >
> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> > >> >
> > >> > checkDOAPfiles(version)
> > >> >
> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> > >> > checkDOAPfiles
> > >> >
> > >> > distpage = load(url)
> > >> >
> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> > >> >
> > >> > content = urllib.request.urlopen(urlString).read().decode('utf-8')
> > >> >
> > >> > File
> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >> > line 223, in urlopen
> > >> >
> > >> > return opener.open(url, data, timeout)
> > >> >
> > >> > File
> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >> > line 526, in open
> > >> >
> > >> > response = self._open(req, data)
> > >> >
> > >> > File
> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >> > line 544, in _open
> > >> >
> > >> > '_open', req)
> > >> >
> > >> > File
> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >> > line 504, in _call_chain
> > >> >
> > >> > result = func(*args)
> > >> >
> > >> > File
> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >> > line 1361, in https_open
> > >> >
> > >> > context=self._context, check_hostname=self._check_hostname)
> > >> >
> > >> > File
> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> > >> > line 1320, in do_open
> > >> >
> > >> > raise URLError(err)
> > >> >
> > >> > urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> > >> > certificate verify failed (_ssl.c:749)>
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > Joel Bernstein
> > >> > http://joelsolr.blogspot.com/
> > >> >
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
I also had to change the smoke tester because of the SSL issue. Which in
theory means everyone else will have to as well. I'm pushing out my changes
to branch_6_5, so people can just update their branch before running the
smoke tester.
Joel Bernstein
http://joelsolr.blogspot.com/
On Wed, Apr 19, 2017 at 5:02 PM, Joel Bernstein <jo...@gmail.com> wrote:
> Ok, I had to push out three changes to the branch but I seemed to have
> moved passed this issue.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
>
>> I'll push out the changes and then revert. Hopefully the changes will do
>> the trick after they've been pushed.
>>
>> Joel Bernstein
>> http://joelsolr.blogspot.com/
>>
>> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
>>
>>> Yeah, that is a sucky part of this: you want to make modifications on
>>> the release branch, but you can’t test unless you commit (and push).
>>>
>>> Another alternative: make modifications in another checkout, then invoke
>>> the script with from an unmodified source tree.
>>>
>>> e.g.:
>>>
>>> cd ..
>>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout
>>> dir
>>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>>> cd lucene-solr
>>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
>>>
>>> (a shorter form of that is to make a copy the script alone and invoke
>>> the modified version from your checkout)
>>>
>>> --
>>> Steve
>>> www.lucidworks.com
>>>
>>> > On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> >
>>> > Ha, that doesn't work either. Now I get this error:
>>> >
>>> > RuntimeError: There are unpushed commits - "git log
>>> origin/branch_6_5.." output is:
>>> >
>>> > So, I'm going to have to push this out.
>>> >
>>> > Let's first decide if this makes sense as the way forward.
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Joel Bernstein
>>> > http://joelsolr.blogspot.com/
>>> >
>>> > On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> > Steve, when I change the script to turn off verification I get the
>>> following error:
>>> > RuntimeError: git clone is dirty:
>>> >
>>> > So as part of the work around I think I'm going to have to commit
>>> locally and then revert locally. Does that make sense to you as the way
>>> forward?
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Joel Bernstein
>>> > http://joelsolr.blogspot.com/
>>> >
>>> > On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>>> arafalov@gmail.com> wrote:
>>> > Could it be anything to do with the fact that the signer is Semantic
>>> > and they are being actively distrusted by - at least - Google:
>>> > http://www.securityweek.com/google-stops-trusting-symantec-i
>>> ssued-certificates
>>> >
>>> > Regards,
>>> > Alex.
>>> > ----
>>> > http://www.solr-start.com/ - Resources for Solr users, new and
>>> experienced
>>> >
>>> >
>>> > On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
>>> > > Ok, I'll turn off the cert verification. I wasn't sure if cert
>>> verification
>>> > > was something that was integral to the process.
>>> > >
>>> > > Joel Bernstein
>>> > > http://joelsolr.blogspot.com/
>>> > >
>>> > > On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com>
>>> wrote:
>>> > >>
>>> > >> Hi Joel,
>>> > >>
>>> > >> Not sure why this is suddenly an issue - I guess “SNI”
>>> > >> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been
>>> enabled on
>>> > >> archive.apache.org?
>>> > >>
>>> > >> Some useful info here (about a “requests” lib, AFAICT an
>>> alternative to
>>> > >> urllib):
>>> > >> <http://docs.python-requests.org/en/master/community/faq/#wh
>>> at-are-hostname-doesn-t-match-errors>
>>> > >>
>>> > >> Short term, you could turn off certificate verification. The bottom
>>> > >> answer here uses the same lib as the script (urllib instead of
>>> urllib2,
>>> > >> which is assumed in the other answers on the page), to turn off
>>> certificate
>>> > >> verification:
>>> > >>
>>> > >>
>>> > >> <http://stackoverflow.com/questions/19268548/python-ignore-c
>>> erticate-validation-urllib2>
>>> > >>
>>> > >> --
>>> > >> Steve
>>> > >> www.lucidworks.com
>>> > >>
>>> > >> > On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com>
>>> wrote:
>>> > >> >
>>> > >> > It appears that it's failing on verifying the SSL cert for
>>> > >> > https://archive.apache.org/dist/lucene/java/.
>>> > >> >
>>> > >> >
>>> > >> >
>>> > >> > Joel Bernstein
>>> > >> > http://joelsolr.blogspot.com/
>>> > >> >
>>> > >> > On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>>> joelsolr@gmail.com>
>>> > >> > wrote:
>>> > >> > I started working on 6.5.1 RC2. I ran the following:
>>> > >> > python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
>>> > >> > /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>>> > >> >
>>> > >> > I believe this is same basic command I used for RC1. But this
>>> time I got
>>> > >> > a new error. At first I thought it might be incorrect keystore
>>> password but
>>> > >> > I changed it and it is correct. Any thoughts what the issue is?
>>> > >> >
>>> > >> > Traceback (most recent call last):
>>> > >> >
>>> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 313, in
>>> <module>
>>> > >> >
>>> > >> > main()
>>> > >> >
>>> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 294, in
>>> main
>>> > >> >
>>> > >> > rev = prepare(c.root, c.version, c.key_id, c.key_password)
>>> > >> >
>>> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 98, in
>>> prepare
>>> > >> >
>>> > >> > checkDOAPfiles(version)
>>> > >> >
>>> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
>>> > >> > checkDOAPfiles
>>> > >> >
>>> > >> > distpage = load(url)
>>> > >> >
>>> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 67, in
>>> load
>>> > >> >
>>> > >> > content = urllib.request.urlopen(urlStri
>>> ng).read().decode('utf-8')
>>> > >> >
>>> > >> > File
>>> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>>> n3.6/urllib/request.py",
>>> > >> > line 223, in urlopen
>>> > >> >
>>> > >> > return opener.open(url, data, timeout)
>>> > >> >
>>> > >> > File
>>> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>>> n3.6/urllib/request.py",
>>> > >> > line 526, in open
>>> > >> >
>>> > >> > response = self._open(req, data)
>>> > >> >
>>> > >> > File
>>> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>>> n3.6/urllib/request.py",
>>> > >> > line 544, in _open
>>> > >> >
>>> > >> > '_open', req)
>>> > >> >
>>> > >> > File
>>> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>>> n3.6/urllib/request.py",
>>> > >> > line 504, in _call_chain
>>> > >> >
>>> > >> > result = func(*args)
>>> > >> >
>>> > >> > File
>>> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>>> n3.6/urllib/request.py",
>>> > >> > line 1361, in https_open
>>> > >> >
>>> > >> > context=self._context, check_hostname=self._check_hostname)
>>> > >> >
>>> > >> > File
>>> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>>> n3.6/urllib/request.py",
>>> > >> > line 1320, in do_open
>>> > >> >
>>> > >> > raise URLError(err)
>>> > >> >
>>> > >> > urllib.error.URLError: <urlopen error [SSL:
>>> CERTIFICATE_VERIFY_FAILED]
>>> > >> > certificate verify failed (_ssl.c:749)>
>>> > >> >
>>> > >> >
>>> > >> >
>>> > >> >
>>> > >> > Joel Bernstein
>>> > >> > http://joelsolr.blogspot.com/
>>> > >> >
>>> > >>
>>> > >>
>>> > >> ------------------------------------------------------------
>>> ---------
>>> > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> > >> For additional commands, e-mail: dev-help@lucene.apache.org
>>> > >>
>>> > >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> > For additional commands, e-mail: dev-help@lucene.apache.org
>>> >
>>> >
>>> >
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
Ok, I had to push out three changes to the branch but I seemed to have
moved passed this issue.
Joel Bernstein
http://joelsolr.blogspot.com/
On Wed, Apr 19, 2017 at 4:50 PM, Joel Bernstein <jo...@gmail.com> wrote:
> I'll push out the changes and then revert. Hopefully the changes will do
> the trick after they've been pushed.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
>
>> Yeah, that is a sucky part of this: you want to make modifications on the
>> release branch, but you can’t test unless you commit (and push).
>>
>> Another alternative: make modifications in another checkout, then invoke
>> the script with from an unmodified source tree.
>>
>> e.g.:
>>
>> cd ..
>> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout
>> dir
>> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
>> cd lucene-solr
>> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
>>
>> (a shorter form of that is to make a copy the script alone and invoke the
>> modified version from your checkout)
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>> > On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
>> >
>> > Ha, that doesn't work either. Now I get this error:
>> >
>> > RuntimeError: There are unpushed commits - "git log
>> origin/branch_6_5.." output is:
>> >
>> > So, I'm going to have to push this out.
>> >
>> > Let's first decide if this makes sense as the way forward.
>> >
>> >
>> >
>> >
>> >
>> > Joel Bernstein
>> > http://joelsolr.blogspot.com/
>> >
>> > On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > Steve, when I change the script to turn off verification I get the
>> following error:
>> > RuntimeError: git clone is dirty:
>> >
>> > So as part of the work around I think I'm going to have to commit
>> locally and then revert locally. Does that make sense to you as the way
>> forward?
>> >
>> >
>> >
>> >
>> >
>> >
>> > Joel Bernstein
>> > http://joelsolr.blogspot.com/
>> >
>> > On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
>> arafalov@gmail.com> wrote:
>> > Could it be anything to do with the fact that the signer is Semantic
>> > and they are being actively distrusted by - at least - Google:
>> > http://www.securityweek.com/google-stops-trusting-symantec-
>> issued-certificates
>> >
>> > Regards,
>> > Alex.
>> > ----
>> > http://www.solr-start.com/ - Resources for Solr users, new and
>> experienced
>> >
>> >
>> > On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
>> > > Ok, I'll turn off the cert verification. I wasn't sure if cert
>> verification
>> > > was something that was integral to the process.
>> > >
>> > > Joel Bernstein
>> > > http://joelsolr.blogspot.com/
>> > >
>> > > On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
>> > >>
>> > >> Hi Joel,
>> > >>
>> > >> Not sure why this is suddenly an issue - I guess “SNI”
>> > >> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been
>> enabled on
>> > >> archive.apache.org?
>> > >>
>> > >> Some useful info here (about a “requests” lib, AFAICT an alternative
>> to
>> > >> urllib):
>> > >> <http://docs.python-requests.org/en/master/community/faq/#wh
>> at-are-hostname-doesn-t-match-errors>
>> > >>
>> > >> Short term, you could turn off certificate verification. The bottom
>> > >> answer here uses the same lib as the script (urllib instead of
>> urllib2,
>> > >> which is assumed in the other answers on the page), to turn off
>> certificate
>> > >> verification:
>> > >>
>> > >>
>> > >> <http://stackoverflow.com/questions/19268548/python-ignore-
>> certicate-validation-urllib2>
>> > >>
>> > >> --
>> > >> Steve
>> > >> www.lucidworks.com
>> > >>
>> > >> > On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> > >> >
>> > >> > It appears that it's failing on verifying the SSL cert for
>> > >> > https://archive.apache.org/dist/lucene/java/.
>> > >> >
>> > >> >
>> > >> >
>> > >> > Joel Bernstein
>> > >> > http://joelsolr.blogspot.com/
>> > >> >
>> > >> > On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <
>> joelsolr@gmail.com>
>> > >> > wrote:
>> > >> > I started working on 6.5.1 RC2. I ran the following:
>> > >> > python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
>> > >> > /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>> > >> >
>> > >> > I believe this is same basic command I used for RC1. But this time
>> I got
>> > >> > a new error. At first I thought it might be incorrect keystore
>> password but
>> > >> > I changed it and it is correct. Any thoughts what the issue is?
>> > >> >
>> > >> > Traceback (most recent call last):
>> > >> >
>> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 313, in
>> <module>
>> > >> >
>> > >> > main()
>> > >> >
>> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 294, in
>> main
>> > >> >
>> > >> > rev = prepare(c.root, c.version, c.key_id, c.key_password)
>> > >> >
>> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 98, in
>> prepare
>> > >> >
>> > >> > checkDOAPfiles(version)
>> > >> >
>> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
>> > >> > checkDOAPfiles
>> > >> >
>> > >> > distpage = load(url)
>> > >> >
>> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 67, in
>> load
>> > >> >
>> > >> > content = urllib.request.urlopen(urlStri
>> ng).read().decode('utf-8')
>> > >> >
>> > >> > File
>> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> > >> > line 223, in urlopen
>> > >> >
>> > >> > return opener.open(url, data, timeout)
>> > >> >
>> > >> > File
>> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> > >> > line 526, in open
>> > >> >
>> > >> > response = self._open(req, data)
>> > >> >
>> > >> > File
>> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> > >> > line 544, in _open
>> > >> >
>> > >> > '_open', req)
>> > >> >
>> > >> > File
>> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> > >> > line 504, in _call_chain
>> > >> >
>> > >> > result = func(*args)
>> > >> >
>> > >> > File
>> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> > >> > line 1361, in https_open
>> > >> >
>> > >> > context=self._context, check_hostname=self._check_hostname)
>> > >> >
>> > >> > File
>> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> > >> > line 1320, in do_open
>> > >> >
>> > >> > raise URLError(err)
>> > >> >
>> > >> > urllib.error.URLError: <urlopen error [SSL:
>> CERTIFICATE_VERIFY_FAILED]
>> > >> > certificate verify failed (_ssl.c:749)>
>> > >> >
>> > >> >
>> > >> >
>> > >> >
>> > >> > Joel Bernstein
>> > >> > http://joelsolr.blogspot.com/
>> > >> >
>> > >>
>> > >>
>> > >> ------------------------------------------------------------
>> ---------
>> > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > >> For additional commands, e-mail: dev-help@lucene.apache.org
>> > >>
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > For additional commands, e-mail: dev-help@lucene.apache.org
>> >
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
I'll push out the changes and then revert. Hopefully the changes will do
the trick after they've been pushed.
Joel Bernstein
http://joelsolr.blogspot.com/
On Wed, Apr 19, 2017 at 4:37 PM, Steve Rowe <sa...@gmail.com> wrote:
> Yeah, that is a sucky part of this: you want to make modifications on the
> release branch, but you can’t test unless you commit (and push).
>
> Another alternative: make modifications in another checkout, then invoke
> the script with from an unmodified source tree.
>
> e.g.:
>
> cd ..
> cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
> # edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
> cd lucene-solr
> python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
>
> (a shorter form of that is to make a copy the script alone and invoke the
> modified version from your checkout)
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > Ha, that doesn't work either. Now I get this error:
> >
> > RuntimeError: There are unpushed commits - "git log origin/branch_6_5.."
> output is:
> >
> > So, I'm going to have to push this out.
> >
> > Let's first decide if this makes sense as the way forward.
> >
> >
> >
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > Steve, when I change the script to turn off verification I get the
> following error:
> > RuntimeError: git clone is dirty:
> >
> > So as part of the work around I think I'm going to have to commit
> locally and then revert locally. Does that make sense to you as the way
> forward?
> >
> >
> >
> >
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <
> arafalov@gmail.com> wrote:
> > Could it be anything to do with the fact that the signer is Semantic
> > and they are being actively distrusted by - at least - Google:
> > http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
> >
> > Regards,
> > Alex.
> > ----
> > http://www.solr-start.com/ - Resources for Solr users, new and
> experienced
> >
> >
> > On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > > Ok, I'll turn off the cert verification. I wasn't sure if cert
> verification
> > > was something that was integral to the process.
> > >
> > > Joel Bernstein
> > > http://joelsolr.blogspot.com/
> > >
> > > On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> > >>
> > >> Hi Joel,
> > >>
> > >> Not sure why this is suddenly an issue - I guess “SNI”
> > >> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been
> enabled on
> > >> archive.apache.org?
> > >>
> > >> Some useful info here (about a “requests” lib, AFAICT an alternative
> to
> > >> urllib):
> > >> <http://docs.python-requests.org/en/master/community/faq/#
> what-are-hostname-doesn-t-match-errors>
> > >>
> > >> Short term, you could turn off certificate verification. The bottom
> > >> answer here uses the same lib as the script (urllib instead of
> urllib2,
> > >> which is assumed in the other answers on the page), to turn off
> certificate
> > >> verification:
> > >>
> > >>
> > >> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> > >>
> > >> --
> > >> Steve
> > >> www.lucidworks.com
> > >>
> > >> > On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > >> >
> > >> > It appears that it's failing on verifying the SSL cert for
> > >> > https://archive.apache.org/dist/lucene/java/.
> > >> >
> > >> >
> > >> >
> > >> > Joel Bernstein
> > >> > http://joelsolr.blogspot.com/
> > >> >
> > >> > On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <joelsolr@gmail.com
> >
> > >> > wrote:
> > >> > I started working on 6.5.1 RC2. I ran the following:
> > >> > python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> > >> > /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> > >> >
> > >> > I believe this is same basic command I used for RC1. But this time
> I got
> > >> > a new error. At first I thought it might be incorrect keystore
> password but
> > >> > I changed it and it is correct. Any thoughts what the issue is?
> > >> >
> > >> > Traceback (most recent call last):
> > >> >
> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 313, in
> <module>
> > >> >
> > >> > main()
> > >> >
> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 294, in
> main
> > >> >
> > >> > rev = prepare(c.root, c.version, c.key_id, c.key_password)
> > >> >
> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 98, in
> prepare
> > >> >
> > >> > checkDOAPfiles(version)
> > >> >
> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> > >> > checkDOAPfiles
> > >> >
> > >> > distpage = load(url)
> > >> >
> > >> > File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> > >> >
> > >> > content = urllib.request.urlopen(urlString).read().decode('utf-
> 8')
> > >> >
> > >> > File
> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >> > line 223, in urlopen
> > >> >
> > >> > return opener.open(url, data, timeout)
> > >> >
> > >> > File
> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >> > line 526, in open
> > >> >
> > >> > response = self._open(req, data)
> > >> >
> > >> > File
> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >> > line 544, in _open
> > >> >
> > >> > '_open', req)
> > >> >
> > >> > File
> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >> > line 504, in _call_chain
> > >> >
> > >> > result = func(*args)
> > >> >
> > >> > File
> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >> > line 1361, in https_open
> > >> >
> > >> > context=self._context, check_hostname=self._check_hostname)
> > >> >
> > >> > File
> > >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> > >> > line 1320, in do_open
> > >> >
> > >> > raise URLError(err)
> > >> >
> > >> > urllib.error.URLError: <urlopen error [SSL:
> CERTIFICATE_VERIFY_FAILED]
> > >> > certificate verify failed (_ssl.c:749)>
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > Joel Bernstein
> > >> > http://joelsolr.blogspot.com/
> > >> >
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > >> For additional commands, e-mail: dev-help@lucene.apache.org
> > >>
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
Yeah, that is a sucky part of this: you want to make modifications on the release branch, but you can’t test unless you commit (and push).
Another alternative: make modifications in another checkout, then invoke the script with from an unmodified source tree.
e.g.:
cd ..
cp -r lucene-solr lucene-solr-2 # assuming lucene-solr is your checkout dir
# edit lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py
cd lucene-solr
python3 -u ../lucene-solr-2/dev-tools/scripts/buildAndPushRelease.py …
(a shorter form of that is to make a copy the script alone and invoke the modified version from your checkout)
--
Steve
www.lucidworks.com
> On Apr 19, 2017, at 4:32 PM, Joel Bernstein <jo...@gmail.com> wrote:
>
> Ha, that doesn't work either. Now I get this error:
>
> RuntimeError: There are unpushed commits - "git log origin/branch_6_5.." output is:
>
> So, I'm going to have to push this out.
>
> Let's first decide if this makes sense as the way forward.
>
>
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> Steve, when I change the script to turn off verification I get the following error:
> RuntimeError: git clone is dirty:
>
> So as part of the work around I think I'm going to have to commit locally and then revert locally. Does that make sense to you as the way forward?
>
>
>
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com> wrote:
> Could it be anything to do with the fact that the signer is Semantic
> and they are being actively distrusted by - at least - Google:
> http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
>
> Regards,
> Alex.
> ----
> http://www.solr-start.com/ - Resources for Solr users, new and experienced
>
>
> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> > was something that was integral to the process.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>
> >> Hi Joel,
> >>
> >> Not sure why this is suddenly an issue - I guess “SNI”
> >> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> >> archive.apache.org?
> >>
> >> Some useful info here (about a “requests” lib, AFAICT an alternative to
> >> urllib):
> >> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
> >>
> >> Short term, you could turn off certificate verification. The bottom
> >> answer here uses the same lib as the script (urllib instead of urllib2,
> >> which is assumed in the other answers on the page), to turn off certificate
> >> verification:
> >>
> >>
> >> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
> >>
> >> --
> >> Steve
> >> www.lucidworks.com
> >>
> >> > On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >> >
> >> > It appears that it's failing on verifying the SSL cert for
> >> > https://archive.apache.org/dist/lucene/java/.
> >> >
> >> >
> >> >
> >> > Joel Bernstein
> >> > http://joelsolr.blogspot.com/
> >> >
> >> > On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> >> > wrote:
> >> > I started working on 6.5.1 RC2. I ran the following:
> >> > python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> >> > /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> >> >
> >> > I believe this is same basic command I used for RC1. But this time I got
> >> > a new error. At first I thought it might be incorrect keystore password but
> >> > I changed it and it is correct. Any thoughts what the issue is?
> >> >
> >> > Traceback (most recent call last):
> >> >
> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> >> >
> >> > main()
> >> >
> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> >> >
> >> > rev = prepare(c.root, c.version, c.key_id, c.key_password)
> >> >
> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> >> >
> >> > checkDOAPfiles(version)
> >> >
> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> >> > checkDOAPfiles
> >> >
> >> > distpage = load(url)
> >> >
> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> >> >
> >> > content = urllib.request.urlopen(urlString).read().decode('utf-8')
> >> >
> >> > File
> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >> > line 223, in urlopen
> >> >
> >> > return opener.open(url, data, timeout)
> >> >
> >> > File
> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >> > line 526, in open
> >> >
> >> > response = self._open(req, data)
> >> >
> >> > File
> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >> > line 544, in _open
> >> >
> >> > '_open', req)
> >> >
> >> > File
> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >> > line 504, in _call_chain
> >> >
> >> > result = func(*args)
> >> >
> >> > File
> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >> > line 1361, in https_open
> >> >
> >> > context=self._context, check_hostname=self._check_hostname)
> >> >
> >> > File
> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> >> > line 1320, in do_open
> >> >
> >> > raise URLError(err)
> >> >
> >> > urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> >> > certificate verify failed (_ssl.c:749)>
> >> >
> >> >
> >> >
> >> >
> >> > Joel Bernstein
> >> > http://joelsolr.blogspot.com/
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: dev-help@lucene.apache.org
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
Ha, that doesn't work either. Now I get this error:
RuntimeError: There are unpushed commits - "git log origin/branch_6_5.."
output is:
So, I'm going to have to push this out.
Let's first decide if this makes sense as the way forward.
Joel Bernstein
http://joelsolr.blogspot.com/
On Wed, Apr 19, 2017 at 4:28 PM, Joel Bernstein <jo...@gmail.com> wrote:
> Steve, when I change the script to turn off verification I get the
> following error:
>
> RuntimeError: git clone is dirty:
>
> So as part of the work around I think I'm going to have to commit locally
> and then revert locally. Does that make sense to you as the way forward?
>
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <arafalov@gmail.com
> > wrote:
>
>> Could it be anything to do with the fact that the signer is Semantic
>> and they are being actively distrusted by - at least - Google:
>> http://www.securityweek.com/google-stops-trusting-symantec-
>> issued-certificates
>>
>> Regards,
>> Alex.
>> ----
>> http://www.solr-start.com/ - Resources for Solr users, new and
>> experienced
>>
>>
>> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
>> > Ok, I'll turn off the cert verification. I wasn't sure if cert
>> verification
>> > was something that was integral to the process.
>> >
>> > Joel Bernstein
>> > http://joelsolr.blogspot.com/
>> >
>> > On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
>> >>
>> >> Hi Joel,
>> >>
>> >> Not sure why this is suddenly an issue - I guess “SNI”
>> >> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been
>> enabled on
>> >> archive.apache.org?
>> >>
>> >> Some useful info here (about a “requests” lib, AFAICT an alternative to
>> >> urllib):
>> >> <http://docs.python-requests.org/en/master/community/faq/#wh
>> at-are-hostname-doesn-t-match-errors>
>> >>
>> >> Short term, you could turn off certificate verification. The bottom
>> >> answer here uses the same lib as the script (urllib instead of urllib2,
>> >> which is assumed in the other answers on the page), to turn off
>> certificate
>> >> verification:
>> >>
>> >>
>> >> <http://stackoverflow.com/questions/19268548/python-ignore-
>> certicate-validation-urllib2>
>> >>
>> >> --
>> >> Steve
>> >> www.lucidworks.com
>> >>
>> >> > On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com>
>> wrote:
>> >> >
>> >> > It appears that it's failing on verifying the SSL cert for
>> >> > https://archive.apache.org/dist/lucene/java/.
>> >> >
>> >> >
>> >> >
>> >> > Joel Bernstein
>> >> > http://joelsolr.blogspot.com/
>> >> >
>> >> > On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
>> >> > wrote:
>> >> > I started working on 6.5.1 RC2. I ran the following:
>> >> > python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
>> >> > /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>> >> >
>> >> > I believe this is same basic command I used for RC1. But this time I
>> got
>> >> > a new error. At first I thought it might be incorrect keystore
>> password but
>> >> > I changed it and it is correct. Any thoughts what the issue is?
>> >> >
>> >> > Traceback (most recent call last):
>> >> >
>> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 313, in
>> <module>
>> >> >
>> >> > main()
>> >> >
>> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
>> >> >
>> >> > rev = prepare(c.root, c.version, c.key_id, c.key_password)
>> >> >
>> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 98, in
>> prepare
>> >> >
>> >> > checkDOAPfiles(version)
>> >> >
>> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
>> >> > checkDOAPfiles
>> >> >
>> >> > distpage = load(url)
>> >> >
>> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
>> >> >
>> >> > content = urllib.request.urlopen(urlStri
>> ng).read().decode('utf-8')
>> >> >
>> >> > File
>> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> >> > line 223, in urlopen
>> >> >
>> >> > return opener.open(url, data, timeout)
>> >> >
>> >> > File
>> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> >> > line 526, in open
>> >> >
>> >> > response = self._open(req, data)
>> >> >
>> >> > File
>> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> >> > line 544, in _open
>> >> >
>> >> > '_open', req)
>> >> >
>> >> > File
>> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> >> > line 504, in _call_chain
>> >> >
>> >> > result = func(*args)
>> >> >
>> >> > File
>> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> >> > line 1361, in https_open
>> >> >
>> >> > context=self._context, check_hostname=self._check_hostname)
>> >> >
>> >> > File
>> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/pytho
>> n3.6/urllib/request.py",
>> >> > line 1320, in do_open
>> >> >
>> >> > raise URLError(err)
>> >> >
>> >> > urllib.error.URLError: <urlopen error [SSL:
>> CERTIFICATE_VERIFY_FAILED]
>> >> > certificate verify failed (_ssl.c:749)>
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > Joel Bernstein
>> >> > http://joelsolr.blogspot.com/
>> >> >
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> >> For additional commands, e-mail: dev-help@lucene.apache.org
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
Steve, when I change the script to turn off verification I get the
following error:
RuntimeError: git clone is dirty:
So as part of the work around I think I'm going to have to commit locally
and then revert locally. Does that make sense to you as the way forward?
Joel Bernstein
http://joelsolr.blogspot.com/
On Wed, Apr 19, 2017 at 4:24 PM, Alexandre Rafalovitch <ar...@gmail.com>
wrote:
> Could it be anything to do with the fact that the signer is Semantic
> and they are being actively distrusted by - at least - Google:
> http://www.securityweek.com/google-stops-trusting-
> symantec-issued-certificates
>
> Regards,
> Alex.
> ----
> http://www.solr-start.com/ - Resources for Solr users, new and experienced
>
>
> On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> > Ok, I'll turn off the cert verification. I wasn't sure if cert
> verification
> > was something that was integral to the process.
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> >>
> >> Hi Joel,
> >>
> >> Not sure why this is suddenly an issue - I guess “SNI”
> >> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been
> enabled on
> >> archive.apache.org?
> >>
> >> Some useful info here (about a “requests” lib, AFAICT an alternative to
> >> urllib):
> >> <http://docs.python-requests.org/en/master/community/faq/#
> what-are-hostname-doesn-t-match-errors>
> >>
> >> Short term, you could turn off certificate verification. The bottom
> >> answer here uses the same lib as the script (urllib instead of urllib2,
> >> which is assumed in the other answers on the page), to turn off
> certificate
> >> verification:
> >>
> >>
> >> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
> >>
> >> --
> >> Steve
> >> www.lucidworks.com
> >>
> >> > On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> >> >
> >> > It appears that it's failing on verifying the SSL cert for
> >> > https://archive.apache.org/dist/lucene/java/.
> >> >
> >> >
> >> >
> >> > Joel Bernstein
> >> > http://joelsolr.blogspot.com/
> >> >
> >> > On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> >> > wrote:
> >> > I started working on 6.5.1 RC2. I ran the following:
> >> > python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> >> > /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> >> >
> >> > I believe this is same basic command I used for RC1. But this time I
> got
> >> > a new error. At first I thought it might be incorrect keystore
> password but
> >> > I changed it and it is correct. Any thoughts what the issue is?
> >> >
> >> > Traceback (most recent call last):
> >> >
> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 313, in
> <module>
> >> >
> >> > main()
> >> >
> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> >> >
> >> > rev = prepare(c.root, c.version, c.key_id, c.key_password)
> >> >
> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 98, in
> prepare
> >> >
> >> > checkDOAPfiles(version)
> >> >
> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> >> > checkDOAPfiles
> >> >
> >> > distpage = load(url)
> >> >
> >> > File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> >> >
> >> > content = urllib.request.urlopen(urlString).read().decode('utf-
> 8')
> >> >
> >> > File
> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >> > line 223, in urlopen
> >> >
> >> > return opener.open(url, data, timeout)
> >> >
> >> > File
> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >> > line 526, in open
> >> >
> >> > response = self._open(req, data)
> >> >
> >> > File
> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >> > line 544, in _open
> >> >
> >> > '_open', req)
> >> >
> >> > File
> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >> > line 504, in _call_chain
> >> >
> >> > result = func(*args)
> >> >
> >> > File
> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >> > line 1361, in https_open
> >> >
> >> > context=self._context, check_hostname=self._check_hostname)
> >> >
> >> > File
> >> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/
> python3.6/urllib/request.py",
> >> > line 1320, in do_open
> >> >
> >> > raise URLError(err)
> >> >
> >> > urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> >> > certificate verify failed (_ssl.c:749)>
> >> >
> >> >
> >> >
> >> >
> >> > Joel Bernstein
> >> > http://joelsolr.blogspot.com/
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: dev-help@lucene.apache.org
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Alexandre Rafalovitch <ar...@gmail.com>.
Could it be anything to do with the fact that the signer is Semantic
and they are being actively distrusted by - at least - Google:
http://www.securityweek.com/google-stops-trusting-symantec-issued-certificates
Regards,
Alex.
----
http://www.solr-start.com/ - Resources for Solr users, new and experienced
On 19 April 2017 at 16:22, Joel Bernstein <jo...@gmail.com> wrote:
> Ok, I'll turn off the cert verification. I wasn't sure if cert verification
> was something that was integral to the process.
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
>>
>> Hi Joel,
>>
>> Not sure why this is suddenly an issue - I guess “SNI”
>> <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
>> archive.apache.org?
>>
>> Some useful info here (about a “requests” lib, AFAICT an alternative to
>> urllib):
>> <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
>>
>> Short term, you could turn off certificate verification. The bottom
>> answer here uses the same lib as the script (urllib instead of urllib2,
>> which is assumed in the other answers on the page), to turn off certificate
>> verification:
>>
>>
>> <http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>> > On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
>> >
>> > It appears that it's failing on verifying the SSL cert for
>> > https://archive.apache.org/dist/lucene/java/.
>> >
>> >
>> >
>> > Joel Bernstein
>> > http://joelsolr.blogspot.com/
>> >
>> > On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
>> > wrote:
>> > I started working on 6.5.1 RC2. I ran the following:
>> > python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
>> > /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>> >
>> > I believe this is same basic command I used for RC1. But this time I got
>> > a new error. At first I thought it might be incorrect keystore password but
>> > I changed it and it is correct. Any thoughts what the issue is?
>> >
>> > Traceback (most recent call last):
>> >
>> > File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
>> >
>> > main()
>> >
>> > File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
>> >
>> > rev = prepare(c.root, c.version, c.key_id, c.key_password)
>> >
>> > File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
>> >
>> > checkDOAPfiles(version)
>> >
>> > File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
>> > checkDOAPfiles
>> >
>> > distpage = load(url)
>> >
>> > File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
>> >
>> > content = urllib.request.urlopen(urlString).read().decode('utf-8')
>> >
>> > File
>> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > line 223, in urlopen
>> >
>> > return opener.open(url, data, timeout)
>> >
>> > File
>> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > line 526, in open
>> >
>> > response = self._open(req, data)
>> >
>> > File
>> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > line 544, in _open
>> >
>> > '_open', req)
>> >
>> > File
>> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > line 504, in _call_chain
>> >
>> > result = func(*args)
>> >
>> > File
>> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > line 1361, in https_open
>> >
>> > context=self._context, check_hostname=self._check_hostname)
>> >
>> > File
>> > "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
>> > line 1320, in do_open
>> >
>> > raise URLError(err)
>> >
>> > urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
>> > certificate verify failed (_ssl.c:749)>
>> >
>> >
>> >
>> >
>> > Joel Bernstein
>> > http://joelsolr.blogspot.com/
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
Ok, I'll turn off the cert verification. I wasn't sure if cert verification
was something that was integral to the process.
Joel Bernstein
http://joelsolr.blogspot.com/
On Wed, Apr 19, 2017 at 4:18 PM, Steve Rowe <sa...@gmail.com> wrote:
> Hi Joel,
>
> Not sure why this is suddenly an issue - I guess “SNI” <
> https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on
> archive.apache.org?
>
> Some useful info here (about a “requests” lib, AFAICT an alternative to
> urllib): <http://docs.python-requests.org/en/master/community/faq/#
> what-are-hostname-doesn-t-match-errors>
>
> Short term, you could turn off certificate verification. The bottom
> answer here uses the same lib as the script (urllib instead of urllib2,
> which is assumed in the other answers on the page), to turn off certificate
> verification:
>
> <http://stackoverflow.com/questions/19268548/python-
> ignore-certicate-validation-urllib2>
>
> --
> Steve
> www.lucidworks.com
>
> > On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
> >
> > It appears that it's failing on verifying the SSL cert for
> https://archive.apache.org/dist/lucene/java/.
> >
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
> > On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com>
> wrote:
> > I started working on 6.5.1 RC2. I ran the following:
> > python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> >
> > I believe this is same basic command I used for RC1. But this time I got
> a new error. At first I thought it might be incorrect keystore password but
> I changed it and it is correct. Any thoughts what the issue is?
> >
> > Traceback (most recent call last):
> >
> > File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
> >
> > main()
> >
> > File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
> >
> > rev = prepare(c.root, c.version, c.key_id, c.key_password)
> >
> > File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
> >
> > checkDOAPfiles(version)
> >
> > File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> checkDOAPfiles
> >
> > distpage = load(url)
> >
> > File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
> >
> > content = urllib.request.urlopen(urlString).read().decode('utf-8')
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 223, in urlopen
> >
> > return opener.open(url, data, timeout)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 526, in open
> >
> > response = self._open(req, data)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 544, in _open
> >
> > '_open', req)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 504, in _call_chain
> >
> > result = func(*args)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 1361, in https_open
> >
> > context=self._context, check_hostname=self._check_hostname)
> >
> > File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 1320, in do_open
> >
> > raise URLError(err)
> >
> > urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> certificate verify failed (_ssl.c:749)>
> >
> >
> >
> >
> > Joel Bernstein
> > http://joelsolr.blogspot.com/
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Issue with 6.5.1 RC2
Posted by Steve Rowe <sa...@gmail.com>.
Hi Joel,
Not sure why this is suddenly an issue - I guess “SNI” <https://en.wikipedia.org/wiki/Server_Name_Indication> has been enabled on archive.apache.org?
Some useful info here (about a “requests” lib, AFAICT an alternative to urllib): <http://docs.python-requests.org/en/master/community/faq/#what-are-hostname-doesn-t-match-errors>
Short term, you could turn off certificate verification. The bottom answer here uses the same lib as the script (urllib instead of urllib2, which is assumed in the other answers on the page), to turn off certificate verification:
<http://stackoverflow.com/questions/19268548/python-ignore-certicate-validation-urllib2>
--
Steve
www.lucidworks.com
> On Apr 19, 2017, at 3:43 PM, Joel Bernstein <jo...@gmail.com> wrote:
>
> It appears that it's failing on verifying the SSL cert for https://archive.apache.org/dist/lucene/java/.
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
> On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com> wrote:
> I started working on 6.5.1 RC2. I ran the following:
> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
>
> I believe this is same basic command I used for RC1. But this time I got a new error. At first I thought it might be incorrect keystore password but I changed it and it is correct. Any thoughts what the issue is?
>
> Traceback (most recent call last):
>
> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
>
> main()
>
> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
>
> rev = prepare(c.root, c.version, c.key_id, c.key_password)
>
> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
>
> checkDOAPfiles(version)
>
> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in checkDOAPfiles
>
> distpage = load(url)
>
> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
>
> content = urllib.request.urlopen(urlString).read().decode('utf-8')
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 223, in urlopen
>
> return opener.open(url, data, timeout)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 526, in open
>
> response = self._open(req, data)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 544, in _open
>
> '_open', req)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 504, in _call_chain
>
> result = func(*args)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 1361, in https_open
>
> context=self._context, check_hostname=self._check_hostname)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py", line 1320, in do_open
>
> raise URLError(err)
>
> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)>
>
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Issue with 6.5.1 RC2
Posted by Joel Bernstein <jo...@gmail.com>.
It appears that it's failing on verifying the SSL cert for
https://archive.apache.org/dist/lucene/java/.
Joel Bernstein
http://joelsolr.blogspot.com/
On Wed, Apr 19, 2017 at 3:36 PM, Joel Bernstein <jo...@gmail.com> wrote:
> I started working on 6.5.1 RC2. I ran the following:
>
> python3 -u dev-tools/scripts/buildAndPushRelease.py --push-local
> /tmp/releases/6.5.1 --rc-num 2 --sign EE64CB1E
> I believe this is same basic command I used for RC1. But this time I got a
> new error. At first I thought it might be incorrect keystore password but I
> changed it and it is correct. Any thoughts what the issue is?
>
> Traceback (most recent call last):
>
> File "dev-tools/scripts/buildAndPushRelease.py", line 313, in <module>
>
> main()
>
> File "dev-tools/scripts/buildAndPushRelease.py", line 294, in main
>
> rev = prepare(c.root, c.version, c.key_id, c.key_password)
>
> File "dev-tools/scripts/buildAndPushRelease.py", line 98, in prepare
>
> checkDOAPfiles(version)
>
> File "dev-tools/scripts/buildAndPushRelease.py", line 143, in
> checkDOAPfiles
>
> distpage = load(url)
>
> File "dev-tools/scripts/buildAndPushRelease.py", line 67, in load
>
> content = urllib.request.urlopen(urlString).read().decode('utf-8')
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 223, in urlopen
>
> return opener.open(url, data, timeout)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 526, in open
>
> response = self._open(req, data)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 544, in _open
>
> '_open', req)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 504, in _call_chain
>
> result = func(*args)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 1361, in https_open
>
> context=self._context, check_hostname=self._check_hostname)
>
> File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/urllib/request.py",
> line 1320, in do_open
>
> raise URLError(err)
>
> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> certificate verify failed (_ssl.c:749)>
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>