Michael Felt added the comment:
I had tried “wb+”, not “w+b”. Is there a difference? I forget if I tried just
“w+”.
But I’ll do them anyway/again to be sure.
Sent from my iPhone
> On 4 Jan 2019, at 23:43, STINNER Victor wrote:
>
>
> Change by STINNER Victor :
>
>
&g
Michael Felt added the comment:
On 04/01/2019 23:42, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> Does the test pass if you open the file in read+write ("w+b") mode rather
> than write-only ("wb") mode?
>
> I'm talking about this li
Michael Felt added the comment:
On 07/01/2019 15:46, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> Since you are getting indentation error, I'm not sure about your test. Can
> you please apply the patch below and run again test_eintr? Does it still fail
>
Michael Felt added the comment:
On 08/01/2019 15:40, Ayappan wrote:
> Ayappan added the comment:
>
> Not sure what went wrong here.
> I used gcc & g++ and didn't hit this issue.
>
> --
>
> ___
> Python tracker
&
New submission from Michael Felt :
By default AIX builds 32-bit applications - and the combined .data, .bss and
.stack areas share one memory segment of 256 Mbyte.
This can be modified by either specifying a larger value for maxdata during
linking (e.g., with LDFLAGS=-bmaxdata:0x4000) or
Change by Michael Felt :
--
keywords: +patch
pull_requests: +11029
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35704>
___
___
Py
New submission from Michael Felt :
Hi all,
as we get closer to having the current tests all patched I want to have a place
to post new "failures" - since the BOT process is unable to report regressions
before all tests are passing for a time.
Initially, the tests run normally,
Michael Felt added the comment:
Well, I can close this again - whatever was wrong with test_xml_etree_c
disappeared - and a cursory look at test_os reveals that the issue might be the
time lag between the NFS server where the temp files are made and the "local"
sense of time.
M
Change by Michael Felt :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue35735>
___
___
Python-bugs-list
Michael Felt added the comment:
On 07/01/2019 15:46, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> Since you are getting indentation error, I'm not sure about your test. Can
> you please apply the patch below and run again test_eintr? Does it s
New submission from Michael Felt :
I see in the bot history that test_bdb is now failing on AIX
https://buildbot.python.org/all/#/builders/161/builds/718/steps/4/logs/stdio
== CPython 3.8.0a0 (heads/master:a37f52436f, Jan 15 2019, 22:53:01) [C]
== AIX-1-00C291F54C00-powerpc-32bit big-endian
Michael Felt added the comment:
I’ll make a new PR and delete the news entry.
Sent from my iPhone
> On 15 Jan 2019, at 11:23, STINNER Victor wrote:
>
>
> STINNER Victor added the comment:
>
>> On AIX the test for flock() passes, but the test for lockf() fails: (...
Michael Felt added the comment:
Done.
> On 1/15/2019 11:23 AM, STINNER Victor wrote:
> I would prefer to simply skip the lockf() test rather than ignoring
> PermissionError for flock() and lockf() on all platforms. Can you please
> write a PR for that?
>
> There is no
New submission from Michael Felt :
Last August I started running a bot for AIX using xlc_r as the compiler, rather
than gcc that the other AIX bot uses.
Initially, I had no issues with the test_multiprocess* tests, but of late (last
two+ months I am guessing) I have been having regular
Change by Michael Felt :
--
title: test_multiprocessing_* tests - success versus fail varies over time ->
test_multiprocessing_* - crash in PyDict_GetItem - segmentation error
___
Python tracker
<https://bugs.python.org/issu
Michael Felt added the comment:
OK, I have gone as far back as "where" in dbx can bring me.
Could this, somehow, be related with changes made in issue-33015 ?
In any case, does it seem correct that "pthread_wrapper(void *arg) can be
correct if arg is nil?
+15
Michael Felt added the comment:
OK. being more specific about the test situation.
When I run ./python -m test test_multiprocessing_fork all is fine. However,
when I run it as: ./python -m test -j2 test_multiprocessing_main_handling
test_multiprocessing_fork
Michael Felt added the comment:
After enabling PYTHONTHREADDEBUG=1 I got the dprintf output.
I added line info (as fixed text) asin:
Python/thread_pthread.h:
+511 PyLockStatus
+512 PyThread_acquire_lock_timed(PyThread_type_lock lock, PY_TIMEOUT_T
microseconds,
+513
Michael Felt added the comment:
Update:
buildbot@x064:[/home/buildbot/buildarea/3.x.aixtools-aix-power6/issue]./python
-m test -v test_bdb
== CPython 3.8.0a0 (heads/master-dirty:0785889468, Jan 30 2019, 16:16:31) [C]
== AIX-1-00C291F54C00-powerpc-32bit big-endian
== cwd:
/home/buildbot
Michael Felt added the comment:
OK. New info.
Back in the time of issue 34347 I installed some extra filesets to support
UTF-8 on the virtual machine (aka partition) that I have the bot on.
On systems where this fileset is not installed this test does not fail.
Shall dig further - in a
Michael Felt added the comment:
On 14/02/2019 23:57, Indra Talip wrote:
> Indra Talip added the comment:
>
> The current code and proposed changes use 'netstat -ia' to find the node
> however if netstat needs to perform a reverse DNS query to resolve some
> interfac
Michael Felt added the comment:
OK. I have narrowed it down to this:
when
LANG=en_US.8859-15
the test fails.
root@x064:[/home/root]grep LANG /etc/environment
LANG=en_US
And now it passes.
--
___
Python tracker
<https://bugs.python.
Michael Felt added the comment:
Some record keeping - to keep track of when this regression first appeared on
the bot:
buildername POWER6 AIX 3.x Builder
buildnumber 718 Build
codebaseBuild
event pushChange
github_distinct trueChange
got_revision
Change by Michael Felt :
--
pull_requests: +11940
___
Python tracker
<https://bugs.python.org/issue35633>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Felt added the comment:
The PR's have been merged. Many thanks.
Closing this issue and looking forward.
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.
Michael Felt added the comment:
As far as 'master' is concerned, this has been resolved, so I'll close it
myself.
--
stage: -> resolved
status: open -> closed
versions: +Python 3.8 -Python 3.4
___
Python tracker
<
Michael Felt added the comment:
Again - after switching the env variable LANG to the 'default' everything works
as expected.
Leaving it open as a regression - because everything was working with a
non-default setting.
When I have more time I'll do a git bisect to try an
New submission from Michael Felt :
On a system using an older version of gcc (v5.7.4) I get an error: (also AIX
6.1)
gcc -pthread -Wno-unused-result -Wsign-compare -g -O0 -Wall -O
-std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter
-Wno-missing-field-initializers -Werror
Michael Felt added the comment:
correction - gcc version is v4.7.4
--
___
Python tracker
<https://bugs.python.org/issue36034>
___
___
Python-bugs-list mailin
Michael Felt added the comment:
I am still trying to get further with this, but I won't get far enough without
some help on how to best dig deeper.
For one, it should be leaving a core dump, but it never seems to leave the core
dump in the working directory. I know it is doing core
Michael Felt added the comment:
Another message that surprises me is:
Warning -- multiprocessing.process._dangling was modified by
test_multiprocessing_spawn
Before: <_weakrefset.WeakSet object at 0x3076e810>
After: <_weakrefset.WeakSet object at 0x3076e390>
Normally
Michael Felt added the comment:
Also - this looks like a core dump was 'seen', but later removed.
Warning -- files was modified by test_multiprocessing_forkserver
Before: []
After: ['core']
What can I change so that ot does not c
Michael Felt added the comment:
xlc has an option -qsource that creates output like this - first showing
the code with macro, then showing the expansion
>>>>> SOURCE SECTION <<<<<
...
16 | dev = st.st_dev;
17 | minor = minor(dev);
Michael Felt added the comment:
Curious.
First pass: using python2.7.12 also hanged as program, on the close()
second pass: interactive - do the read first, then the close - seems to work:
root@x064:[/data/prj/python/issues/29545]cat hello.py
#!/usr/bin/env python
import errno
import os
Michael Felt added the comment:
I see I already asked howto better utilize this info:
ConnectionRefusedError: [Errno 79] Connection refused
Warning -- files was modified by test_multiprocessing_fork
Before: []
After: ['core']
-- so, more specific -- which module, or file, is
New submission from Michael Felt :
Only marking Python3.8, but this is a historical issue I have ignored as long
as possible.
There are many - ancient and recent issues open around the extension module
_curses - and over the years it appears many assumptions have come into the
code (such as
Change by Michael Felt :
--
keywords: +patch
pull_requests: +12197
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue36210>
___
___
Py
Michael Felt added the comment:
Could this also be backported to 3.7 and 3.6 please?
--
versions: +Python 3.6, Python 3.7
___
Python tracker
<https://bugs.python.org/issue35
Michael Felt added the comment:
Could this also be backported to 3.6 and 3.7 please?
--
versions: +Python 3.6, Python 3.7
___
Python tracker
<https://bugs.python.org/issue34
Michael Felt added the comment:
could this be backported to versions 3.7, and if applicable, to version 3.6
--
___
Python tracker
<https://bugs.python.org/issue34
Michael Felt added the comment:
Could this also be backported to version 3.6?
--
versions: +Python 3.6
___
Python tracker
<https://bugs.python.org/issue35
Michael Felt added the comment:
Could this also be backported to Version 3.6?
--
versions: +Python 3.6
___
Python tracker
<https://bugs.python.org/issue34
Michael Felt added the comment:
Could this also be backported to Version 3.7 and 3.6?
--
versions: +Python 3.6, Python 3.7
___
Python tracker
<https://bugs.python.org/issue34
Michael Felt added the comment:
Could this also be backported to Version 3.7 and 3.6 (I do not expect it to be
backported to 2.7, but I had mistakenly removed it 2.7 when I changed it to 3.8
- and should have added 3.6 and 3.7 then).
--
versions: +Python 2.7, Python 3.6, Python 3.7
Michael Felt added the comment:
Could this alos be backported to Version 3.7 and 3.6 - thx!
--
versions: +Python 3.6, Python 3.7
___
Python tracker
<https://bugs.python.org/issue34
Michael Felt added the comment:
Could this be backported to version 3.7?
--
___
Python tracker
<https://bugs.python.org/issue34347>
___
___
Python-bugs-list m
Michael Felt added the comment:
On 11/03/2019 09:42, Stéphane Wirtel wrote:
> Stéphane Wirtel added the comment:
>
> Hi Michael,
>
> I think no, because 3.6 is in security mode.
Clear reason. Maybe makes the baclport to 3.7 more opportune. Thx for
the reply!
>
>
Michael Felt added the comment:
On 10/03/2019 19:43, Michael Felt wrote:
> Michael Felt added the comment:
>
> Could this alos be backported to Version 3.7 and 3.6 - thx!
As 3.6 is in security mode - I guess only 3.7 then.
> --
> versions: +Python
Michael Felt added the comment:
On 10/03/2019 19:40, Michael Felt wrote:
> Michael Felt added the comment:
>
> Could this also be backported to Version 3.7 and 3.6 (I do not expect it to
> be backported to 2.7, but I had mistakenly removed it 2.7 when I changed it
> to 3.8 -
Michael Felt added the comment:
On 10/03/2019 19:37, Michael Felt wrote:
> Michael Felt added the comment:
>
> Could this also be backported to Version 3.6?
Ignore this since 3.6 is in security mode.
>
> --
> versions: +Python 3.6
>
>
Michael Felt added the comment:
On 10/03/2019 19:31, Michael Felt wrote:
> Michael Felt added the comment:
>
> could this be backported to versions 3.7, and if applicable, to version 3.6
Only 3.7 - As 3.6 is in security mode.
>
> --
>
> ___
Michael Felt added the comment:
On 10/03/2019 19:34, Michael Felt wrote:
> Michael Felt added the comment:
>
> Could this also be backported to version 3.6?
>
> --
> versions: +Python 3.6
Not to worry: As 3.6 is in security mode.
>
>
Michael Felt added the comment:
On 10/03/2019 19:25, Michael Felt wrote:
> Michael Felt added the comment:
>
> Could this also be backported to 3.7 and 3.6 please?
Only 3.7 I guess - As 3.6 is in security mode.
>
> --
> versions: +Pyth
Change by Michael Felt :
--
versions: -Python 3.6
___
Python tracker
<https://bugs.python.org/issue35704>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Michael Felt :
--
versions: -Python 3.6
___
Python tracker
<https://bugs.python.org/issue34373>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Michael Felt :
--
versions: -Python 3.6
___
Python tracker
<https://bugs.python.org/issue11192>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Michael Felt :
--
versions: -Python 3.6
___
Python tracker
<https://bugs.python.org/issue34720>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Felt added the comment:
>From memory I do not believe this is still a problem, at least on Python3.
There was recently a different issue (do not recall the #) where there was an
issue with CXX regardless of compiler.
In any case, the apporach I would recommend would be to export
Michael Felt added the comment:
I have looked at this briefly.
I would consider it a regression, or a spurious incident as the bot run before
(https://buildbot.python.org/all/#/builders/10/builds/2223) and after
(https://buildbot.python.org/all/#/builders/10/builds/2225) do not show this
Michael Felt added the comment:
Updating this to not only correct the failure of 3rd-party library ncurses
(while IBM curses builds with no issue) to also stop announcing that the
optional modules osaudiodev and spwd have not been built.
Neither are supported on AIX - so they will never be
Change by Michael Felt :
--
versions: +Python 3.7
___
Python tracker
<https://bugs.python.org/issue36210>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Michael Felt :
--
title: correct AIX logic in setup.py for non-existant optional extensions ->
correct AIX logic in setup.py for (non-existant) optional extensions
___
Python tracker
<https://bugs.python.org/issu
New submission from Michael Felt :
sys.platform returns "aix[3|4|4|5|6|7"
AIX 3 and AIX 4 are no longer around, in any supported form, so references to
these specific releases is pointless.
This will remove the (two) places where they are still referenced.
--
compone
Change by Michael Felt :
--
keywords: +patch
pull_requests: +12587
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue36503>
___
___
Py
New submission from Michael Felt :
This is something that probably shouts - boring - but back in 2012 it was a hot
topic for linux2 and linux3.
Maybe - as far back as 1996 (when AIX4 was new) "aix3" and "aix4" made sense.
Whether that is true, or not - is pointless thes
Michael Felt added the comment:
On 10/04/2019 17:05, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> I like the idea. Would you like to propose a patch? I suggest to only make
> such change in Python 3.8 and properly document it.
>
> --
Michael Felt added the comment:
On 09/04/2019 18:51, STINNER Victor wrote:
> New submission from STINNER Victor :
>
> https://buildbot.python.org/all/#/builders/10/builds/2389
>
> 0:45:36 [412/420/1] test_venv crashed (Exit code 1)
> Timeout (0:15:00)!
> Thread 0x0
Change by Michael Felt :
--
pull_requests: +12704
___
Python tracker
<https://bugs.python.org/issue28009>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Felt added the comment:
Was:
root@x064:[/data/prj/python/python3-3.8]./python
Python 3.8.0a3+ (heads/bpo-28009-2-dirty:2fb2bc81c3, Apr 11 2019, 07:09:55) [C]
on aix6
Type "help", "copyright", "credits" or "license" for more informatio
Change by Michael Felt :
--
keywords: +patch
pull_requests: +12714
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue36588>
___
___
Py
Michael Felt added the comment:
On 10/04/2019 18:49, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> "I am looking into this - but as it seems to have gone away again - is
> there a simple way to get that code back, and/or see what the diff is,
> before/badr
Michael Felt added the comment:
On 12/04/2019 10:28, Michael Felt wrote:
> Michael Felt added the comment:
>
> On 10/04/2019 18:49, STINNER Victor wrote:
>> STINNER Victor added the comment:
>>
>> "I am looking into this - but as it seems to have gone away aga
Michael Felt added the comment:
On 12/04/2019 16:16, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> Do you want to work on a change to replace sys.platform.startswith("aix") to
> cleanup the stdlib and tests? Not sure if it'
Michael Felt added the comment:
On 12/04/2019 17:34, STINNER Victor wrote:
> STINNER Victor added the comment:
>
>> But, should I just continue standard practice (sys.platform), or would
>> this be a moment to move towards platform.system() (i.e., set the
>> exampl
New submission from Michael Felt :
Back in 2012 (issue12326 and issue12795), and just recently (issue36588)
sys.platform has been modified (and documented) to not return the platform
version.
Additionally, the recommendation is to use the form
sys.platform.startswith() - to continue to be
Michael Felt added the comment:
On 12/04/2019 23:16, Michael Felt wrote:
> Agreed, in case of doubt - leave alone (never change a winning team).
>
> And, to make it a short reply - I'll get started, and we see where it
> leads us.
I opened issue36624 (https://bugs.pyth
Michael Felt added the comment:
I took a peak at test.support.
a) I see that while many tests import test.support, or from test.support import
- not all tests use this.
b) I see that only 35 .py files in Lib/test have the string
sys.platform.startswith, and there are 76 files that have
Michael Felt added the comment:
On 14/04/2019 18:04, Michael Felt wrote:
> Is this a good way to get started?
So, as an example - seems to be many attributes in test/support/__init__.py
diff --git a/Lib/test/support/__init__.py b/Lib/test/support/__init__.py
index 5bd15a2..e20567f 100
Michael Felt added the comment:
On 15/04/2019 11:50, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> support.is_android has two flaws:
>
> * it's a constant: it must be spelled as UPPER CASE
> * I dislike "is_" prefix: "MS_WINDOWS" c
Change by Michael Felt :
--
keywords: +patch
pull_requests: +12768
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue36624>
___
___
Py
Michael Felt added the comment:
OK. I have been chewing my bone. I hope not too much indigestion.
Who has a pointer for the antacid?
Getting base branch for PR ... origin/master
Getting the list of files that have been added/changed ... 72 files
Fixing Python file whitespace ... Traceback
Michael Felt added the comment:
Never mind - typos in the files I did work on. iow, I found a way to get the
filename, and am cleaning up the errors.
--
___
Python tracker
<https://bugs.python.org/issue36
Michael Felt added the comment:
On 17/04/2019 14:02, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> The same bug is back:
> https://buildbot.python.org/all/#/builders/10/builds/2443
>
> Warning -- files was modified by test_threading
> Before:
New submission from Michael Felt :
My AIX bot has been very consistent - only the multiprocessing tests failing
when run by bot, but 4 or 5 days ago 3 to 5 additional tests - that, afaik, had
never failed before, are now failing.
These may also be compiler related specifics, or the presence
Michael Felt added the comment:
On 22/04/2019 14:15, Inada Naoki wrote:
> Inada Naoki added the comment:
>
> Maybe, XLC doesn't support -D name. -Dname should be used instead.
Excellent hint: the diff between bot run 1013 and run 1014 reveals:
diff --git a/setup.py b/
Michael Felt added the comment:
On 22/04/2019 21:14, Steve Dower wrote:
> Steve Dower added the comment:
>
> I like this, though I don't like using the platform module here and would
> prefer sys.platform to be canonical (until there's a need to differentiate -
> e
Michael Felt added the comment:
On 23/04/2019 17:53, Steve Dower wrote:
> Steve Dower added the comment:
>
>> Being 'runtime' rather than 'buildtime' seemed more precise - tests that
>> are not meant to be build-time dependent use run-time status whil
Change by Michael Felt :
--
pull_requests: +5012
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue27435>
___
___
Python-bugs-list mai
Michael Felt added the comment:
On 30/07/2016 02:51, Martin Panter wrote:
> Martin Panter added the comment:
>
>
> ./python -m unittest -v ctypes.test.test_bitfields
>
> What I am suggesting as a fix is to change line 381 from plain “int” to
> “signed int”, and 382 to “si
Michael Felt added the comment:
On 04/08/2016 10:58, Martin Panter wrote:
> Martin Panter added the comment:
>
> Okay, so to be clear, I am assuming XLC supports all of the following fields,
> and uses unsigned bit fields by default:
>
> struct UNSIGNED_BITS {
>
Change by Michael Felt :
--
pull_requests: +5020
___
Python tracker
<https://bugs.python.org/issue27643>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Felt added the comment:
@panter - your patch seems to be working well. Thanks.
PR 5164 submitted for review
--
___
Python tracker
<https://bugs.python.org/issue27
New submission from Michael Felt :
in issue25582 - the issue is not (yet) resolved. Perhaps this one can be closed
and issue25582 reopened.
Both from python2-2.7.14 and "git master" I am getting:
michael@x071:[/data/prj/python/git/gcc-python3-3.7]./python -m u
Change by Michael Felt :
--
keywords: +patch
pull_requests: +5037
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue28009>
___
___
Py
Michael Felt added the comment:
PR added, please review.
--
___
Python tracker
<https://bugs.python.org/issue28009>
___
___
Python-bugs-list mailing list
Unsub
Michael Felt added the comment:
FYI: - On AIX, no uuid_create support:
./python -m unittest -v test.test_uuid
...
Ran 48 tests in 0.261s
OK (skipped=37)
On AIX 6.1 (with ctypes, without _uuid)
./python -m unittest -v test.test_uuid
...
Ran 48 tests in 0.274s
OK (skipped=32)
On AIX 6.1
Michael Felt added the comment:
Thanks for the clarification.
Being curious, is there a way to see what the size of the cache is? I want to
believe, but i do not have the impression memory is being reallocated to later
users. My gut feeling is that the code change permits repeated calls to
Michael Felt added the comment:
On 14/01/2018 22:01, Antoine Pitrou wrote:
> Antoine Pitrou added the comment:
>
> Is nohup required in the example you just posted or is that a red herring?
>
> --
>
> ___
> Python tracker
&g
Michael Felt added the comment:
After even more years - I see the same test failing, just a bit different.
And, others
in short:
./python Lib/test/test_distutils.py
...
Ran 245 tests in 10.337s
FAILED (errors=7, skipped=31)
I have managed to get this to:
FAILED (errors=1, skipped=37
Change by Michael Felt :
--
versions: +Python 3.7 -Python 3.2
___
Python tracker
<https://bugs.python.org/issue11191>
___
___
Python-bugs-list mailing list
Unsub
301 - 400 of 737 matches
Mail list logo
