Charalampos Stratakis added the comment:
Case in point: https://buildbot.python.org/all/#/builders/355/builds/338
--
___
Python tracker
<https://bugs.python.org/issue46
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
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
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
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
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: alloc_arg
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
New submission from Charalampos Stratakis :
The buildbot started experiencing some failures. First after
https://github.com/python/cpython/commit/ddbef71a2c166a5d5dd168e26493973053a953d6
this test started failing
Change by Charalampos Stratakis :
--
nosy: +cstratak
___
Python tracker
<https://bugs.python.org/issue38820>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
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
Fed
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?
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 supported
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
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
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 default
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 master
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
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
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
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
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://developers.redhat.
Change by Charalampos Stratakis :
--
pull_requests: +20160
pull_request: https://github.com/python/cpython/pull/20986
___
Python tracker
<https://bugs.python.org/issue37
Change by Charalampos Stratakis :
--
pull_requests: +20131
pull_request: https://github.com/python/cpython/pull/20951
___
Python tracker
<https://bugs.python.org/issue40
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
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/issue40
Change by Charalampos Stratakis :
--
nosy: -cstratak
___
Python tracker
<https://bugs.python.org/issue40334>
___
___
Python-bugs-list mailing list
Unsubscribe:
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://bugs.pyth
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
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
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
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
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
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
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
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
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
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
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
--
___
Python tracker
<https://bugs.python.org/issu
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
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
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
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
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
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
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
Change by Charalampos Stratakis :
--
nosy: +cstratak
___
Python tracker
<https://bugs.python.org/issue38270>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
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
Change by Charalampos Stratakis :
--
nosy: +cstratak
___
Python tracker
<https://bugs.python.org/issue38576>
___
___
Python-bugs-list mailing list
Unsubscribe:
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.
--
nosy
Change by Charalampos Stratakis :
--
nosy: +cstratak
___
Python tracker
<https://bugs.python.org/issue38510>
___
___
Python-bugs-list mailing list
Unsubscribe:
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.org/issue38
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
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: +cstratak
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
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
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
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
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 compile
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/issue38
Change by Charalampos Stratakis :
--
nosy: +cstratak
___
Python tracker
<https://bugs.python.org/issue38239>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Charalampos Stratakis :
--
pull_requests: +15857
pull_request: https://github.com/python/cpython/pull/16264
___
Python tracker
<https://bugs.python.org/issue17
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
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 tracker
<ht
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 which
Change by Charalampos Stratakis :
--
nosy: +cstratak
___
Python tracker
<https://bugs.python.org/issue37630>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
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
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
Change by Charalampos Stratakis :
--
nosy: +cstratak
___
Python tracker
<https://bugs.python.org/issue36742>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
Charalampos Stratakis added the comment:
Reported here: https://bugs.python.org/issue35998
--
nosy: +cstratak
___
Python tracker
<https://bugs.python.org/issue37
Charalampos Stratakis added the comment:
A small clarification on the differences of those two CVE's.
CVE-2019-9740: CLRF sequences are not properly handled in python built-in
modules urllib/urllib2 in the query part of the url parameter of urlopen()
function
CVE-2019-9947: CLRF sequences
Change by Charalampos Stratakis :
--
nosy: +cstratak
___
Python tracker
<https://bugs.python.org/issue35907>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Charalampos Stratakis :
--
nosy: +cstratak
___
Python tracker
<https://bugs.python.org/issue36659>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Charalampos Stratakis :
--
nosy: +cstratak
___
Python tracker
<https://bugs.python.org/issue36276>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Charalampos Stratakis :
In tokenizer.c we have those lines of code [0]:
if (final_length < needed_length && final_length)
/* should never fail */
buf = PyMem_REALLOC(buf, final_length);
return buf;
If however that realloc fails, the memory allocate
Charalampos Stratakis added the comment:
On my system with openssl 1.1.1b, by reducing the PAYLOAD_SIZE the test passes
successfully.
It starts failing when it's bigger than 1024 * 95
--
___
Python tracker
<https://bugs.python.org/issue35
Change by Charalampos Stratakis :
--
pull_requests: +12305
___
Python tracker
<https://bugs.python.org/issue18368>
___
___
Python-bugs-list mailing list
Unsub
Charalampos Stratakis added the comment:
This code is unreachable. Will mark it as such.
--
___
Python tracker
<https://bugs.python.org/issue36292>
___
___
Pytho
Change by Charalampos Stratakis :
--
versions: -Python 2.7, Python 3.7
___
Python tracker
<https://bugs.python.org/issue36292>
___
___
Python-bugs-list mailin
Change by Charalampos Stratakis :
--
keywords: +patch
pull_requests: +12304
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
New submission from Charalampos Stratakis :
The coverity scan was run on python2, however the same defect seems to exist in
python3 as well.
Error: RESOURCE_LEAK (CWE-772): [#def69]
Python-2.7.15/Objects/longobject.c:3793: alloc_fn: Storage is returned from
allocation function "_PyLon
Change by Charalampos Stratakis :
--
keywords: +patch
pull_requests: +12301
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
New submission from Charalampos Stratakis :
Coverity reports a leak within the json module:
Error: RESOURCE_LEAK (CWE-772): [#def26]
Python-2.7.15/Modules/_json.c:1367: alloc_fn: Storage is returned from
allocation function "PyString_FromStringAndSize".
Python-2.7.15/Objects/stringo
Change by Charalampos Stratakis :
--
keywords: +patch
pull_requests: +12300
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
New submission from Charalampos Stratakis :
Coverity scan reports this for bufferedio.c :
Error: RESOURCE_LEAK (CWE-772): [#def23]
Python-2.7.15/Modules/_io/bufferedio.c:1353: alloc_fn: Storage is returned from
allocation function "PyString_FromStringAndSize".
Python-2.7.
Change by Charalampos Stratakis :
--
keywords: +patch
pull_requests: +12298
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Charalampos Stratakis :
--
nosy: +mark.dickinson, vstinner
___
Python tracker
<https://bugs.python.org/issue36262>
___
___
Python-bugs-list mailin
New submission from Charalampos Stratakis :
Coverity report on dtoa.c. It was run on python2 but the same code resides on
python3.
Error: RESOURCE_LEAK (CWE-772): [#def89]
Python-2.7.15/Python/dtoa.c:1846: alloc_fn: Storage is returned from allocation
function "s2b".
Python-2.7
New submission from Charalampos Stratakis :
Coverity scan reports a leak on _hotshot.c:
Python-2.7.15/Modules/_hotshot.c:442: alloc_arg: "unpack_string" allocates
memory that is stored into "s1".
Python-2.7.15/Modules/_hotshot.c:329:5: alloc_fn: Storage is returned from
Change by Charalampos Stratakis :
--
keywords: +patch
pull_requests: +12161
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
New submission from Charalampos Stratakis :
There are two places [0][1] in the code where NULL is returned but the fd
handle is not closed.
[0] https://github.com/python/cpython/blob/2.7/Modules/linuxaudiodev.c#L129
[1] https://github.com/python/cpython/blob/2.7/Modules/linuxaudiodev.c#L133
Change by Charalampos Stratakis :
--
keywords: +patch
pull_requests: +12108
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Charalampos Stratakis added the comment:
Also the change from PyUnicode_FromStringAndSize to PyBytes_FromStringAndSize
happened here: https://bugs.python.org/issue8966
--
___
Python tracker
<https://bugs.python.org/issue36
New submission from Charalampos Stratakis :
Coverity scan on python2 resulted in this error.
Python-2.7.15/Modules/_ctypes/cfield.c:1297: alloc_fn: Storage is returned from
allocation function "PyString_FromString".
Python-2.7.15/Objects/stringobject.c:143:5: alloc_fn: Storage i
Change by Charalampos Stratakis :
--
nosy: +vstinner
___
Python tracker
<https://bugs.python.org/issue13096>
___
___
Python-bugs-list mailing list
Unsubscribe:
Charalampos Stratakis added the comment:
It seems the python2 backport was incomplete as a PyMem_Free is missing, making
buf leak.
--
nosy: +cstratak
___
Python tracker
<https://bugs.python.org/issue13
Change by Charalampos Stratakis :
--
pull_requests: +12107
___
Python tracker
<https://bugs.python.org/issue13096>
___
___
Python-bugs-list mailing list
Unsub
1 - 100 of 293 matches
Mail list logo