Re: [Python-Dev] API for bugs.python.org or some statistic about lib/module merge rate?
Thanks for the reply, 2017-04-27 14:14 GMT+08:00 Terry Reedy : > On 4/26/2017 1:17 AM, Louie Lu wrote: > >> Fix some pr counting issue, and now the bpo-mergerate can choose hg (the >> old process), git, or all for mergerate counting. Also, relative bpo issue >> can be expand by clicking row for more detail. > > > Details do not seem to be correct. I searched for 'Lib/idlelib'. > For pyshell.py, it says 3 merged, 1 open. > I clicked and got bpo issues: 29162 29581 29919 30067 > The 'open' one is https://bugs.python.org/issue29581, patch at > https://github.com/python/cpython/pull/527/commits/de5d514e649729a1f9e6f3e132d8ffb872d38b08 > seems to be an error. You are right, somehow database was wrong, and cannot deal with path change (if there is a change after fetching). Rebuild and fix this problem. > > Lib/idlelib/idle_test/test_calltips.py has 1 and 1 > bpo issues: 20185 22392 24665 > None of these are idlelib issues. > Not that directly, but these bpo issue PR has changed the file. See: bpo-20185: PR 542 bpo-24665: PR 89, and a issue fixed but close PR 898. The detail now will show the relative PR (which bpo and which PR that is merged, fixed, or open) inside. e.g. Lib/idlelib/idle_test/test_calltips.py bpo issues: 20185 22392 24665 PR: bpo-20185: PR 542 bpo-24665: PR 89 Best Regards, Louie. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] TLS issue (unknown CA) on test_imaplib
Hi, test_imaplib is starting to fail randomly causing CI tests to fail and buildbots to fail randomly: http://bugs.python.org/issue30175 Can somone please take a look to help me to fix this issue which becomes blocking? test.test_imaplib.RemoteIMAP_SSLTest.test_logincapa_with_client_certfile() fails with: ssl.SSLError: [SSL: TLSV1_ALERT_UNKNOWN_CA] tlsv1 alert unknown ca (_ssl.c:749) RemoteIMAP_SSLTest uses the cyrus.andrew.cmu.edu server with the port 993. Certificate chain: 0 s:/C=US/postalCode=15213/ST=PA/L=Pittsburgh/street=5000 Forbes/O=Carnegie Mellon University/OU=Carnegie Mellon University/OU=Multi-Domain SSL/CN=cyrus.andrew.cmu.edu i:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Organization Validation Secure Server CA 1 s:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Organization Validation Secure Server CA i:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Certification Authority 2 s:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Certification Authority i:/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root 3 s:/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root i:/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root Note: Would it be possible to setup an IMAP server on pythontest.net instead of using a server of an university? http://www.cmu.edu/ Victor ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] TLS issue (unknown CA) on test_imaplib
There's also a failure in test_nntplib: https://travis-ci.org/python/cpython/jobs/226384811#L3157-L3171 Regards Antoine. On Thu, 27 Apr 2017 14:50:43 +0200 Victor Stinner wrote: > Hi, > > test_imaplib is starting to fail randomly causing CI tests to fail and > buildbots to fail randomly: > http://bugs.python.org/issue30175 > > Can somone please take a look to help me to fix this issue which > becomes blocking? > > test.test_imaplib.RemoteIMAP_SSLTest.test_logincapa_with_client_certfile() > fails with: > > ssl.SSLError: [SSL: TLSV1_ALERT_UNKNOWN_CA] tlsv1 alert unknown ca > (_ssl.c:749) > > RemoteIMAP_SSLTest uses the cyrus.andrew.cmu.edu server with the port 993. > > Certificate chain: > > 0 s:/C=US/postalCode=15213/ST=PA/L=Pittsburgh/street=5000 > Forbes/O=Carnegie Mellon University/OU=Carnegie Mellon > University/OU=Multi-Domain SSL/CN=cyrus.andrew.cmu.edu >i:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA > Limited/CN=COMODO RSA Organization Validation Secure Server CA > 1 s:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA > Limited/CN=COMODO RSA Organization Validation Secure Server CA >i:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA > Limited/CN=COMODO RSA Certification Authority > 2 s:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA > Limited/CN=COMODO RSA Certification Authority >i:/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust > External CA Root > 3 s:/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust > External CA Root >i:/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust > External CA Root > > Note: Would it be possible to setup an IMAP server on pythontest.net > instead of using a server of an university? http://www.cmu.edu/ > > Victor ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] TLS issue (unknown CA) on test_imaplib
2017-04-27 15:41 GMT+02:00 Antoine Pitrou : > There's also a failure in test_nntplib: > https://travis-ci.org/python/cpython/jobs/226384811#L3157-L3171 That's a different issue, unrelated to the SSL issue. EOFError is probably as old as test_nntplib, there are 2 open issues to track this bug: http://bugs.python.org/issue19613 http://bugs.python.org/issue19756 Victor ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] TLS issue (unknown CA) on test_imaplib
2017-04-27 15:46 GMT+02:00 Victor Stinner : > 2017-04-27 15:41 GMT+02:00 Antoine Pitrou : >> There's also a failure in test_nntplib: >> https://travis-ci.org/python/cpython/jobs/226384811#L3157-L3171 > > That's a different issue, unrelated to the SSL issue. > > EOFError is probably as old as test_nntplib, there are 2 open issues > to track this bug: Oh wait, it seems like nntplib now has a fail rate close to 100% :-/ I created http://bugs.python.org/issue30188 and wrote a fix. I included this nntplib fix in my imaplib PR... Victor ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] API for bugs.python.org or some statistic about lib/module merge rate?
On 4/27/2017 7:57 AM, Louie Lu wrote: Lib/idlelib/idle_test/test_calltips.py has 1 and 1 bpo issues: 20185 22392 24665 None of these are idlelib issues. Not that directly, but these bpo issue PR has changed the file. See: bpo-20185: PR 542 bpo-24665: PR 89, and a issue fixed but close PR 898. #20185: The PR number is *very* helpful. This issue has multiple patches and 5 PRs merged to default. #22392: PR 89 has about 10 commits. The original, easy-to-find patch, https://github.com/python/cpython/pull/89/commits/6ea78e33b599605b0c1c35fbbc2df493d6dfc80a did not touch test_calltips. It is touched by the latest, not so easy-to-find commit https://github.com/python/cpython/pull/89/commits/54de7aa6c6fffe9b2248153051a24b0e658bf665 I don't know how to get the complete merged diff that would be applied if the green button were pressed. #22392 has PR 899 (merged) and PR 898 (closed). The latter was a blunder that incorporated about 100 already applied patches, mostly from 2016. Take a look. https://github.com/python/cpython/pull/898 Part of doing good statistics is removing bogus data from datasets. Even though you cannot remove 898 from github, you should ignore it in your analysis. All the hits it generates are false positives. This is probably the source of many other false hits for idlelib. The detail now will show the relative PR (which bpo and which PR that is merged, fixed, or open) inside. e.g. Lib/idlelib/idle_test/test_calltips.py bpo issues: 20185 22392 24665 PR: bpo-20185: PR 542 bpo-24665: PR 89 Note that 898 is so bogus that it cannot be handled properly. For me, the immediate use case is to find patches to idlelib by others that I am not aware of, like the two real ones to test_calltips. I would like an entry box for the start date to put in date last checked. What would be really super would to be able to exclude issues (and associated patches) assigned to me. When you get this polished, I hope you open an issue and PR to add it to one of the cpython and mention it in the devguide. -- Terry Jan Reedy ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] TLS issue (unknown CA) on test_imaplib
2017-04-27 17:16 GMT+02:00 Victor Stinner : > Oh wait, it seems like nntplib now has a fail rate close to 100% :-/ I > created http://bugs.python.org/issue30188 and wrote a fix. I included > this nntplib fix in my imaplib PR... I have good news: * I pushed fixes for test_imaplib and test_nntplib in 3.5, 3.6 and master * I contacted the administrator of the NNTP server used by test_nntplib. I noticed a failure this morning (the server was unable to spawn new processes). He fixed the issue, the server should be back. I was aware that Python was using his server and doesn't seem to be annoyed by that. He wrote RFC 6048, RFC 8143, and co-authored the RFC 8054! Network News Transfer Protocol (NNTP) Additions to LIST Command https://tools.ietf.org/html/rfc6048 Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP) https://tools.ietf.org/html/rfc8143 Network News Transfer Protocol (NNTP) Extension for Compression https://tools.ietf.org/html/rfc8054 He asked me if Python is going to support the last extension, Compression. I don't know nntplib, so I have to take a look. Victor ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] API for bugs.python.org or some statistic about lib/module merge rate?
2017-04-28 4:06 GMT+08:00 Terry Reedy : > On 4/27/2017 7:57 AM, Louie Lu wrote: > >>> Lib/idlelib/idle_test/test_calltips.py has 1 and 1 >>> bpo issues: 20185 22392 24665 >>> None of these are idlelib issues. >>> >> >> Not that directly, but these bpo issue PR has changed the file. >> See: bpo-20185: PR 542 bpo-24665: PR 89, and a issue fixed but close PR >> 898. > > > #20185: The PR number is *very* helpful. This issue has multiple patches > and 5 PRs merged to default. > > #22392: PR 89 has about 10 commits. The original, easy-to-find patch, > https://github.com/python/cpython/pull/89/commits/6ea78e33b599605b0c1c35fbbc2df493d6dfc80a > did not touch test_calltips. > > It is touched by the latest, not so easy-to-find commit > https://github.com/python/cpython/pull/89/commits/54de7aa6c6fffe9b2248153051a24b0e658bf665 > > I don't know how to get the complete merged diff that would be applied if > the green button were pressed. > > #22392 has PR 899 (merged) and PR 898 (closed). The latter was a blunder > that incorporated about 100 already applied patches, mostly from 2016. Take > a look. > https://github.com/python/cpython/pull/898 > > Part of doing good statistics is removing bogus data from datasets. Even > though you cannot remove 898 from github, you should ignore it in your > analysis. All the hits it generates are false positives. This is probably > the source of many other false hits for idlelib. > Now add the blacklist for PR, this is still manual to add into the config I have three cases: PR 898, PR 703, and PR 552. The "automatic" identified should be add in future (probably) >> The detail now will show the relative PR (which bpo and which PR that >> is merged, fixed, or open) inside. >> >> e.g. >> Lib/idlelib/idle_test/test_calltips.py >> bpo issues: 20185 22392 24665 >> PR: bpo-20185: PR 542 bpo-24665: PR 89 > > > Note that 898 is so bogus that it cannot be handled properly. > > For me, the immediate use case is to find patches to idlelib by others that > I am not aware of, like the two real ones to test_calltips. I would like an > entry box for the start date to put in date last checked. What would be The latest bpo-issue check date will now be shown when the cursor hovers on the issue. (That mean, mobile can't see the date now. I think (on mobile) this isn't that needed) > really super would to be able to exclude issues (and associated patches) > assigned to me. This may be update in the future. (Assignee from bpo or GitHub?) > > When you get this polished, I hope you open an issue and PR to add it to one > of the cpython and mention it in the devguide. > Yes, I will. A small question what does it mean "add it to one of the cpython"? > > -- > Terry Jan Reedy > Best Regards, Louie. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
