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.
>
> --
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
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 :
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 :
--
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
Change by Michael Felt :
--
versions: +Python 3.7
___
Python tracker
<https://bugs.python.org/issue36210>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
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
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 exp
Change by Michael Felt :
--
versions: -Python 3.6
___
Python tracker
<https://bugs.python.org/issue34720>
___
___
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/issue34373>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Michael Felt :
--
versions: -Python 3.6
___
Python tracker
<https://bugs.python.org/issue35704>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
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: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: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: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: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 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:
Could this be backported to version 3.7?
--
___
Python tracker
<https://bugs.python.org/issue34347>
___
___
Python-bugs-list m
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 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 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.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.6?
--
versions: +Python 3.6
___
Python tracker
<https://bugs.python.org/issue35
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 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 also be backported to 3.7 and 3.6 please?
--
versions: +Python 3.6, Python 3.7
___
Python tracker
<https://bugs.python.org/issue35
Change by Michael Felt :
--
keywords: +patch
pull_requests: +12197
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue36210>
___
___
Py
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
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 doing
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:
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 cleanup the core file
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>
Norma
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 dump
Michael Felt added the comment:
correction - gcc version is v4.7.4
--
___
Python tracker
<https://bugs.python.org/issue36034>
___
___
Python-bugs-list mailin
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:
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 and establish
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
<https://bugs.p
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.org/i
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:
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
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:
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
> interfaces this ma
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
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:
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:
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:
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
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
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
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
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: (...
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:
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 i
Change by Michael Felt :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue35735>
___
___
Python-bugs-list
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 t
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,
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 :
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
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
> &
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
> with
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 line:
&
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:
Further along - however, I never get to the "link" routine.
Again, this is likely a pandas coding issue - currently python is calling xlc_r
..., but when I manually modify it to xlC_r I get the same error.
xlc_r -D_LARGE_FILES -O -I/opt/include -O
Michael Felt added the comment:
On 04/01/2019 17:08, Kevin wrote:
> Kevin added the comment:
>
> Ah. We always compile with GCC, so would not have hit that particular problem.
>
> --
>
> ___
> Python tracker
> <http
Michael Felt added the comment:
While the PR probably solves this - there is a 'bug' in pandas (I expect) that
prevents me from completing the test - as, I expect LONG before the .cpp source
is to be compiled - there is a error because a wrong flag is passed to the
compiler (-Wno-unused
Change by Michael Felt :
--
components: -IO
___
Python tracker
<https://bugs.python.org/issue35633>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Michael Felt :
--
pull_requests: +10842, 10843, 10845
___
Python tracker
<https://bugs.python.org/issue35189>
___
___
Python-bugs-list mailin
Change by Michael Felt :
--
pull_requests: +10842, 10843, 10844, 10845
___
Python tracker
<https://bugs.python.org/issue35189>
___
___
Python-bugs-list mailin
Change by Michael Felt :
--
pull_requests: +10842, 10843
___
Python tracker
<https://bugs.python.org/issue35189>
___
___
Python-bugs-list mailing list
Unsub
Change by Michael Felt :
--
pull_requests: +10842
___
Python tracker
<https://bugs.python.org/issue35189>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Michael Felt :
--
keywords: +patch, patch
pull_requests: +10840, 10841
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Michael Felt :
--
keywords: +patch
pull_requests: +10840
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35633>
___
___
Py
Michael Felt added the comment:
After reading the PEP I realized it is much simpler. The test is for interrupts
that occur at a low-level - and not for permission issues. The test is failing
because there is a permission issue, not a missed interrupt issue. Modifying
the code to: (see line
New submission from Michael Felt :
test_eintr fails on AIX since fcntl functions were modified
In issue35189 the fnctl() module was modified so that the EINTR interruption
should be retried automatically.
On AIX the test for flock() passes, but the test for lockf() fails
Michael Felt added the comment:
p.s., removed 2.7 and 3.6 as too old for any interest.
--
versions: -Python 2.7, Python 3.6
___
Python tracker
<https://bugs.python.org/issue28
Michael Felt added the comment:
As I am not clear on where to have a more general discussion (in a PR
conversation) or here - going to start here because I cannot figure out which
comment in the PR to reply to.
Generally, before modifying the test_uuid.py to based tests on
uuid
Michael Felt added the comment:
On 27/12/2018 15:48, Michael Felt wrote:
> Michael Felt added the comment:
>
> The "improved" output after getting back to "latest" commit:
>
> == CPython 3.8.0a0 (heads/master-dirty:34ae04f74d, Dec 27 2018, 14:05:08) [C]
&g
Michael Felt added the comment:
The "improved" output after getting back to "latest" commit:
== CPython 3.8.0a0 (heads/master-dirty:34ae04f74d, Dec 27 2018, 14:05:08) [C]
== AIX-1-00C291F54C00-powerpc-32bit big-endian
== cwd: /data/prj/python/python3-3.8/build/test_py
Michael Felt added the comment:
Forgot to include the test failure message:
==
FAIL: test_all (test.test_eintr.EINTRTests)
--
Traceback (most recent call
Michael Felt added the comment:
I have not looked at 3.6, but I have bisected the 3.7 and 3.8 branches for AIX.
I get:
On 3.7 Branch:
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[56742f1eb05401a27499af0ccdcb4e4214859fd1] [3.7] bpo-35189: Retry fnctl calls
on EINTR (GH
Change by Michael Felt :
--
pull_requests: +10576
___
Python tracker
<https://bugs.python.org/issue34897>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Michael Felt :
--
pull_requests: +10576, 10577
___
Python tracker
<https://bugs.python.org/issue34897>
___
___
Python-bugs-list mailing list
Unsub
Change by Michael Felt :
--
title: core logic of uuid.getnode() is broken for AIX - all versions -> core
logic of uuid.getnode() is broken for netstat
___
Python tracker
<https://bugs.python.org/issu
Michael Felt added the comment:
Historically, I started this issue because I saw that none of the calls made in
uuid.py were working for AIX.
I also assumed that they ALL worked already, at least somewhere.
a) one cause is the difference between AIX and (all) others was the letter
chosen
Michael Felt added the comment:
Still getting the same errors, even with 64-bit build, so still not close to
testing the actual problem.
FYI: last time I build pandas the version was 0.19.0 - then it was 'simple'.
Anyway, short of a simple (test) python module that includes c++ code, I'll
Michael Felt added the comment:
Getting farther - after "hacking" pandas setup.py to not force a gcc flag.
Still not getting as far, I think, as the initial poster.
...
/opt/include/python3.8dm -c pandas/_libs/parsers.c -o
build/temp.aix-6.1-3.8-pydebug/pandas/_libs/parsers.o
x
Change by Michael Felt :
--
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issue35198>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Felt added the comment:
There are, perhaps, other issues as well.
After a build of "master"
a) pip3 install pandas
- failed to find/download and build numpy
- after "manual" pip3 install numpy and got to " six, python-dateutil, pytz,
pandas"
T
Michael Felt added the comment:
Thx.
So, while "" is not None (i.e., "" is not False), it does test as a Boolean
expression as 'False' so the test for None or "" is the same as testing for ""
(but not the same as testing for None).
I accep
Michael Felt added the comment:
The AIX build-bots thank you. Back to "failed-test" status.
1721...failed test (failure)
1720...failed compile (failure)
--
___
Python tracker
<https://bugs.python.o
Michael Felt added the comment:
FYI: On my manual build server I have coreutils "install" installed, and it
seems install-sh is not called in that case (which is why I never saw with
manual builds)
FYI: There is also an issue (I hope side-effect) that pyexpat is not building
whi
Michael Felt added the comment:
This is closed, however, since this was merged the AIX buildbots have failed.
This is because the file mode bits lack the -x
root@x066:[/data/prj/python/git/cpython-master]find . -name install-sh -ls
148833829 16 -rw-r--r-- 1 root felt 15368
Michael Felt added the comment:
> On 10/26/2018 5:36 PM, Tal Einat wrote:
> Tal Einat added the comment:
>
> I'm not sure that the resolution currently suggested, changing
> compiler.set_executables(), is the right way to go.
>
> This change to distutils is
Michael Felt added the comment:
re; the current status of PR8672 - which I shall probably close as it no longer
merges.
@taleinat re: the need for lambda
As _find_mac_netstat() is only called once the need for the last two arguments
may be unnecessary. My reason for including them
Michael Felt added the comment:
On 16/10/2018 21:35, Ned Deily wrote:
> Ned Deily added the comment:
>
> I'm glad it works. Any object to closing this issue then?
I have no objection. Should I do that?
>
> --
> resolution: -> not a bug
> stage: -> resolve
Michael Felt added the comment:
using CC=gcc ./configure works fine
And, this does not appear to be a regression:
HEAD is now at 1bf9cc5 3.7.0 final
$ cd ../python3-3.7.0
$ ./configure
checking for git... found
checking build system type... powerpc-ibm-aix7.2.0.0
checking host system type
Michael Felt added the comment:
I'll compare with the 3.7.0. As I did not have access to gcc then, would have
never seen it.
Yesterday I used --with-gcc, today I'll use CC=gcc and update after I know more.
--
___
Python tracker
<ht
301 - 400 of 756 matches
Mail list logo
