[issue46542] test_json and test_lib2to3 crash on s390x Fedora Clang 3.x buildbot

Charalampos Stratakis added the comment: The issue seems to be affecting also the PPC64LE Fedora Rawhide Clang 3.x and PPC64LE Fedora Stable Clang 3.x -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue46

[issue46114] OpenSSL 3.0 uses different version scheme

Charalampos Stratakis added the comment: 3.8 builds are still running on the buildbots so not fixing 3.8 will cause them to fail. -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue46

[issue46114] OpenSSL 3.0 uses different version scheme

Charalampos Stratakis added the comment: Case in point: https://buildbot.python.org/all/#/builders/355/builds/338 -- ___ Python tracker <https://bugs.python.org/issue46

[issue38033] Use After Free: PyObject_Free (valgrind)

Charalampos Stratakis added the comment: Another thing also, is to be sure to utilize the python's suppression file by adding the --suppressions= to valgrind's command line invocation. -- nosy: +cstratak ___ Python track

[issue38132] Simplify hashlib implementation

Charalampos Stratakis added the comment: Yes that would be awesome! Indeed hashlib has been a bit of a pain to work with especially with FIPS related modifications, simplifying it would help a ton. -- nosy: +cstratak ___ Python tracker <ht

[issue17258] multiprocessing.connection challenge implicitly uses MD5

Change by Charalampos Stratakis : -- pull_requests: +15857 pull_request: https://github.com/python/cpython/pull/16264 ___ Python tracker <https://bugs.python.org/issue17

[issue38239] test_gdb fails on AMD64 Fedora Stable LTO 3.8 and AMD64 RHEL8 LTO 3.x: Unexpected gdb output

Change by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue38239> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38269] AMD64 Debian PGO 3.x, AMD64 Clang UBSan 2.7 buildbots: No space left on device

Charalampos Stratakis added the comment: Yep that was my change as some jobs couldn't be run on the same worker due to the configs using the same directory. -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/is

[issue38269] AMD64 Debian PGO 3.x, AMD64 Clang UBSan 2.7 buildbots: No space left on device

Charalampos Stratakis added the comment: It's already explained that the build directories are duplicated, however it could be more verbose indeed. When a config is being used alongside a config which inherits from the previous one, then buildbot aborts with an error as it tries to co

[issue37096] Add large-file tests for modules using sendfile(2)

Charalampos Stratakis added the comment: After this change I get some disk space issues on the Fedora rawhide buildbot for the clang installed build only (and strangely enough not for the other jobs). There are currently around 9GB of free space there: https://buildbot.python.org/all

[issue37096] Add large-file tests for modules using sendfile(2)

Charalampos Stratakis added the comment: It seems that the -uall argument is passed to regrtest invocation for the buildbot run [0] which invokes the largefile tests (including all the resource intensive tests). However when configure is run you can see: checking whether to enable large

[issue37631] EXTRA_CFLAGS get overrided by CFLAGS_NODIST

Charalampos Stratakis added the comment: Dug a bit further here. The issue is that CFLAGS_NODIST will always come after normal CFLAGS (which are subsets of PY_CFLAGS and PY_CFLAGS_NODIST) [0][1]. The EXTRA_CFLAGS variable is appended at the end of PY_CFLAGS [2], hence as reported here

[issue37631] EXTRA_CFLAGS get overrided by CFLAGS_NODIST

Charalampos Stratakis added the comment: Also this is due to an expected behaviour from gcc. From the documentation: "If you use multiple -O options, with or without level numbers, the last such option is the one that is effe

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

Charalampos Stratakis added the comment: Do note though that if the -D_FORTIFY_SOURCE=2 hardening flag is used, the compilation will fail with an optimization level less than -Og. Haven't tried yet with -D_FORTIFY_SOURCE=1 to see if it works with -O0. -- nosy: +cst

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

Charalampos Stratakis added the comment: Correction, not fail, just a ton of warnings. The same is true for -D_FORTIFY_SOURCE=1 -- ___ Python tracker <https://bugs.python.org/issue38

[issue38350] ./configure --with-pydebug should use -O0 rather than -Og

Charalampos Stratakis added the comment: It seems that it's still being worked on from gcc's side: https://gcc.gnu.org/bugzilla//show_bug.cgi?id=78685 -- ___ Python tracker <https://bugs.python.o

[issue38510] build python with --enable-shared with static linked python against libpython*.a

Change by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue38510> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34028] Python 3.7.0 wont compile with SSL Support 1.1.0 > alledged missing X509_VERIFY_PARAM_set1_host() support

Charalampos Stratakis added the comment: Have you also tried $ yum install openssl-devel ? That should work without requiring to compile openssl from source, unless you want a later version, which isn't advisable to install system-wide, as it could break other things. --

[issue38576] CVE-2019-18348: CRLF injection via the host part of the url passed to urlopen()

Change by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue38576> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43164] test_nntplib.NetworkedNNTP_SSLTests fails on "AMD64 RHEL8 FIPS Only Blake2 Builtin Hash" buildbot

Charalampos Stratakis added the comment: The issue seems to be resolved and the buildbot is green. -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue38820] Make Python compatible with OpenSSL 3.0.0

Change by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue38820> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44048] test_hashlib failure for "AMD64 RHEL8 FIPS Only Blake2 Builtin Hash" buildbot

New submission from Charalampos Stratakis : The buildbot started experiencing some failures. First after https://github.com/python/cpython/commit/ddbef71a2c166a5d5dd168e26493973053a953d6 this test started failing with

[issue44048] test_hashlib failure for "AMD64 RHEL8 FIPS Only Blake2 Builtin Hash" buildbot

Change by Charalampos Stratakis : -- keywords: +patch pull_requests: +25065 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26470 ___ Python tracker <https://bugs.python.org/issu

[issue44285] Coverity scan: Modules/getpath.c. "calculate_open_pyenv" allocates memory that is stored into "env_file".

New submission from Charalampos Stratakis : This is an issue as it seems with coverity as it's an error case where the file was not actually opened. This warning can be silenced and the code be made more explicit by adding an assertion. Python-3.9.1/Modules/getpath.c:1264: allo

[issue44285] Coverity scan: Modules/getpath.c. "calculate_open_pyenv" allocates memory that is stored into "env_file".

Change by Charalampos Stratakis : -- keywords: +patch pull_requests: +25082 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26486 ___ Python tracker <https://bugs.python.org/issu

[issue45067] Failed to build _curses on CentOS 7

Charalampos Stratakis added the comment: You should use -lpaneltw instead of -lpanelw. See also: https://bugs.python.org/issue41981 -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue45

[issue37096] Add large-file tests for modules using sendfile(2)

Charalampos Stratakis added the comment: Alright added some more disk space at the buildbots, however it seems that it is not related to that. The current Fedora rawhide buildbot has 19GB of free space and the test is still failing. I tested on the Fedora stable buildbot for which I reduced

[issue38850] test_largefile fails on android

Charalampos Stratakis added the comment: I got the same failures on Fedora rawhide. See https://bugs.python.org/issue37096 -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue38

[issue38270] Tests: Avoid MD5 or check for MD5 availablity

Change by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue38270> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38270] Tests: Avoid MD5 or check for MD5 availablity

Change by Charalampos Stratakis : -- pull_requests: +16927 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/17446 ___ Python tracker <https://bugs.python.org/issu

[issue38980] Compile libpython with -fno-semantic-interposition

Charalampos Stratakis added the comment: > Maybe it should only be default when using --with-optimizations I think it will add to the complexity of the --with-optimizations flag which already implies PGO and LTO. Maybe an opt-in flag would be better IMHO. -- nosy: +cstra

[issue38965] test_stack_overflow (test.test_faulthandler.FaultHandlerTests) is stuck with GCC10

Charalampos Stratakis added the comment: Would it make sense to also backport this fix to the 3.6 release? People compiling 3.6 with gcc 10 will stumble upon that. -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue38

[issue37096] Add large-file tests for modules using sendfile(2)

Charalampos Stratakis added the comment: Can we reopen the issue? Clearly this change modifies the expectations of free disk space for the temp files created by the tests. Or at least clarify that those tests require more than 6gb of free disk space in /tmp for unix

[issue39676] test_shutil fails with OSError: [Errno 28] No space left on device on "PPC64LE Fedora Stable LTO + PGO 3.x" buildbot

Charalampos Stratakis added the comment: The issue has been fixed. root was 15GB, but there was still 30GB of un-allocated space in the volume group, so just expanded the logical volume. -- ___ Python tracker <https://bugs.python.org/issue39

[issue39689] test_struct failure on s390x Fedora Clang buildbot

New submission from Charalampos Stratakis : The clang build was recently added for that buildbot and it seems on that particular architecture, test_struct fails with: == FAIL: test_bool (test.test_struct.StructTest

[issue39689] test_struct failure on s390x Fedora Clang buildbot

Charalampos Stratakis added the comment: Failed assertion here: https://github.com/python/cpython/blob/master/Lib/test/test_struct.py#L520 -- ___ Python tracker <https://bugs.python.org/issue39

[issue39689] test_struct failure on s390x Fedora Clang buildbot

Charalampos Stratakis added the comment: On this loop: for c in [b'\x01', b'\x7f', b'\xff', b'\x0f', b'\xf0']: self.assertTrue(struct.unpack('>?', c)[0]) It fails for the b'\xf0' case -- __

[issue38913] Py_BuildValue("(s#O)", ...) segfaults if entered with exception raised

Charalampos Stratakis added the comment: After this change, the arm64 buildbots are reporting reference leaks: 1:03:24 load avg: 0.95 Re-running failed tests in verbose mode 1:03:24 load avg: 0.95 Re-running test_capi in verbose mode test_capi leaked [4, 4, 4] references, sum=12 e.g. https

[issue32521] NIS module fails to build due to the removal of interfaces related to Sun RPC from glibc.

Charalampos Stratakis added the comment: Closing the issue as python2 is not receiving any more fixes and our downstream workaround is enough for it. Python3 is fine as well. -- status: open -> closed ___ Python tracker <https://bugs.pyth

[issue40044] Tests failing with the latest update of openssl to version 1.1.1e

New submission from Charalampos Stratakis : The fedora rawhide buildbots started failing due to the latest update of openssl to version 1.1.1e. e.g. https://buildbot.python.org/all/#/builders/607/builds/137 Changelog: https://www.openssl.org/news/cl111.txt The relevant info which seems to

[issue40044] Tests failing with the latest update of openssl to version 1.1.1e

Charalampos Stratakis added the comment: Closing it as duplicate of https://bugs.python.org/issue40018 -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue40018] test_ssl fails with OpenSSL 1.1.1e

Charalampos Stratakis added the comment: The relevant info which seems to make the tests fail: Properly detect EOF while reading in libssl. Previously if we hit an EOF while reading in libssl then we would report an error back to the application (SSL_ERROR_SYSCALL) but errno would be 0. We

[issue40018] test_ssl fails with OpenSSL 1.1.1e

Change by Charalampos Stratakis : -- keywords: +patch pull_requests: +18491 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19129 ___ Python tracker <https://bugs.python.org/issu

[issue40018] test_ssl fails with OpenSSL 1.1.1e

Charalampos Stratakis added the comment: Still searching the issue and created a first draft PR. With it, tesT_ssl and test_imaplib pass now, urllib2_localnet still has issues. -- ___ Python tracker <https://bugs.python.org/issue40

[issue40018] test_ssl fails with OpenSSL 1.1.1e

Charalampos Stratakis added the comment: This behavior change is considered being reverted upstream. PR: https://github.com/openssl/openssl/pull/11400 -- ___ Python tracker <https://bugs.python.org/issue40

[issue40018] test_ssl fails with OpenSSL 1.1.1e

Charalampos Stratakis added the comment: The change has been reverted upstream. Also on the rawhide buildbots, we have an updated build with the commit reverted, so they returned back to green. Now the revertion will be included at a new release of the 1.1.1 branch, however it will still

[issue40018] test_ssl fails with OpenSSL 1.1.1e

Charalampos Stratakis added the comment: And there is already a meta-issue created by cheimes for 3.0.0: https://bugs.python.org/issue38820 -- ___ Python tracker <https://bugs.python.org/issue40

[issue40334] PEP 617: new PEG-based parser

Charalampos Stratakis added the comment: > Is this related to this issue? We didn't change that line I can provide you access to the buildbot if you'd like to debug the issue. -- nosy: +cstratak ___ Python tracker <https:/

[issue40334] PEP 617: new PEG-based parser

Change by Charalampos Stratakis : -- nosy: -cstratak ___ Python tracker <https://bugs.python.org/issue40334> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43164] test_nntplib.NetworkedNNTP_SSLTests fails on "AMD64 RHEL8 FIPS Only Blake2 Builtin Hash" buildbot

New submission from Charalampos Stratakis : This is one of the unstable buildbots, running under FIPS mode. One of the tests is failing at the moment. == ERROR: setUpClass (test.test_nntplib.NetworkedNNTP_SSLTests

[issue43179] Remove 32-bit s390 Linux support (s390-linux-gnu triplet)

Charalampos Stratakis added the comment: For RHEL7 which is the older OS that buildbots are still running, only the System Z architecture is supported. From the release notes [0]: Note that Red Hat Enterprise Linux 7 supports IBM zEnterprise 196 hardware or later; IBM System z10 mainframe

[issue43179] Remove 32-bit s390 Linux support (s390-linux-gnu triplet)

Charalampos Stratakis added the comment: And to dig a bit further with a semi-official answer. RHEL4 had standalone support for s390, while since RHEL5+ we've had only multilib support (64 bits kernel and possibility of s390 userspace packages). RHEL7 that is the oldest currently supp

[issue43179] Remove 32-bit s390 Linux support (s390-linux-gnu triplet)

Charalampos Stratakis added the comment: > s390 is being built for SLE-12, for example, on the internal SUSE build > system and SLE-12 is still supported. So if a customer wants to use Python > 3.10 in a SLE-12 s390 environment, why keep them from doing so? Are you sure about that?

[issue43179] Remove 31/32-bit s390 Linux support (s390-linux-gnu triplet)

Charalampos Stratakis added the comment: > You do not need to support every platform. Just allow your users to use them. This is kinda missing the point though. For example I've dealt a lot with the CPython codebase (and I'm also one of the Red Hat maintainers for RHEL and

[issue40698] distutils.command.upload md5_digest

Charalampos Stratakis added the comment: There is also https://github.com/pypa/warehouse/pull/888 So I would assume it's safe it change the digest to sha256. -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/is

[issue40637] Allow users to disable builtin hash modules on compile time

Change by Charalampos Stratakis : -- nosy: +cstratak nosy_count: 2.0 -> 3.0 pull_requests: +20116 pull_request: https://github.com/python/cpython/pull/20937 ___ Python tracker <https://bugs.python.org/issu

[issue40637] Allow users to disable builtin hash modules on compile time

Change by Charalampos Stratakis : -- pull_requests: +20131 pull_request: https://github.com/python/cpython/pull/20951 ___ Python tracker <https://bugs.python.org/issue40

[issue37630] Investigate replacing SHA3 code with OpenSSL

Change by Charalampos Stratakis : -- pull_requests: +20160 pull_request: https://github.com/python/cpython/pull/20986 ___ Python tracker <https://bugs.python.org/issue37

[issue41175] Static analysis issues reported by GCC 10

New submission from Charalampos Stratakis : GCC added a static analysis tool recently [0]. Running it under for CPython code base produces some interesting results. Reproducer: ./configure --with-pydebug && CFLAGS='-fanalyzer' make Attaching the log. [0] https://develope

[issue41175] Static analysis issues reported by GCC 10

Charalampos Stratakis added the comment: First issue in Objects/bytearrayobject.c [0]. warning: use of NULL ‘’ where non-null expected [CWE-690] [-Wanalyzer-null-argument] 277 | memcpy(result->ob_bytes, va.buf, va.len); [0] https://github.com/python/cpython/blob/master/Obje

[issue41175] Static analysis issues reported by GCC 10

Change by Charalampos Stratakis : -- keywords: +patch pull_requests: +20392 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21240 ___ Python tracker <https://bugs.python.org/issu

[issue41642] RHEL and fedora buildbots fail due to disk space error

Charalampos Stratakis added the comment: There is an issue which I discovered after I returned from holidays, basically the buildbot-worker keeps getting disconnected from master, so builds start and end abruptly, retaining some artifacts. The next second it tried again with the same

[issue41642] RHEL and fedora buildbots fail due to disk space error

Charalampos Stratakis added the comment: There were almost 10GB of remnant cc* files in /tmp from the compilers used, which I presume were also the temporary artifacts which remained there after the disconnects. Cleaned those up and rebooted the RHEL8 x86_64 buildbot

[issue41648] edelsohn-* buildbot worker failing with: No space left on device

Charalampos Stratakis added the comment: Note: I found that all my Fedora and RHEL8 buildbots have issues with connecting to the master buildbot server. Not sure if a related package got updated and prompts the disconnects (as the RHEL7 ones are fine), or if it's relevant to the m

[issue41981] Errors building python 3.9.0 from source on Centos 7 with GCC 10

Charalampos Stratakis added the comment: The RHEL7 buildbots test on the default system compiler (GCC 4.8). The combination of RHEL7 + GCC10 + Python 3.9 could do very weird stuff, and I don't think it would easy to support. Generally the build environment of an OS is tied to the de

[issue37081] Test with OpenSSL 1.1.1c

Charalampos Stratakis added the comment: Reported here: https://bugs.python.org/issue35998 -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue37

[issue37081] Test with OpenSSL 1.1.1c

Charalampos Stratakis added the comment: Also those failures are recorded on the Fedora buildbot, it seems to be happening randomly: https://buildbot.python.org/all/#/workers/32 -- ___ Python tracker <https://bugs.python.org/issue37

[issue36742] CVE-2019-10160: urlsplit NFKD normalization vulnerability in user:password@

Change by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue36742> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37382] Improve conditional check for test_gdb

Charalampos Stratakis added the comment: There is a fleet of buildbots with a variety og versions of gcc and gdb, so if a change like that is pushed, all the fleet has to be monitored for potential failures, as there are many older OSes supported there. -- nosy: +cstratak

[issue37631] EXTRA_CFLAGS get overrided by CFLAGS_NODIST

Charalampos Stratakis added the comment: Could you provide more info, e.g. comparison between the proper and the erroneous output, as well as what it affects (test_gdb if I recall correctly)? -- nosy: +cstratak ___ Python tracker <ht

[issue9216] FIPS support for hashlib

Charalampos Stratakis added the comment: Providing a simple keyword as a workaround for bypassing the FIPS restrictions, could potentially violate the standard, as there is no way from the python side to verify if the code in question is used for security purposes or not. Thus I would close

[issue37630] Investigate replacing SHA3 code with OpenSSL

Change by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue37630> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37631] EXTRA_CFLAGS get overrided by CFLAGS_NODIST

Charalampos Stratakis added the comment: I agree that documenting the flags is quite important, I've had a hard time trying to figure out how to implement the LDFLAGS_NODIST, and the change still broke macos builds (luckily it was fixed swiftly). Nevertheless, this is still a bug

[issue30714] test_ssl fails with openssl 1.1.0f

New submission from Charalampos Stratakis: After updating openssl in Fedora 26 from 1.1.0e to 1.1.0f the test_alpn_protocols from test_ssl started failing: == FAIL: test_alpn_protocols (test.test_ssl.ThreadedTests

[issue30714] test_ssl fails with openssl 1.1.0f

Charalampos Stratakis added the comment: Note: Python version is 3.6.1 -- versions: +Python 3.6 ___ Python tracker <http://bugs.python.org/issue30714> ___ ___

[issue29523] latest setuptools breaks virtualenvs due to unbundling dependencies

Charalampos Stratakis added the comment: Closing this per the discussion at the PR. -- stage: -> resolved status: open -> closed ___ Python tracker <http://bugs.python.org/i

[issue29411] Option --executable for entry_points

Changes by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <http://bugs.python.org/issue29411> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26415] Excessive peak memory consumption by the Python parser

Changes by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <http://bugs.python.org/issue26415> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9216] FIPS support for hashlib

Charalampos Stratakis added the comment: @Andrew This has already been implemented downstream for RHEL and centos. -- ___ Python tracker <http://bugs.python.org/issue9

[issue31013] gcc7 throws warning when pymem.h development header is used

Changes by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <http://bugs.python.org/issue31013> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31017] gcc 7 fallthrough warnings

New submission from Charalampos Stratakis: On gcc 7 the new -Wimplicit-fallthrough option was introduced which produces warnings about switch cases that can fall through. The easiest way to silence these warnings is to add the comment /* Falls through. */ for those cases. More information

[issue30923] Add -Wimplicit-fallthrough=0 to Makefile ?

Changes by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <http://bugs.python.org/issue30923> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31032] test_ssl

Charalampos Stratakis added the comment: This is a duplicate of http://bugs.python.org/issue30714 -- nosy: +cstratak ___ Python tracker <http://bugs.python.org/issue31

[issue30923] Add -Wimplicit-fallthrough=0 to Makefile ?

Charalampos Stratakis added the comment: Yeah the warnings are quit annoying when compiling the master and 3.6 branch. Fedora 26 currently includes gcc 7 which emits those warnings, other distros will follow up when they update gcc, so I'd think it would be better to f

[issue31034] test_subprocess_send_signal() of test_asyncio hangs if SIGHUP is ignored

Changes by Charalampos Stratakis : -- nosy: +cstratak versions: +Python 3.6 ___ Python tracker <http://bugs.python.org/issue31034> ___ ___ Python-bugs-list mailin

[issue31132] test_prlimit from test_resource fails when building python3 inside systemd-nspawn environment

New submission from Charalampos Stratakis: FAIL: test_prlimit (test.test_resource.ResourceTest) -- Traceback (most recent call last): File "/builddir/build/BUILD/Python-3.6.2/Lib/test/support/__init__.py", lin

[issue31158] test_pty: test_basic() fails randomly on Travis CI

Charalampos Stratakis added the comment: I've observed the exact same issue on Fedora at random times. -- nosy: +cstratak ___ Python tracker <http://bugs.python.org/is

[issue31429] TLS cipher suite compile time option for downstream

Changes by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue31429> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31450] Subprocess exceptions re-raised in parent process do not have child_traceback attribute

Changes by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker <https://bugs.python.org/issue31450> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33570] OpenSSL 1.1.1 / TLS 1.3 cipher suite changes

Change by Charalampos Stratakis : -- pull_requests: +9850 ___ Python tracker <https://bugs.python.org/issue33570> ___ ___ Python-bugs-list mailing list Unsub

[issue28043] Sane defaults for SSLContext options and ciphers

Change by Charalampos Stratakis : -- pull_requests: +9851 stage: commit review -> patch review ___ Python tracker <https://bugs.python.org/issue28043> ___ _

[issue35351] LTOFLAGS are passed to BASECFLAGS when using LTO

New submission from Charalampos Stratakis : Through configure.ac and this change [0] LTOFLAGS and more specifically -flto is baked into BASECFLAGS when using link time optimizations, which will make this flag propagate to distutils. [0] https://github.com/python/cpython/commit

[issue35351] LTOFLAGS are passed to BASECFLAGS when using LTO

Change by Charalampos Stratakis : -- keywords: +patch pull_requests: +10044 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue35352] test_asyncio fails on RHEL8

New submission from Charalampos Stratakis : When compiling python3 on RHEL8 and run the tests, test_asyncio fails with 8 failures (and more on older branches). openssl version is 1.1.1 Attaching the failures for the various branches. -- components: Tests, asyncio files

[issue35352] test_asyncio fails on RHEL8

Change by Charalampos Stratakis : Added file: https://bugs.python.org/file47956/asyncio_failures_3.7.log ___ Python tracker <https://bugs.python.org/issue35352> ___ ___

[issue35352] test_asyncio fails on RHEL8

Charalampos Stratakis added the comment: Seems that 3.8 and 3.7 get the same failures, while 3.6 gets 14 instead of 8. -- ___ Python tracker <https://bugs.python.org/issue35

[issue35352] test_asyncio fails on RHEL8

Change by Charalampos Stratakis : Added file: https://bugs.python.org/file47957/asyncio_failures_3.6.log ___ Python tracker <https://bugs.python.org/issue35352> ___ ___

[issue35352] test_asyncio fails on RHEL8

Charalampos Stratakis added the comment: It seems I can reproduce it on Fedora as well by setting stronger crypto defaults through 'update-crypto-policies --set FUTURE'. Repo located here: https://gitlab.com/redhat-crypto/fedora-crypto-policies/tree/master The changes are many

[issue35352] test_asyncio fails on RHEL8

Charalampos Stratakis added the comment: I believe I figured out the issue, at least on the master branch. While checking the certificates used by asyncio tests within the test_asyncio folder I noticed they were quite outdated when compared to the more recent updated ones with the test

[issue35352] test_asyncio fails on RHEL8

Change by Charalampos Stratakis : -- keywords: +patch pull_requests: +10067 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

  1   2   3   >