[issue41625] Add splice() to the os module

2020-11-26 Thread Michael Felt


Michael Felt  added the comment:

This is still broken.

Since this was included in master - the AIX buildbot is failing to compile 
(https://buildbot.python.org/all/#/builders/438/builds/391 and 
https://buildbot.python.org/all/#/builders/302/builds/377)

Strangely enough - the first bot continues to fail compile at the same location 
- while the second bot (running in a different environment) starting passing 
compile and all tests starting with 
https://buildbot.python.org/all/#/builders/302/builds/406.

Note: bot 1 is using what I call (personal opinion) a mixed environment with 
some libraries coming from OSS packages and some from IBM AIX. bot 2 - relies 
on IBM AIX libraries.

++
Note: manual build on same system as bot 1 using gcc - gives same error:

aixtools@gcc119:[/home/aixtools/cpython/cpython-master]make V=1
gcc -pthread -c -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv 
-O3 -Wall  -O  -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter 
-Wno-missing-field-initializers -Werror=implicit-function-declaration 
-fvisibility=hidden  -I./Include/internal  -I. -I./Include-DPy_BUILD_CORE  
-DABIFLAGS='""'-o Python/sysmodule.o ./Python/sysmodule.c
gcc -pthread -c -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv 
-O3 -Wall  -O  -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter 
-Wno-missing-field-initializers -Werror=implicit-function-declaration 
-fvisibility=hidden  -I./Include/internal  -I. -I./Include-DPy_BUILD_CORE 
-o Modules/config.o Modules/config.c
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 
-Wall  -O  -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter 
-Wno-missing-field-initializers -Werror=implicit-function-declaration 
-fvisibility=hidden  -I./Include/internal  -I. -I./Include
-DPy_BUILD_CORE_BUILTIN  -DPy_BUILD_CORE_BUILTIN -I./Include/internal -c 
./Modules/posixmodule.c -o Modules/posixmodule.o
./Modules/posixmodule.c: In function 'os_splice_impl':
./Modules/posixmodule.c:10429:15: error: implicit declaration of function 
'splice'; did you mean 'plock'? [-Werror=implicit-function-declaration]
 ret = splice(src, p_offset_src, dst, p_offset_dst, count, flags);
   ^~
   plock
cc1: some warnings being treated as errors
make: 1254-004 The error code from the last command is 1.

* On same system, using xlc-v13, the build completes normally.

--
nosy: +Michael.Felt

___
Python tracker 
<https://bugs.python.org/issue41625>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42323] [AIX] test_math: test_nextafter(float('nan'), 1.0) does not return a NaN on AIX

2020-11-17 Thread Michael Felt


Michael Felt  added the comment:

Yes, just probing, the version of gcc is irrelevant.

What I do believe is important is that bot run 374, 375 and 376 passed - On AIX 
7.1 TL4 SP8.

The failure starting with 377 is an undefined variable.

"./Modules/posixmodule.c", line 15146.53: 1506-045 (S) Undeclared identifier 
SPLICE_F_MOVE.
"./Modules/posixmodule.c", line 15147.57: 1506-045 (S) Undeclared identifier 
SPLICE_F_NONBLOCK.
"./Modules/posixmodule.c", line 15148.53: 1506-045 (S) Undeclared identifier 
SPLICE_F_MORE.

So, let's put this on hold. I'll get a new environment built up specific for 
testing python on AIX. Hopefully by Friday.

--

___
Python tracker 
<https://bugs.python.org/issue42323>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42323] [AIX] test_math: test_nextafter(float('nan'), 1.0) does not return a NaN on AIX

2020-11-16 Thread Michael Felt


Michael Felt  added the comment:

There seems to be a lot of interaction of OS level and compiler used.

* Waiting for the next bot run to get a different compiler.

+++
AIX 6.1.6 and older libraries - no test errors reported

AIX 7.1.4 and newer libraries - when using the binary built on 6.1.6 (AIX 6.1 
TL6) - no error

AIX 7.1.4, using xlc-v13.1.2 (try and buy version), same AIX level as the bot 
(7.1 TL4 SP8) - no error

Back to the bot: AIX 7.1 TL4 SP8 and gcc-4.7.4 - strange errors. See, e.g., 
https://buildbot.python.org/all/#/builders/302/builds/373/steps/5/logs/stdio 
with additional errors such as:

==
FAIL: testHypotAccuracy (test.test_math.MathTests) (hx='0x1.89d8c423ea0c6p+29', 
hy='0x1.d35dcfe902bc3p+29', x=825956484.4892814, y=980138493.1263355)
--
Traceback (most recent call last):
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/test_math.py", 
line 867, in testHypotAccuracy
self.assertEqual(hypot(x, y), z)
AssertionError: 1281747081.1271062 != 1281747081.127106

Waiting for bot run 374 - to see if the results change when the compiler 
changes.

I'll try moving the bot to another system - as the system the bot is on is more 
than just the bot. Maybe there are side-effects coming in, unexpectedly, from 
other sources. ** The two systems just mentioned are fresh installs.

--

___
Python tracker 
<https://bugs.python.org/issue42323>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42309] BUILD: AIX-64-bit segmentation fault using xlc-v11

2020-11-16 Thread Michael Felt


Michael Felt  added the comment:

For now, I am going to suggest closing this - as a bug in the xlc-v11 compiler 
- and not worth researching.

I am able to build the 3.9 distribution as well as the 3.10 master using the 
xlC-v13-1.3.2 (Try and Buy) version.

Thanks for thinking together!

--
title: BUILD: AIX-64-bit segmentation fault using xlc -> BUILD: AIX-64-bit 
segmentation fault using xlc-v11

___
Python tracker 
<https://bugs.python.org/issue42309>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42323] [AIX] test_math: test_nextafter(float('nan'), 1.0) does not return a NaN on AIX

2020-11-16 Thread Michael Felt


Michael Felt  added the comment:

I have been experimenting with different hardware and AIX versions.

When building on AIX 5.3 - and the oldest libraries - test_math passes.

When I run the test on POWER8, using either xlc or gcc test_math fails with 
just one element of the test.

When I run the test on POWER6 I get many more errors - that I never had before. 
These are all after OS updates (I was not going to build for AIX 5.3 any more).

An idea I have now - that may explain the sudden change in behavior is if the 
libraries have been optimized to always use the DFP (decimal floating point) 
internally - for what, from the application perspective - is the normal - no HW 
acceleration for FP - interface.

I know there are ways to 'discover' this, but I'll need to write some tests so 
that I can see - if linking to different libraries actuates DFP performance 
counters yes and no.

At this point - this feels like the a potential explanation.

--

___
Python tracker 
<https://bugs.python.org/issue42323>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42309] BUILD: AIX-64-bit segmentation fault using xlc

2020-11-16 Thread Michael Felt


Michael Felt  added the comment:

Added "using xlc" to description.

When I have a system that has 64-bit support for gcc - I'll verify that it 
works, or does not work, for me using gcc.

--
title: BUILD: AIX-64-bit segmentation fault -> BUILD: AIX-64-bit segmentation 
fault using xlc

___
Python tracker 
<https://bugs.python.org/issue42309>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42309] BUILD: AIX-64-bit segmentation fault

2020-11-10 Thread Michael Felt


Michael Felt  added the comment:

On a different server, different compiler (xlc-v13, mine is xlc-v11) it gets 
past this point.

So, perhaps it is a compiler issue.

As the second system is missing many 64-bit libraries - still cannot build 
64-bit Python-3.9.

Low priority - imho.

--

___
Python tracker 
<https://bugs.python.org/issue42309>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42309] BUILD: AIX-64-bit segmentation fault

2020-11-10 Thread Michael Felt


New submission from Michael Felt :

Successfully built and packaged the Python-3.9.0 distribution tar archive 
without modification - as 32-bit.

Repeating the same process with the following environment change:

 # export OBJECT_MODE=64

fails with a segmentation fault by the "first-phase" python executable:

```
../src/py39-3.9.0/Modules/makexp_aix Modules/python.exp "." 
libpython3.9.a
 xlc_r -Wl,-bE:Modules/python.exp -lld -o python Programs/python.o 
libpython3.9.a -lintl -ldl  -lm   -lm
 ./python -E -S -m sysconfig --generate-posix-vars ; if test $? -ne 0 ; 
then  echo "generate-posix-vars failed" ;  rm -f ./pybuilddir.txt ;  exit 1 ;  
fi
/bin/sh: 6291700 Segmentation fault(coredump)
make: 1254-004 The error code from the last command is 139.


Stop.
root@x066:[/data/prj/python/py39-3.9.0]./python -E -S -m sysconfig 
--generate-posix-vars
Segmentation fault(coredump)
root@x066:[/data/prj/python/py39-3.9.0]./python
Segmentation fault(coredump)
```

Will try to duplicate in a second environment.

--
components: Build
messages: 380654
nosy: Michael.Felt
priority: normal
severity: normal
status: open
title: BUILD: AIX-64-bit segmentation fault
type: crash
versions: Python 3.9

___
Python tracker 
<https://bugs.python.org/issue42309>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41401] Using non-ascii that require UTF-8 breaks AIX testing

2020-08-18 Thread Michael Felt


Michael Felt  added the comment:

As much as I wish I had the skills to do the cherry picking - I am not going to 
touch this.

The AIX bots for 3.9 branch continue to report broken for test_io (ENV change) 
- as they still wait for the backport for that branch!

--

___
Python tracker 
<https://bugs.python.org/issue41401>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40424] AIX: makexp_aix, parallel build (failures) and ld WARNINGS

2020-08-16 Thread Michael Felt

Michael Felt  added the comment:

If #19521 had been merged I would be all for closing this as a duplicate. 
However, if i have read all the comments correctly noone has tested the other 
pr. 

As the approaches are quite different I think both should be open until a 
decision is made on the better approach. 

Closing one (asap) is a good idea, especially if that leads to something being 
merged so this is finally repaired. 

Sent from my iPhone

> On 15 Aug 2020, at 23:07, Stefan Krah  wrote:
> 
> 
> Stefan Krah  added the comment:
> 
> I understand that both of you are in favor of #19521 (the patch of
> which I have not tried yet).
> 
> Can we close this as a duplicate? Please just reopen if you disagree.
> 
> --
> nosy: +skrah
> resolution:  -> duplicate
> stage: patch review -> resolved
> status: open -> closed
> superseder:  -> Parallel build race condition on AIX since python-2.7
> 
> ___
> Python tracker 
> <https://bugs.python.org/issue40424>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40424>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41461] test_pathlib assumes underlying filesystem permits creation with world-write permissions

2020-08-03 Thread Michael Felt


New submission from Michael Felt :

Two tests in test_pathlib test that the files created have mode o666 (rw-rw-rw).

However, on a filesystem (in my case NFS) configured to never permit global 
write - the test will always fail.

Is this something to be concerned about?

I can think of a few possible ways to react to an exception such as this, e.g., 
rather than 'FAIL' outright, try umask(2).



==
FAIL: test_open_mode (test.test_pathlib.PosixPathTest)
--
Traceback (most recent call last):
  File "/data/prj/python/src/py38-3.8.5/Lib/test/test_pathlib.py", line 2210, 
in test_open_mode
self.assertEqual(stat.S_IMODE(st.st_mode), 0o666)
AssertionError: 436 != 438

==
FAIL: test_touch_mode (test.test_pathlib.PosixPathTest)
--
Traceback (most recent call last):
  File "/data/prj/python/src/py38-3.8.5/Lib/test/test_pathlib.py", line 2223, 
in test_touch_mode
self.assertEqual(stat.S_IMODE(st.st_mode), 0o666)
AssertionError: 436 != 438

--


Just to verify it does work when on a 'local' filesystem.

cp -rp build /tmp/build
mv build build.nfs
ln -s /tmp/build build

== Tests result: SUCCESS ==

1 test OK.

Total duration: 7.8 sec
Tests result: SUCCESS

--
components: Tests
messages: 374725
nosy: Michael.Felt
priority: normal
severity: normal
status: open
title: test_pathlib assumes underlying filesystem permits creation with 
world-write permissions
type: behavior
versions: Python 3.10, Python 3.8, Python 3.9

___
Python tracker 
<https://bugs.python.org/issue41461>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41401] Using non-ascii that require UTF-8 breaks AIX testing

2020-07-29 Thread Michael Felt


Michael Felt  added the comment:

The 'master' branch bot is working again, the 3.9 branch is still broken, and 
the 3.8 branch seems, as yet, unaffected.

--

___
Python tracker 
<https://bugs.python.org/issue41401>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41401] Using non-ascii that require UTF-8 breaks AIX testing

2020-07-27 Thread Michael Felt

Michael Felt  added the comment:

Excellent!!

aixtools@gcc119:[/home/aixtools/cpython/cpython-master]git pr 21640
remote: Enumerating objects: 50, done.
remote: Counting objects: 100% (50/50), done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 58 (delta 46), reused 48 (delta 46), pack-reused 8
Unpacking objects: 100% (58/58), done.
>From https://github.com/python/cpython
 * [new ref] refs/pull/21640/head -> pr_21640

aixtools@gcc119:[/home/aixtools/cpython/cpython-master]./python -m test
test_io
0:00:00 Run tests sequentially
0:00:00 [1/1] test_io
test_io passed in 1 min

== Tests result: SUCCESS ==

1 test OK.

Total duration: 1 min
Tests result: SUCCESS

On 27/07/2020 16:16, Serhiy Storchaka wrote:
> Change by Serhiy Storchaka :
>
>
> --
> keywords: +patch
> pull_requests: +20781
> stage:  -> patch review
> pull_request: https://github.com/python/cpython/pull/21640
>
> ___
> Python tracker 
> <https://bugs.python.org/issue41401>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue41401>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue18280] Documentation is too personalized

2020-07-27 Thread Michael Felt


Change by Michael Felt :


--
keywords: +patch
pull_requests: +20780
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/21639

___
Python tracker 
<https://bugs.python.org/issue18280>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue18280] Documentation is too personalized

2020-07-27 Thread Michael Felt


Michael Felt  added the comment:

Thanks. afaik, double spacing is a 'feature' a programmer added to a
text processing language - of the WYSIWUG kind, because program's such
as troff/nroff
didn't need them. They, rather it, understood that a period followed by
a space indicated the end of a sentence.

On 26/07/2020 18:39, Serhiy Storchaka wrote:
> Serhiy Storchaka  added the comment:
>
> I think they are not required, but recommended.
>
> >From https://www.python.org/dev/peps/pep-0008/#comments:
>
>You should use two spaces after a sentence-ending period in multi- 
> sentence comments, except after the final sentence.
>
> >From https://www.python.org/dev/peps/pep-0012/#general:
>
>You must adhere to the Emacs convention of adding two spaces at the end of 
> every sentence.
>
> AFAIK in English typography the space after a sentence-ending period is 
> longer than spaces between words. In other European typographies they have 
> the same width.

I thought it was where type setters, classically, used the break between
the endings of a sentence - additional 'kerning' could be applied there.

Anyway - final question: does .rst reformat line-lingths, or does it
present everything literally - only adding ``embellishments``. I have
been thinking
it does both - and, yet another convention for sentence endings is to
always start a sentence on a new line (and two new-lines indicate
start of a paragraph.

However, for now - double-spaces will remain - and I hope to remember to
add my own :)

> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue18280>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue18280>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41401] Using non-ascii that require UTF-8 breaks AIX testing

2020-07-26 Thread Michael Felt

Michael Felt  added the comment:

Neat! extra arguments!!

The warnings - extracted:

== CPython 3.10.0a0 (heads/master-dirty:b1a8730, Jul 26 2020, 14:00:34) [GCC 
7.2.0]
== AIX-2-00F9C1964C00-powerpc-32bit big-endian
== cwd: /home/aixtools/cpython/cpython-master/build/test_python_27984450▒
== CPU count: 32
== encodings: locale=ISO8859-1, FS=iso8859-1
0:00:00 Run tests sequentially
0:00:00 [1/1] test_io
test_fspath_support (test.test_io.CIOTest) ... ok

--

Ran 1 test in 0.026s

OK
Warning -- files was modified by test_io
  Before: []
  After:  ['@test_27984450_tmpæ']
test_io failed (env changed)

+
== CPython 3.10.0a0 (heads/master-dirty:b1a8730, Jul 26 2020, 14:00:34) [GCC 
7.2.0]
== AIX-2-00F9C1964C00-powerpc-32bit big-endian
== cwd: /home/aixtools/cpython/cpython-master/build/test_python_28246552▒
== CPU count: 32
== encodings: locale=ISO8859-1, FS=iso8859-1
0:00:00 Run tests sequentially
0:00:00 [1/1] test_io
test_fspath_support (test.test_io.PyIOTest) ... ok

--

Ran 1 test in 0.026s

OK
Warning -- files was modified by test_io
  Before: []
  After:  ['@test_28246552_tmpæ']
test_io failed (env changed)

== Tests result: SUCCESS ==

1 test altered the execution environment:
test_io



== CPython 3.10.0a0 (heads/master-dirty:b1a8730, Jul 26 2020, 14:00:34) [GCC 
7.2.0]
== AIX-2-00F9C1964C00-powerpc-32bit big-endian
== cwd: /home/aixtools/cpython/cpython-master/build/test_python_33620404▒
== CPU count: 32
== encodings: locale=ISO8859-1, FS=iso8859-1
0:00:00 Run tests sequentially
0:00:00 [1/1] test_io
test_reader_writer_close_error_on_close (test.test_io.CBufferedRWPairTest) ... 
ok

--

Ran 1 test in 0.001s

OK
Warning -- Unraisable exception
Exception ignored in: <_io.BufferedRWPair object at 0x30689750>
Traceback (most recent call last):
  File "/home/aixtools/cpython/cpython-master/Lib/test/support/__init__.py", 
line 613, in gc_collect
gc.collect()
ValueError: flush of closed file
Warning -- Unraisable exception
Exception ignored in: <_io.BufferedWriter>
Traceback (most recent call last):
  File "/home/aixtools/cpython/cpython-master/Lib/test/support/__init__.py", 
line 613, in gc_collect
gc.collect()
ValueError: flush of closed file
test_io failed (env changed)

== Tests result: SUCCESS ==

1 test altered the execution environment:
test_io

Hope this helps!

--

___
Python tracker 
<https://bugs.python.org/issue41401>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue18280] Documentation is too personalized

2020-07-26 Thread Michael Felt


Michael Felt  added the comment:

I am taking a look at these, and I am sure there is a PEP I am unaware of - atm 
- so, a quick question.

Is the double space at the end of a sentence 'required' by the rst processing, 
or is this also a 'personal' writing style in some of the documents (i.e., is 
replacing them with a single ' ', or otherwise, a new line ('\n') an error.

iirc - new paragraphs are indicated by two new-lines.

--
nosy: +Michael.Felt

___
Python tracker 
<https://bugs.python.org/issue18280>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41401] Using non-ascii that require UTF-8 breaks AIX testing

2020-07-26 Thread Michael Felt

New submission from Michael Felt :

issue41069 introduces tests for paths/files containing non-ascii characters.

On AIX - since the merge of PR21035 and PR21156 - the bots have been broken, 
i.e., returning test failed.

commit 700cfa8c90a90016638bac13c4efd03786b2b2a0
Author: Serhiy Storchaka 
Date:   Thu Jun 25 17:56:31 2020 +0300

bpo-41069: Make TESTFN and the CWD for tests containing non-ascii 
characters. (GH-21035)

commit f925407a19eeb9bf5f7640143979638adce2c677
Author: Serhiy Storchaka 
Date:   Thu Jun 25 20:39:12 2020 +0300

[3.9] bpo-41069: Make TESTFN and the CWD for tests containing non-ascii 
characters. (GH-21035). (GH-21156)

(cherry picked from commit 700cfa8c90a90016638bac13c4efd03786b2b2a0)



Sadly, I cannot determine - exactly - where it is going wrong as the verbose 
results ends (says SUCCESS, but there is an ENV change, so bot says FAILED) as:

--

Ran 614 tests in 59.122s

OK (skipped=8)
Warning -- files was modified by test_io
  Before: []
  After:  ['@test_23134518_tmpæ']
test_io failed (env changed) in 59.7 sec

== Tests result: SUCCESS ==

1 test altered the execution environment:
test_io

Total duration: 59.8 sec

--
components: IO, Tests
messages: 374312
nosy: Michael.Felt
priority: normal
severity: normal
status: open
title: Using non-ascii that require UTF-8 breaks AIX testing
type: behavior
versions: Python 3.10, Python 3.9

___
Python tracker 
<https://bugs.python.org/issue41401>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-07 Thread Michael Felt


Michael Felt  added the comment:

Here is the stack trace - still during initialization: And in "ceval.c,
but dbx does not like how the 'h files are being used: line 941 and 659
lines don't match :(

(dbx) list
"object.h" has only 659 lines

Segmentation fault in _PyEval_EvalFrameDefault at line 941 in file
"../git/py39-3.10/Include/object.h" ($t1)
"object.h" has only 659 lines
(dbx) where
_PyEval_EvalFrameDefault(tstate = 0x3009c9d0, f = 0x0017, throwflag
= 15), line 941 in "object.h"
_PyEval_EvalCode(tstate = 0x1001c454, _co = 0x3009c250, globals =
0x2ff20260, locals = 0x10324233, args = 0x100b2798, argcount = 44,
kwnames = 0x2ff20280, kwargs = 0x2228228f, kwcount = 0, kwstep = 2, defs
= (nil), defcount = 0, kwdefs = (nil), closure = (nil), name = (nil),
qualname = (nil)), line 40 in "pycore_ceval.h"
_PyEval_EvalCodeWithName(_co = 0x0003, globals = 0x2ff20340, locals
= 0x2ff202f0, args = 0x2004429c, argcount = 805945904, kwnames = (nil),
kwargs = 0x2ff202f0, kwcount = 0, kwstep = 2, defs = (nil), defcount =
0, kwdefs = (nil), closure = (nil), name = (nil), qualname = (nil)),
line 4416 in "ceval.c"
PyEval_EvalCodeEx(_co = 0x10110c74, globals = 0x200817a2, locals =
(nil), args = 0x30091598, argcount = 805901716, kws = 0x200817da,
kwcount = 537401128, defs = 0x30078f58, defcount = 0, kwdefs = (nil),
closure = (nil)), line 4415 in "ceval.c"
builtin___build_class__(self = 0x100b8bdc, args = (nil), nargs =
804389872, kwnames = 0x2004429c), line 222 in "bltinmodule.c"
cfunction_vectorcall_FASTCALL_KEYWORDS(func = 0x100d5e54, args = (nil),
nargsf = 805553488, kwnames = 0x3004658c), line 459 in "methodobject.c"
_PyEval_EvalFrameDefault(tstate = 0x300912d8, f = 0x30050c8c, throwflag
= 805485032), line 628 in "abstract.h"
_PyEval_EvalCode(tstate = 0x10110c74, _co = 0x3004abb8, globals =
0x30095fa8, locals = 0x3009d16c, args = 0x3009d168, argcount =
805586012, kwnames = 0x30044450, kwargs = 0x30001028, kwcount = 0,
kwstep = 2, defs = (nil), defcount = 0, kwdefs = (nil), closure = (nil),
name = (nil), qualname = (nil)), line 40 in "pycore_ceval.h"
_PyEval_EvalCodeWithName(_co = 0x3004abd8, globals = 0x30092258, locals
= 0x2ff20680, args = 0x2004429c, argcount = 269191840, kwnames =
0x300550e0, kwargs = 0x2ff20680, kwcount = 1109926476, kwstep = 2, defs
= (nil), defcount = 0, kwdefs = (nil), closure = (nil), name = (nil),
qualname = (nil)), line 4416 in "ceval.c"
PyEval_EvalCodeEx(_co = 0x10090ab0, globals = (nil), locals =
0xf0653ea8, args = 0xf0653ea8, argcount = 0, kws = 0x20082720, kwcount =
804390704, defs = 0x2228228f, defcount = 0, kwdefs = (nil), closure =
(nil)), line 4415 in "ceval.c"
PyEval_EvalCode(co = 0x103a1274, globals = 0x103a155e, locals =
0x30099978), line 857 in "ceval.c"
builtin_exec_impl(module = 0x300912c4, source = 0x30050cb8, globals =
0x20060a78, locals = 0x0002), line 1035 in "bltinmodule.c"
builtin_exec(module = 0x100d58b4, args = 0x30050cb8, nargs = 0), line
371 in "bltinmodule.c.h"
cfunction_vectorcall_FASTCALL(func = 0x, args = 0x30050b80,
nargsf = 804391008, kwnames = 0x2004429c), line 443 in "methodobject.c"
PyVectorcall_Call(callable = 0x1001e5cc, tuple = 0x20060a78, kwargs =
0x2ff208c0), line 249 in "call.c"
_PyObject_Call(tstate = 0x100b259c, callable = 0x30027ce2, args =
0x2ff20920, kwargs = 0x2004429c), line 265 in "call.c"
do_call_core(tstate = 0x0002, func = 0x20026bc0, callargs =
0x2ff20990, kwdict = 0x3004abb8), line 5142 in "ceval.c"
_PyEval_EvalFrameDefault(tstate = 0x, f = 0x3004a070, throwflag
= 804391536), line 3603 in "ceval.c"
_PyEval_EvalCode(tstate = 0x3005e9b0, _co = 0x30062290, globals = (nil),
locals = 0x20026020, args = 0x300922f8, argcount = 805331176, kwnames =
0x2ff20b30, kwargs = 0x422822cf, kwcount = 0, kwstep = 1, defs = (nil),
defcount = 0, kwdefs = (nil), closure = (nil), name = 0x300197c8,
qualname = 0x300197c8), line 40 in "pycore_ceval.h"
_PyFunction_Vectorcall(func = 0x3005dbac, stack = (nil), nargsf =
805553488, kwnames = 0x30040960), line 417 in "call.c"
_PyEval_EvalFrameDefault(tstate = 0x10075ac4, f = 0x300921b8, throwflag
= 804392064), line 628 in "abstract.h"
function_code_fastcall(tstate = 0x30087538, co = 0x3004a1b0, args =
0x2000af70, nargs = 1, globals = 0x3004a688), line 40 in "pycore_ceval.h"
_PyEval_EvalFrameDefault(tstate = (nil), f = 0x0001, throwflag =
804392400), line 628 in "abstract.h"
function_code_fastcall(tstate = 0x30042fcc, co = 0x30031176, args =
0x30031160, nargs = 805622640, globals = (nil)), line 40 in "pycore_ceval.h"
_PyEval_EvalFrameDefault(tstate = 0x10075ac4, f = 0x20060a78, throwflag
= 804392736), line 628 in "abstract.h"
function_code_fastcall(tstate = 0x00e0, co = 0x009c, args =
0x300

[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-07 Thread Michael Felt


Michael Felt  added the comment:

On 07/07/2020 11:12, Michael Felt wrote:
> Michael Felt  added the comment:
>
> I saw the mails last night and restarted my bot - it still fails.
> Checking manually for master, 3.9, 3.8 and 3.7 branches. Will let you
3.7, 3.8 and 3.9 built, master does not. Will provide more info on
master later.
> know asap.
>
> Yes - expecting 3.8 and 3.7 to build, but want to be sure.
>
> On 06/07/2020 23:34, Pablo Galindo Salgado wrote:
>> Pablo Galindo Salgado  added the comment:
>>
>> Michael, could you check the latest master and 3.9 HEAD? If you don;t see 
>> the problem anymore, we can close this issue :)
>>
>> --
>>
>> ___
>> Python tracker 
>> <https://bugs.python.org/issue41215>
>> ___
>>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue41215>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue41215>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-07 Thread Michael Felt


Michael Felt  added the comment:

I saw the mails last night and restarted my bot - it still fails.
Checking manually for master, 3.9, 3.8 and 3.7 branches. Will let you
know asap.

Yes - expecting 3.8 and 3.7 to build, but want to be sure.

On 06/07/2020 23:34, Pablo Galindo Salgado wrote:
> Pablo Galindo Salgado  added the comment:
>
> Michael, could you check the latest master and 3.9 HEAD? If you don;t see the 
> problem anymore, we can close this issue :)
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue41215>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue41215>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-06 Thread Michael Felt

Michael Felt  added the comment:

I also tested xlC v16, and then it just hung, for hours - while all of you were 
being more productive. 

I’ll kickoff my bot again, and see how it goes. 

Sent from my iPhone

> On 6 Jul 2020, at 21:31, miss-islington  wrote:
> 
> 
> miss-islington  added the comment:
> 
> 
> New changeset 1ac0cbca369f16f9191833dd54536482fb141a98 by Pablo Galindo in 
> branch 'master':
> bpo-41215: Don't use NULL by default in the PEG parser keyword list (GH-21355)
> https://github.com/python/cpython/commit/1ac0cbca369f16f9191833dd54536482fb141a98
> 
> 
> --
> 
> ___
> Python tracker 
> <https://bugs.python.org/issue41215>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue41215>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-06 Thread Michael Felt


Michael Felt  added the comment:

Note: - two different systems, different HW, different OS levels.

xlc-v11, master : commit deb016224cc506503fb05e821a60158c83918ed4 (HEAD
-> master, upstream/master, upstream/HEAD)

Segmentation fault in _PyEval_EvalFrameDefault at line 941 in file
"../git/py39-3.10/Include/object.h" ($t1)
"object.h" has only 659 lines
(dbx) where
_PyEval_EvalFrameDefault(tstate = 0x300af594, f = 0x0017, throwflag
= 15), line 941 in "object.h"
_PyEval_EvalCode(tstate = 0x1001c454, _co = 0x30092520, globals =
0x2ff20190, locals = 0x10324213, args = 0x100b2798, argcount = 44,
kwnames = 0x2ff201b0, kwargs = 0x2228228f, kwcount = 0, kwstep = 2, defs
= (nil), defcount = 0, kwdefs = (nil), closure = (nil), name = (nil),
qualname = (nil)), line 40 in "pycore_ceval.h"
_PyEval_EvalCodeWithName(_co = 0x0003, globals = 0x2ff20270, locals
= 0x2ff20220, args = 0x2004426c, argcount = 806222336, kwnames = (nil),
kwargs = 0x2ff20220, kwcount = 0, kwstep = 2, defs = (nil), defcount =
0, kwdefs = (nil), closure = (nil), name = (nil), qualname = (nil)),
line 4416 in "ceval.c"
PyEval_EvalCodeEx(_co = 0x10110c74, globals = 0x20095072, locals =
(nil), args = 0x300af598, argcount = 806024596, kws = 0x200950aa,
kwcount = 537481208, defs = 0x300bcf10, defcount = 0, kwdefs = (nil),
closure = (nil)), line 4415 in "ceval.c"
builtin___build_class__(self = 0x100b8bdc, args = (nil), nargs =
804389664, kwnames = 0x2004426c), line 222 in "bltinmodule.c"
cfunction_vectorcall_FASTCALL_KEYWORDS(func = 0x20060d88, args =
0x30046448, nargsf = 805553488, kwnames = 0x3004abb8), line 459 in
"methodobject.c"
_PyEval_EvalFrameDefault(tstate = 0x01ff, f = 0x200012d0, throwflag
= 80439), line 628 in "abstract.h"
_PyEval_EvalCode(tstate = 0x100d4eb4, _co = 0x3003f440, globals =
0x300b2ca8, locals = 0x300b516c, args = 0x300b5168, argcount =
805586012, kwnames = 0x30044450, kwargs = 0x30001028, kwcount = 0,
kwstep = 2, defs = (nil), defcount = 0, kwdefs = (nil), closure = (nil),
name = (nil), qualname = (nil)), line 40 in "pycore_ceval.h"
_PyEval_EvalCodeWithName(_co = 0x3004abd8, globals = 0x300ac910, locals
= 0x2ff205b0, args = 0x2004426c, argcount = 269191840, kwnames =
0x2ff2060c, kwargs = 0x, kwcount = 0, kwstep = 2, defs = (nil),
defcount = 0, kwdefs = (nil), closure = (nil), name = (nil), qualname =
(nil)), line 4416 in "ceval.c"
PyEval_EvalCodeEx(_co = 0x10090ab0, globals = 0x0004, locals =
0x30062be8, args = (nil), argcount = 805624984, kws = 0x20060d88,
kwcount = 804390432, defs = 0x0004, defcount = 0, kwdefs = (nil),
closure = (nil)), line 4415 in "ceval.c"
PyEval_EvalCode(co = 0x103a1254, globals = 0x103a153e, locals =
0x300d1a48), line 857 in "ceval.c"
builtin_exec_impl(module = 0x300b8ec8, source = 0x300671d8, globals =
0x2002af08, locals = 0x300af170), line 1035 in "bltinmodule.c"
builtin_exec(module = 0x30059f6c, args = 0x30050d20, nargs = 804390720),
line 371 in "bltinmodule.c.h"
cfunction_vectorcall_FASTCALL(func = 0x101c1120, args = 0x3006906c,
nargsf = 805736544, kwnames = 0x2004426c), line 443 in "methodobject.c"
PyVectorcall_Call(callable = 0xd0129a34, tuple = 0x3008c028, kwargs =
0x2ff207f0), line 249 in "call.c"
_PyObject_Call(tstate = 0x100b259c, callable = 0x30027ce2, args =
0x2ff20850, kwargs = 0x000c), line 265 in "call.c"
do_call_core(tstate = (nil), func = (nil), callargs = 0x3003c550, kwdict
= 0x3004abb8), line 5142 in "ceval.c"
_PyEval_EvalFrameDefault(tstate = 0x, f = 0x300b2268, throwflag
= 805759592), line 3603 in "ceval.c"
_PyEval_EvalCode(tstate = 0x3005e9d8, _co = 0x30062290, globals = (nil),
locals = 0x20026000, args = 0x300ac690, argcount = 805331176, kwnames =
0x2ff20a60, kwargs = 0x422822cf, kwcount = 0, kwstep = 1, defs = (nil),
defcount = 0, kwdefs = (nil), closure = (nil), name = 0x300197c8,
qualname = 0x300197c8), line 40 in "pycore_ceval.h"
_PyFunction_Vectorcall(func = 0x3005dbac, stack = (nil), nargsf =
805553488, kwnames = 0x30040960), line 417 in "call.c"
_PyEval_EvalFrameDefault(tstate = 0x10075ac4, f = 0x30090e10, throwflag
= 804391856), line 628 in "abstract.h"
function_code_fastcall(tstate = 0x300a4568, co = 0x3004a1b0, args =
0x2000af50, nargs = 1, globals = 0x3004a688), line 40 in "pycore_ceval.h"
_PyEval_EvalFrameDefault(tstate = (nil), f = 0x0001, throwflag =
804392192), line 628 in "abstract.h"
function_code_fastcall(tstate = 0x3009116c, co = 0x30031176, args =
0x30031160, nargs = 805622640, globals = (nil)), line 40 in "pycore_ceval.h"
_PyEval_EvalFrameDefault(tstate = 0x10075ac4, f = 0x20060d88, throwflag
= 804392528), line 628 in "abstract.h"
function_code_fastcall(tstate = 0x0094, co = 0x00ab, args =
0x3003c550, nargs = 805702704, globals 

[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-06 Thread Michael Felt


Michael Felt  added the comment:

I tried check.c and check_bad.c using xlc-v11 (on my POWER6) - and the
results were the same as in Pablo's entry.

On the gcc119 host - using the v13 compiler, check_bad does not crash.
Not gotten to testing xlc-v16 yet.

I have seen lots of options today - wheile researching, so probably,
yes. Just do not know it off the top.

Atm - testing "master" build using xlc-v11 and xlc-v13.

On 06/07/2020 18:13, David Edelsohn wrote:
> David Edelsohn  added the comment:
>
> I don't believe that this is an XLC bug, but I suspect that it is undefined 
> behavior / implementation-defined behavior.
>
> I suspect that this is tripping over AIX/XLC null behavior. AIX specifically 
> and intentionally maps the first page of memory at address 0 to allow the 
> compiler to speculate through NULL pointers. The compiler probably is 
> speculating in this case and the second element is not defined.
>
> There is some option to disable this speculation in XLC.
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue41215>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue41215>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-06 Thread Michael Felt


Michael Felt  added the comment:

On 06/07/2020 16:35, Pablo Galindo Salgado wrote:
> Pablo Galindo Salgado  added the comment:
>
>> Glad you figured it out!
> Well, this is not over ;)
>
> We should confirm that this is either a bug in XLC or a violation of C99

probably a bug (that they might call a difference of implementation).

I have been testing with xlc-v11; shall also try (your simplified
example) using v13 and v16.

>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue41215>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue41215>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-06 Thread Michael Felt


Michael Felt  added the comment:

Glad you figured it out!

I doubt I would have. Thx!!

On 06/07/2020 14:37, Pablo Galindo Salgado wrote:
> Pablo Galindo Salgado  added the comment:
>
> This is enough to reproduce the problem:
>
> #include 
>
> typedef struct {
> char *str;
> int type;
> } KeywordToken;
>
> static KeywordToken *the_array[] = {
>NULL,
>NULL,
>(KeywordToken[]) {
> {"if", 510},
> {"in", 518},
> {"as", 520},
> {"is", 527},
> {"or", 532},
> {NULL, -1},
>},
>NULL,
>NULL,
> (KeywordToken[]) {
> {"del11", 503},
> {"try22", 511},
> {NULL, -1},
> },
> NULL
> };
>
>
> int main() {
>for (int s=0; s<7;s++) {
>   KeywordToken *tok = the_array[s];
>   printf("--> %i\n",s);
>   if (tok == NULL) {
>  continue;
>   }
>   printf("--> %i %.*s\n", s,s, tok->str);
>}
>return 0;
> }
>
> [cpython (3.9)]$ xlc check_bad.c -o check_bad
> [cpython (3.9)]$ ./check_bad
> --> 0
> --> 1
> --> 2
> Segmentation fault (core dumped)
>
>
> But if you change it to:
>
> #include 
>
> typedef struct {
> char *str;
> int type;
> } KeywordToken;
>
> static KeywordToken *the_array[] = {
>  (KeywordToken[]) {{NULL, -1}},
>  (KeywordToken[]) {{NULL, -1}},
> (KeywordToken[]) {
> {"if", 510},
> {"in", 518},
> {"as", 520},
> {"is", 527},
> {"or", 532},
> {NULL, -1},
> },
> (KeywordToken[]) {{NULL, -1}},
> (KeywordToken[]) {{NULL, -1}},
> (KeywordToken[]) {
> {"del11", 503},
> {"try22", 511},
> {NULL, -1},
> },
> (KeywordToken[]) {{NULL, -1}},
> };
>
>
> int main() {
>for (int s=0; s<7;s++) {
>   KeywordToken *tok = the_array[s];
>   if (tok == NULL) {
>  continue;
>   }
>   printf("--> %i %.*s\n", s,s, tok->str);
>}
>return 0;
> }
>
> [cpython (3.9)]$ xlc check.c -o check
> [cpython (3.9)]$ ./check
> --> 0
> --> 1
> --> 2 if
> --> 3
> --> 4
> --> 5 del11
> --> 6
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue41215>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue41215>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue35773] test_bdb fails on non-UTF-8 locale

2020-07-06 Thread Michael Felt


Michael Felt  added the comment:

Thanks for getting back to this. ++1 :)

On 25/06/2020 11:49, Serhiy Storchaka wrote:
> Serhiy Storchaka  added the comment:
>
> test_bdb fails on non-UTF-8 locale because Python executes a Python code from 
> the corresponding "encodings" submodule. There are shortcuts for the UTF-8 
> codec which avoid using the Python code.
>
> --
> nosy: +serhiy.storchaka
> title: test_bdb fails on AIX bot (regression) -> test_bdb fails on non-UTF-8 
> locale
> versions: +Python 3.10, Python 3.9
>
> ___
> Python tracker 
> <https://bugs.python.org/issue35773>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue35773>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-06 Thread Michael Felt

Michael Felt  added the comment:

My apologies for lack of context.

On 05/07/2020 20:27, Pablo Galindo Salgado wrote:
> Pablo Galindo Salgado  added the comment:
>
> Unfortunately, I am having a hard time parsing your error description because 
> is not immediate to distinguish:
>
> - What is the error.
crash - segmentation error.
> - Where does the error happen.
During python initialization.
> - How to reproduce the error.

The error occurs during `make`

root@x066:[/data/prj/python/bpo-41215]make
    xlc_r -g -c  -DNDEBUG -O -I/opt/include -O2 -qmaxmem=-1
-qarch=pwr5 -O    -I../git/bpo-41215/Include/internal -IObjects
-IInclude -IPython -I. -I../git/bpo-41215/Include -I/opt/include  
-DPy_BUILD_CORE -o Parser/pegen/pegen.o
../git/bpo-41215/Parser/pegen/pegen.c
    xlc_r -g -c  -DNDEBUG -O -I/opt/include -O2 -qmaxmem=-1
-qarch=pwr5 -O    -I../git/bpo-41215/Include/internal -IObjects
-IInclude -IPython -I. -I../git/bpo-41215/Include -I/opt/include  
-DPy_BUILD_CORE  -DGITVERSION="\"`LC_ALL=C `\""  -DGITTAG="\"`LC_ALL=C
`\""  -DGITBRANCH="\"`LC_ALL=C `\""  -o Modules/getbuildinfo.o
../git/bpo-41215/Modules/getbuildinfo.c
    rm -f libpython3.9.a
    ar rcs libpython3.9.a Modules/getbuildinfo.o  Parser/acceler.o 
Parser/grammar1.o  Parser/listnode.o  Parser/node.o  Parser/parser.o 
Parser/token.o   Parser/pegen/pegen.o  Parser/pegen/parse.o 
Parser/pegen/parse_string.o  Parser/pegen/peg_api.o Parser/myreadline.o
Parser/parsetok.o Parser/tokenizer.o  Objects/abstract.o 
Objects/accu.o  Objects/boolobject.o  Objects/bytes_methods.o 
Objects/bytearrayobject.o  Objects/bytesobject.o  Objects/call.o 
Objects/capsule.o  Objects/cellobject.o  Objects/classobject.o 
Objects/codeobject.o  Objects/complexobject.o  Objects/descrobject.o 
Objects/enumobject.o  Objects/exceptions.o 
Objects/genericaliasobject.o  Objects/genobject.o  Objects/fileobject.o 
Objects/floatobject.o  Objects/frameobject.o  Objects/funcobject.o 
Objects/interpreteridobject.o  Objects/iterobject.o 
Objects/listobject.o  Objects/longobject.o  Objects/dictobject.o 
Objects/odictobject.o  Objects/memoryobject.o  Objects/methodobject.o 
Objects/moduleobject.o  Objects/namespaceobject.o  Objects/object.o 
Objects/obmalloc.o  Objects/picklebufobject.o  Objects/rangeobject.o 
Objects/setobject.o  Objects/sliceobject.o  Objects/structseq.o 
Objects/tupleobject.o  Objects/typeobject.o  Objects/unicodeobject.o 
Objects/unicodectype.o  Objects/weakrefobject.o  Python/_warnings.o 
Python/Python-ast.o  Python/asdl.o  Python/ast.o  Python/ast_opt.o 
Python/ast_unparse.o  Python/bltinmodule.o  Python/ceval.o 
Python/codecs.o  Python/compile.o  Python/context.o 
Python/dynamic_annotations.o  Python/errors.o  Python/frozenmain.o 
Python/future.o  Python/getargs.o  Python/getcompiler.o 
Python/getcopyright.o  Python/getplatform.o  Python/getversion.o 
Python/graminit.o  Python/hamt.o  Python/import.o  Python/importdl.o 
Python/initconfig.o  Python/marshal.o  Python/modsupport.o 
Python/mysnprintf.o  Python/mystrtoul.o  Python/pathconfig.o 
Python/peephole.o  Python/preconfig.o  Python/pyarena.o 
Python/pyctype.o  Python/pyfpe.o  Python/pyhash.o  Python/pylifecycle.o 
Python/pymath.o  Python/pystate.o  Python/pythonrun.o  Python/pytime.o 
Python/bootstrap_hash.o  Python/structmember.o  Python/symtable.o 
Python/sysmodule.o  Python/thread.o  Python/traceback.o 
Python/getopt.o  Python/pystrcmp.o  Python/pystrtod.o 
Python/pystrhex.o  Python/dtoa.o  Python/formatter_unicode.o 
Python/fileutils.o  Python/dynload_shlib.o    Modules/config.o 
Modules/getpath.o  Modules/main.o  Modules/gcmodule.o 
Modules/posixmodule.o  Modules/errnomodule.o  Modules/pwdmodule.o 
Modules/_sre.o  Modules/_codecsmodule.o  Modules/_weakref.o 
Modules/_functoolsmodule.o  Modules/_operator.o 
Modules/_collectionsmodule.o  Modules/_abc.o  Modules/itertoolsmodule.o 
Modules/atexitmodule.o  Modules/signalmodule.o  Modules/_stat.o 
Modules/timemodule.o  Modules/_threadmodule.o  Modules/_localemodule.o 
Modules/_iomodule.o Modules/iobase.o Modules/fileio.o Modules/bytesio.o
Modules/bufferedio.o Modules/textio.o Modules/stringio.o 
Modules/faulthandler.o  Modules/_tracemalloc.o Modules/hashtable.o 
Modules/_peg_parser.o  Modules/symtablemodule.o  Modules/xxsubtype.o 
Python/frozen.o
    ../git/bpo-41215/Modules/makexp_aix Modules/python.exp .
libpython3.9.a;  xlc_r -g -Wl,-bE:Modules/python.exp -lld -o python
Programs/python.o libpython3.9.a -lintl -ldl  -lm   -lm
 ./python -E -S -m sysconfig --generate-posix-vars ; if test $?
-ne 0 ; then  echo "generate-posix-vars failed" ;  rm -f
./pybuilddir.txt ;  exit 1 ;  fi
/bin/sh: 5242890 Segmentation fault(coredump)
make: 1254-004 The error code from the last command is 139.

Stop.

And can be repeated by just trying to start the executable:

root@x066:[/data/prj/python/bpo-41215]./python
Segmentation fault(coredu

[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-05 Thread Michael Felt


Michael Felt  added the comment:

Iirc, my debug shows that k is not NULL, as k++ is not going to suddenly become 
smaller. And my debug shows it grows by a constant. 

My gut says the pointer to the base of the tokens is wrong, because the key 
types are such different values. Or do you know that those are valid types?

--

___
Python tracker 
<https://bugs.python.org/issue41215>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40424] AIX: makexp_aix, parallel build (failures) and ld WARNINGS

2020-07-05 Thread Michael Felt


Michael Felt  added the comment:

Thanks Kevin.

I took your patch (added your name to blurb as well).

Only difference was to remove Qsystem (or something), from the pathnames.

--
versions: +Python 3.7

___
Python tracker 
<https://bugs.python.org/issue40424>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-05 Thread Michael Felt

Michael Felt  added the comment:

OK - merely added some fprintf statements.

When it is working as expected, the k->type values seem to be between 500 and 
535 - when it fails the k->type value is frequently 9 digits (e.g., 537120904) 
- and it seems to never become -1 -- which would end the loop and "RETURN NAME".

One working example...

NAMEPTR: 20089d44, name_len:6 strlen(name):4472 name.16s:
import aliases



token: 20030d30, k_type:500, strlen(k->str):6 k->str.16s:
return

token: 20030d38, k_type:505, strlen(k->str):6 k->str.16s:
assert

token: 20030d40, k_type:508, strlen(k->str):6 k->str.16s:
global

token: 20030d48, k_type:513, strlen(k->str):6 k->str.16s:
import

RETURN k->type: 513 from k-str.16:import

And a failed (abbreviated) that ends with the segmentation error:

NAMEPTR: 20089d60, name_len:8 strlen(name): name.16s:
_unknown = '--un

token: 2000f340, k_type:537120904, strlen(k->str):0 k->str.16s:


token: 2000f348, k_type:271488524, strlen(k->str):8 k->str.16s:
d  z▒

token: 2000f350, k_type:805316552, strlen(k->str):0 k->str.16s:


token: 2000f358, k_type:368, strlen(k->str):11 k->str.16s:
__setitem__

token: 2000f360, k_type:537120928, strlen(k->str):8 k->str.16s:
<▒ z▒

token: 2000f368, k_type:0, strlen(k->str):61 k->str.16s:
__setitem__($sel

token: 2000f370, k_type:271482672, strlen(k->str):0 k->str.16s:


...
token: 2000f730, k_type:0, strlen(k->str):0 k->str.16s:


token: 2000f738, k_type:0, strlen(k->str):0 k->str.16s:


token: 2000f740, k_type:0, strlen(k->str):0 k->str.16s:


token: 2000f748, k_type:0, strlen(k->str):0 k->str.16s:


token: 2000f750, k_type:0, strlen(k->str):0 k->str.16s:


token: 2000f758, k_type:0, strlen(k->str):0 k->str.16s:


token: 2000f760, k_type:0, strlen(k->str):0 k->str.16s:


token: 2000f768, k_type:0, strlen(k->str):0 k->str.16s:


token: 2000f770, k_type:271810528, strlen(k->str):0 k->str.16s:


token: 2000f778, k_type:0, strlen(k->str):0 k->str.16s:


token: 2000f780, k_type:271810512, strlen(k->str):4 k->str.16s:
real

token: 2000f788, k_type:0, strlen(k->str):0 k->str.16s:


/bin/sh: 8847524 Segmentation fault(coredump)
make: 1254-004 The error code from the last command is 139.


Hope this helps. I really do not know 'WHERE' it went wrong. I can only begin 
by guessing. So, expert guidance is appreciated!

--

___
Python tracker 
<https://bugs.python.org/issue41215>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-05 Thread Michael Felt


Michael Felt  added the comment:

Well, the first step -s just showing where the segmentation fault occurs (in 
pegen.c).

I am not really 'wiser' in what I should be looking at. I'll try adding a 
fprintf(stderr, ) to see if I can figure out a bit more.

For the experts:

(dbx) where
strncmp(??, ??, ??) at 0xd011d920
_get_keyword_or_name_type(p = 0x0023, name = warning: Unable to access 
address 0xd from core
(invalid char ptr (0x000d)), name_len = 0), line 503 in "pegen.c"
_PyPegen_fill_token(p = 0x1025f138), line 546 in "pegen.c"
_PyPegen_expect_token(p = (nil), type = 805759776), line 675 in "pegen.c"
_tmp_6_rule@AF486_140(??), line 10251 in "parse.c"
_PyPegen_lookahead(positive = 269294544, func = 0x3001da40, p = 0x2ff20f30), 
line 666 in "pegen.c"
compound_stmt_rule@AF476_280(??), line 1232 in "parse.c"
statement_rule@AF477_284(??), line 795 in "parse.c"
unnamed block in _loop1_2_rule(p = 0x30085830), line 10086 in "parse.c"
_loop1_2_rule(p = 0x30085830), line 10086 in "parse.c"
statements_rule@AF478_285(??), line 766 in "parse.c"
file_rule@AF479_289(??), line 646 in "parse.c"
_PyPegen_run_parser(p = 0x30085820), line 916 in "pegen.c"
_PyPegen_run_parser_from_string(str = "compile", start_rule = 272032944, 
filename_ob = 0x20084f68, iflags = 805427776, arena = 0x30085820), line 1024 in 
"pegen.c"
PyPegen_ASTFromStringObject(str = (nil), filename = (nil), mode = 804393472, 
flags = 0x20035cb0, arena = 0x102453c4), line 26 in "peg_api.c"
unnamed block in Py_CompileStringObject(str = "|p^[yN", filename = (nil), start 
= 0, flags = 0x3007bbc8, optimize = -2147483647), line 1244 in "pythonrun.c"
Py_CompileStringObject(str = "|p^[yN", filename = (nil), start = 0, flags = 
0x3007bbc8, optimize = -2147483647), line 1244 in "pythonrun.c"
builtin_compile_impl(module = (nil), source = 0x2bd8, filename = 
0x20063c48, mode = "\320Qf", flags = 1, dont_inherit = 536873648, optimize = 
804393760, feature_version = 537275800), line 823 in "bltinmodule.c"
builtin_compile(module = 0x2ff21460, args = 0x3007fa78, nargs = 2, kwnames = 
0x30007470), line 274 in "bltinmodule.c.h"
cfunction_vectorcall_FASTCALL_KEYWORDS(func = 0x100b203c, args = 0x0003, 
nargsf = 804394000, kwnames = 0x20047844), line 396 in "methodobject.c"
PyVectorcall_Call(callable = 0x100b2e10, tuple = 0x20026f40, kwargs = 
0x2ff21470), line 255 in "call.c"
_PyObject_Call(tstate = 0x100b1d1c, callable = 0x30002870, args = 0x2ff214c0, 
kwargs = 0x30043fd0), line 265 in "call.c"
do_call_core(tstate = 0x0001, func = 0x30094050, callargs = 0x30046428, 
kwdict = 0x300462e8), line 5054 in "ceval.c"
_PyEval_EvalFrameDefault(tstate = 0x3009315c, f = 0x30043e58, throwflag = 
-261800280), line 3542 in "ceval.c"
_PyEval_EvalCode(tstate = 0x3005d820, _co = 0x3003a6a0, globals = 0x2ff216d0, 
locals = 0x422822cc, args = 0x100b46e4, argcount = 805410760, kwnames = 
0x2ff216d0, kwargs = 0x20047844, kwcount = 2, kwstep = 1, defs = (nil), 
defcount = 0, kwdefs = (nil), closure = (nil), name = 0x300197c8, qualname = 
0x300197c8), line 41 in "pycore_ceval.h"
_PyFunction_Vectorcall(func = 0x100d3714, stack = 0x3008ea08, nargsf = 
804394848, kwnames = 0x20047844), line 411 in "call.c"
_PyEval_EvalFrameDefault(tstate = 0x, f = 0x300834c8, throwflag = 
804395040), line 487 in "abstract.h"
_PyEval_EvalCode(tstate = 0x300865b0, _co = 0x30061b88, globals = 0x2ff218e0, 
locals = 0x5328333f, args = 0x10073d54, argcount = 537279560, kwnames = 
0x2ff218e0, kwargs = 0x20047844, kwcount = 0, kwstep = 1, defs = (nil), 
defcount = 0, kwdefs = 0x3006bb90, closure = (nil), name = 0x30061b88, qualname 
= 0x3004eb10), line 41 in "pycore_ceval.h"
_PyFunction_Vectorcall(func = 0x30092f50, stack = 0x30004048, nargsf = 
804395376, kwnames = (nil)), line 411 in "call.c"
_PyEval_EvalFrameDefault(tstate = 0x100759a4, f = (nil), throwflag = 
804395568), line 487 in "abstract.h"
function_code_fastcall(tstate = 0x300418bc, co = (nil), args = 0x3000c220, 
nargs = 805664616, globals = (nil)), line 41 in "pycore_ceval.h"
_PyEval_EvalFrameDefault(tstate = 0x100759a4, f = 0x30087c08, throwflag = 
804395904), line 487 in "abstract.h"
function_code_fastcall(tstate = 0x30086520, co = 0x3004c070, args = 0x2000abe8, 
nargs = 1, globals = 0x30049ec0), line 41 in "pycore_ceval.h"
_PyEval_EvalFrameDefault(tstate = (nil), f = 0x0001, throwflag = 
804396240), line 487 in "abstract.h"
function_code_fastcall(tstate = 0x3004389c, co = 0x30031176, args = 0x30031160, 
nargs = 805626736, globals = (nil)), line 41 in "pycore_ceval.h"
_PyEval_EvalFrameDefault(tstate = 0x100759a4, f = 0x20063c48, throwflag = 
80439

[issue41215] AIX: build fails for xlc/xlC since new PEG parser

2020-07-05 Thread Michael Felt


New submission from Michael Felt :

As the bots were both running - based on gcc - this was not noticed immediately.

issue40334 implements PEP 617, the new PEG parser for CPython.

Using bisect I located:

commit c5fc15685202cda73f7c3f5c6f299b0945f58508 (HEAD, refs/bisect/bad)
Author: Pablo Galindo 
Date:   Wed Apr 22 23:29:27 2020 +0100

bpo-40334: PEP 617 implementation: New PEG parser for CPython (GH-19503)

Co-authored-by: Guido van Rossum 
Co-authored-by: Lysandros Nikolaou 

+++ the make status (abbreviated) is:
root@x066:[/data/prj/python/py39-3.10]slibclean; rm -rf *; buildaix 
--without-computed-gotos; print; date; ./python -E -S -m sysconfig 
--generate-posix-vars; ./python
+ CPPFLAGS="-I/opt/include" CFLAGS="-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5"\
../git/py39-3.10/configure\
--prefix=/opt \
--sysconfdir=/var/py39/etc\
--sharedstatedir=/var/py39/com\
--localstatedir=/var/py39\
--mandir=/usr/share/man\
--infodir=/opt/share/info/py39 --without-computed-gotos\
> .buildaix/configure.out
+ /usr/bin/make > .buildaix/make.out
1500-016: (W) WARNING: Compiler problem occurred while compiling 
_PyPegen_clear_memo_statistics: A file or directory in the path name does not 
exist..
1500-034: (S) Cannot create object file.
make: 1254-004 The error code from the last command is 1.

+++ The complete make.out (stdout) is:
root@x066:[/data/prj/python/py39-3.10]cat .buildaix/make*
xlc_r -c  -DNDEBUG -O -I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 
-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5
-I../git/py39-3.10/Include/internal -IObjects -IInclude -IPython -I. 
-I../git/py39-3.10/Include -I/opt/include -I/opt/include  -DPy_BUILD_CORE -o 
Programs/python.o ../git/py39-3.10/Programs/python.c
xlc_r -c  -DNDEBUG -O -I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 
-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5
-I../git/py39-3.10/Include/internal -IObjects -IInclude -IPython -I. 
-I../git/py39-3.10/Include -I/opt/include -I/opt/include  -DPy_BUILD_CORE -o 
Parser/acceler.o ../git/py39-3.10/Parser/acceler.c
xlc_r -c  -DNDEBUG -O -I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 
-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5
-I../git/py39-3.10/Include/internal -IObjects -IInclude -IPython -I. 
-I../git/py39-3.10/Include -I/opt/include -I/opt/include  -DPy_BUILD_CORE -o 
Parser/grammar1.o ../git/py39-3.10/Parser/grammar1.c
xlc_r -c  -DNDEBUG -O -I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 
-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5
-I../git/py39-3.10/Include/internal -IObjects -IInclude -IPython -I. 
-I../git/py39-3.10/Include -I/opt/include -I/opt/include  -DPy_BUILD_CORE -o 
Parser/listnode.o ../git/py39-3.10/Parser/listnode.c
xlc_r -c  -DNDEBUG -O -I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 
-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5
-I../git/py39-3.10/Include/internal -IObjects -IInclude -IPython -I. 
-I../git/py39-3.10/Include -I/opt/include -I/opt/include  -DPy_BUILD_CORE -o 
Parser/node.o ../git/py39-3.10/Parser/node.c
xlc_r -c  -DNDEBUG -O -I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 
-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5
-I../git/py39-3.10/Include/internal -IObjects -IInclude -IPython -I. 
-I../git/py39-3.10/Include -I/opt/include -I/opt/include  -DPy_BUILD_CORE -o 
Parser/parser.o ../git/py39-3.10/Parser/parser.c
xlc_r -c  -DNDEBUG -O -I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 
-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5
-I../git/py39-3.10/Include/internal -IObjects -IInclude -IPython -I. 
-I../git/py39-3.10/Include -I/opt/include -I/opt/include  -DPy_BUILD_CORE -o 
Parser/token.o ../git/py39-3.10/Parser/token.c
xlc_r -c  -DNDEBUG -O -I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 
-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5
-I../git/py39-3.10/Include/internal -IObjects -IInclude -IPython -I. 
-I../git/py39-3.10/Include -I/opt/include -I/opt/include  -DPy_BUILD_CORE -o 
Parser/pegen/pegen.o ../git/py39-3.10/Parser/pegen/pegen.c

***
After 
commit a25f3c4c8f7d4878918ce1d3d67db40ae255ccc6 (HEAD)
Author: Pablo Galindo 
Date:   Thu Apr 23 01:38:11 2020 +0100

bpo-40334: Fix builds outside the source directory and regenerate autoconf 
files (GH-19667)

/bin/sh: 7405692 Segmentation fault(coredump)
make: 1254-004 The error code from the last command is 139.


Stop.
/usr/bin/make returned an error

Sun Jul  5 11:23:39 UTC 2020
Segmentation fault(coredump)
Python 3.9.0a5+ (default, Jul  5 2020, 11:23:33) [C] on aix
Type "help", "copyright", "credits" or "license" for more information.

***
The above includes 

aixtools@x064:[/data/prj/python/git/py39-3.10]git checkout 
458004bf7914f96b20bb76bc3584718cf83f652e
Previous HEAD position was a25f3c4c8f bpo-40334: Fix builds outside the source 
directory and regenerate autocon

[issue40878] Use c99 on the aixtools bot

2020-06-23 Thread Michael Felt


Michael Felt  added the comment:

I have been doing manual tests - and it seems build is broken for AIX
and xlc.

I shall be working on a git bisect to try and identify what broke it for
xlc-v11. Finding what broke xlc-v13 will require more time.

Note: it is no longer limited to _decimal not being built - builds
(i.e., compile) fail completely atm.

regards,

Michael

On 15/06/2020 18:55, Michael Felt wrote:
> Michael Felt  added the comment:
>
> I'll switch my bot https://buildbot.python.org/all/#/builders/119 to use
> c99_r rather than xlc_r.
>
> Test 1129 will b e the first with c99_r (and xlc v13).
>
> On 11/06/2020 00:37, Stefan Krah wrote:
>> Stefan Krah  added the comment:
>>
>> So it would still be interesting to see what happens if you compile
>> libmpdec with c99_r (emphasis mine):
>>
>>
>> """
>> This command supports all ISO
>> C99 language features, but does
>> not support IBM language
>> extensions. Use this invocation for
>> *strict* conformance to the C99
>> standard.
>> """
>>
>> --
>>
>> ___
>> Python tracker 
>> <https://bugs.python.org/issue40878>
>> ___
>>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40878>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40878>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40680] thread_cputime isn't supported by AIX5

2020-06-16 Thread Michael Felt


Michael Felt  added the comment:

There is still a lot of AIX 6.1 out there, and iirc, there may be
"extended" support available.

However, at this point in time the bots run (most of the time) on AIX
7.2, -- occasionally, on AIX 7.1. And when I (personally) test - it is
usually on AIX 6.1 (e.g., to have _uuid support).

In any case, I still package using AIX 6.1 (again, _uuid mod support)
and rely on AIX binary compatibility for installations on AIX 7.1 and
AIX 7.2.

Should you be thinking/considering moving AIX to the "supported" column
- I would "gladly" embrace AIX 7.1 as a requirement.

On 10/06/2020 22:58, STINNER Victor wrote:
> STINNER Victor  added the comment:
>
> According to 
> https://www.ibm.com/support/pages/aix-support-lifecycle-information I suggest 
> to require AIX 7.1 and newer.
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40680>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40680>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40878] Use c99 on the aixtools bot

2020-06-16 Thread Michael Felt

Michael Felt  added the comment:

I switched the "aixtools" bot back to "xlc", and also back to my POWER6
server that runs xlc-v11.

iirc it is xlc-v13 (or maybe even v12) that is having trouble with
_decimal (or is it POWER8). From memory, _decimal was compiling properly
with xlc-v11.

Although - my last runs on the POWER6, by default, were using gcc - so
maybe I thought, incorrectly, that xlc was passing.

Time shall tell.

p.s. - if you make a PR that emulates a rollback, if that is what you
were thinking - I can test that separately/manually.

Michael

On 16/06/2020 09:04, Michael Felt wrote:
> Michael Felt  added the comment:
>
> I’ll switch back to xlc ( even try without the _r ) and look for the macro 
> asap (vacation and occasional travel). 
>
> Sent from my iPhone
>
>> On 15 Jun 2020, at 21:20, Stefan Krah  wrote:
>>
>> 
>> Stefan Krah  added the comment:
>>
>> Thanks!
>>
>> Ha, it turns out that c99_r has excellent C99 compliance. :)
>>
>>> Variable arguments macro RAISE_SYNTAX_ERROR was invoked with an empty 
>>> variable argument list.
>> Totally legit, we should use xlc (at least the front end) more often.
>>
>>
>> So maybe our code base is not C99 compliant enough and we have to switch 
>> back for sanity.
>>
>>
>>
>> For the _decimal problem at hand, if you give me the compiler identification 
>> macro (__xlc__ or something?) I can try the same as for MSVC and use the 
>> explicit EXTINLINE definition.
>>
>> --
>>
>> ___
>> Python tracker 
>> <https://bugs.python.org/issue40878>
>> ___
>>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40878>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40878>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40878] Use c99 on the aixtools bot

2020-06-16 Thread Michael Felt

Michael Felt  added the comment:

I’ll switch back to xlc ( even try without the _r ) and look for the macro asap 
(vacation and occasional travel). 

Sent from my iPhone

> On 15 Jun 2020, at 21:20, Stefan Krah  wrote:
> 
> 
> Stefan Krah  added the comment:
> 
> Thanks!
> 
> Ha, it turns out that c99_r has excellent C99 compliance. :)
> 
>> Variable arguments macro RAISE_SYNTAX_ERROR was invoked with an empty 
>> variable argument list.
> 
> Totally legit, we should use xlc (at least the front end) more often.
> 
> 
> So maybe our code base is not C99 compliant enough and we have to switch back 
> for sanity.
> 
> 
> 
> For the _decimal problem at hand, if you give me the compiler identification 
> macro (__xlc__ or something?) I can try the same as for MSVC and use the 
> explicit EXTINLINE definition.
> 
> --
> 
> ___
> Python tracker 
> <https://bugs.python.org/issue40878>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40878>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40878] Use c99 on the aixtools bot

2020-06-15 Thread Michael Felt


Michael Felt  added the comment:

I'll switch my bot https://buildbot.python.org/all/#/builders/119 to use
c99_r rather than xlc_r.

Test 1129 will b e the first with c99_r (and xlc v13).

On 11/06/2020 00:37, Stefan Krah wrote:
> Stefan Krah  added the comment:
>
> So it would still be interesting to see what happens if you compile
> libmpdec with c99_r (emphasis mine):
>
>
> """
> This command supports all ISO
> C99 language features, but does
> not support IBM language
> extensions. Use this invocation for
> *strict* conformance to the C99
> standard.
> """
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40878>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40878>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40424] AIX: makexp_aix, parallel build (failures) and ld WARNINGS

2020-06-15 Thread Michael Felt


Michael Felt  added the comment:

Yes, it is less hacky - and something to pursue later - as a better
solution. Even the idea of perhaps no longer needing makexp_aix and/or
ld_so_aix and python.exp is much better solution.

However, the goal of this PR is to have something now - that removes the
pain (e.g., false bot failures and bot report storage impact) asap.

Many thanks for looking - and commenting!

On 15/06/2020 16:34, Kevin wrote:
> Kevin  added the comment:
>
> This seems to be a duplicate of https://bugs.python.org/issue19521
>
> The PR for that one seems a little less hacky since it uses make rules to 
> prevent duplication instead of lock files.
>
> --
> nosy: +kadler
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40424>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40424>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40424] AIX: makexp_aix, parallel build (failures) and ld WARNINGS

2020-06-11 Thread Michael Felt


Change by Michael Felt :


--
title: AIX: parallel build and ld WARNINGS -> AIX: makexp_aix, parallel build 
(failures) and ld WARNINGS

___
Python tracker 
<https://bugs.python.org/issue40424>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40424] AIX: parallel build and ld WARNINGS

2020-06-11 Thread Michael Felt


Michael Felt  added the comment:

specifically, makexp_aix - from 1998-1999 - did not consider parallelization.

make -j2 is sufficient to create the following issue - that frequently leads to 
a failed compile/build.

./Modules/makexp_aix Modules/python.exp . libpython3.9d.a;  gcc -pthread 
-Wl,-bE:Modules/python.exp -lld -o python Programs/python.o libpython3.9d.a 
-lintl -ldl  -lm   -lm 
./Modules/makexp_aix Modules/python.exp . libpython3.9d.a;  gcc -pthread 
-Wl,-bE:Modules/python.exp -lld -o Programs/_testembed Programs/_testembed.o 
libpython3.9d.a -lintl -ldl  -lm   -lm 
ld: 0711-418 ERROR: Import or export file Modules/python.exp at line 2:
A symbol name may only be followed by an export attribute
or an address. The line is being ignored.
ld: 0711-415 WARNING: Symbol PyAST_Check is already exported.
ld: 0711-415 WARNING: Symbol PyAST_Compile is already exported.
ld: 0711-415 WARNING: Symbol PyAST_CompileEx is already exported.
ld: 0711-415 WARNING: Symbol PyAST_CompileObject is already exported.
...
Over 4000 lines of warnings later:
ld: 0711-415 WARNING: Symbol _Py_write is already exported.
ld: 0711-415 WARNING: Symbol _Py_write_noraise is already exported.
collect2: error: ld returned 8 exit status
Makefile:598: recipe for target 'python' failed
make: *** [python] Error 1
program finished with exit code 2

Explanation: makexp_aix is running in parallel - and writing to python.exp in 
parallel.

The patch/PR "tames" this - and, hopefully, multiple "fails" per day, of the 
AIX bots will cease.

p.s. needed in 3.8, 3.9 and the new master (3.10)

--
versions: +Python 3.10

___
Python tracker 
<https://bugs.python.org/issue40424>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40680] thread_cputime isn't supported by AIX5

2020-06-10 Thread Michael Felt


Michael Felt  added the comment:

No, it is not supported - asin there are no new patches - but there are
organizations that use it.

imho - those organizations are not likely to be using the latest Python
- but I have been packaging Python on AIX 5.3 and AIX 6.1 - as these
packages run unmodified on AIX 7.1 and AIX 7.2 (AIX binary compatibility).

FYI.

On 19/05/2020 13:57, Batuhan Taskaya wrote:
> Batuhan Taskaya  added the comment:
>
> Does AIX 5.3 officially supported by IBM? As far as I can locate, it is 
> deprecated long time ago.
>
> --
> nosy: +BTaskaya
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40680>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40680>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40878] Use c99 on the aixtools bot

2020-06-10 Thread Michael Felt

Michael Felt  added the comment:

Actually, iirc - xlc is c99 plus a few extra settings.

The configuration files for xlc are, traditionally, in /etc (the later
versions of the compiler have moved them into /opt/show/where so that
multiple versions of the compiler can be installed.

buildbot@x064:[/home/buildbot]ls -l /etc/*vac*
-rw-r--r--    1 bin  bin   37731 Aug 02 2018  /etc/vac.cfg.53
-rw-r--r--    1 bin  bin   39672 Aug 02 2018  /etc/vac.cfg.61
-rw-r--r--    1 bin  bin   39681 Aug 02 2018  /etc/vac.cfg.71
-rw-r--r--    1 bin  bin   39611 Aug 02 2018  /etc/vac.cfg.72

Herein I see that xlc is "extc99" and some extras:

* -qlanglvl=extc99 C compiler with common extensions, UNIX headers
xlc:    use    = DEFLT_C
    crt    = /lib/crt0.o
    mcrt   = /lib/mcrt0.o
    gcrt   = /lib/gcrt0.o
    libraries  = -L/usr/vac/lib,-lxlopt,-lxlipa,-lxl,-lc
    proflibs   = -L/lib/profiled,-L/usr/lib/profiled
    options    =
-qlanglvl=extc99,-qcpluscmt,-qkeyword=inline,-qalias=ansi

I have chosen the xlc_r variant - for thread_safe additions:

* standard c compiler aliased as xlc_r (61 Threads)
xlc_r:  use    = DEFLT_C
    crt    = /lib/crt0.o
    mcrt   = /lib/mcrt0.o
    gcrt   = /lib/gcrt0.o
    libraries  = -L/usr/vac/lib,-lxlopt,-lxlipa,-lxl,-lpthreads,-lc
    proflibs   = -L/lib/profiled,-L/usr/lib/profiled
    hdlibs = -L/usr/vac/lib,-lhmd
    options    =
-qlanglvl=extc99,-qcpluscmt,-qkeyword=inline,-qalias=ansi,-qthreaded,-D_THREAD_SAFE,-D__VACPP_MULTI__

So, what is c99 then? -> focus on it is 'stdc99' rather than 'extc99'

* Strict ANSI compiler, ANSI headers
c99:    use    = DEFLT_C
    crt    = /lib/crt0.o
    mcrt   = /lib/mcrt0.o
    gcrt   = /lib/gcrt0.o
    libraries  = -L/usr/vac/lib,-lxlopt,-lxlipa,-lxl,-lc
    proflibs   = -L/lib/profiled,-L/usr/lib/profiled
    options    =
-qlanglvl=stdc99,-D_ANSI_C_SOURCE,-D_ISOC99_SOURCE,-qalias=ansi,-qstrict_induction

Hope this helps clarify that both xlc and c99 are "c99" based.

Regards,

Michael

On 05/06/2020 21:34, Stefan Krah wrote:
> New submission from Stefan Krah :
>
> There appears to be an xlc buildbot with libmpdec failures.
>
> libmpdec uses C99 extern inline semantics. From the brief period that I had 
> access to xlc I remember that xlc was quite picky about C99.
>
> Actually all of Python uses C99. So I think xlc_r needs to be invoked as 
> c99_r.
>
> --
> messages: 370779
> nosy: Michael.Felt, skrah
> priority: normal
> severity: normal
> status: open
> title: Use c99 on the aixtools bot
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40878>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40878>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue39791] New `files()` api from importlib_resources.

2020-06-06 Thread Michael Felt

Michael Felt  added the comment:

The 'fancy' file name breaks on latin-1 character set.

aixtools@gcc119:[/home/aixtools/python/py39-3.9] 
a4fa9a95153a3800dea60b3029b2dcaf8a4f6acb Lib/test/test_importlib/test_main.py   
<
diff --git a/Lib/test/test_importlib/test_main.py 
b/Lib/test/test_importlib/test_main.py
index 42a7999..7b18c3d 100644
--- a/Lib/test/test_importlib/test_main.py
+++ b/Lib/test/test_importlib/test_main.py
@@ -246,3 +246,19 @@ class TestEntryPoints(unittest.TestCase):
 """
 with self.assertRaises(Exception):
 json.dumps(self.ep)
+
+def test_module(self):
+assert self.ep.module == 'value'
+
+def test_attr(self):
+assert self.ep.attr is None
+
+
+class FileSystem(fixtures.OnSysPath, fixtures.SiteDir, unittest.TestCase):
+def test_unicode_dir_on_sys_path(self):
+"""
+Ensure a Unicode subdirectory of a directory on sys.path
+does not crash.
+"""
+fixtures.build_files({'☃': {}}, prefix=self.site_dir)
+list(distributions())

AIX bots fail with:

Captured traceback
==

Traceback (most recent call last):
  File 
"/home/shager/cpython-buildarea/3.9.edelsohn-aix-ppc64/build/Lib/test/test_importlib/test_main.py",
 line 263, in test_unicode_dir_on_sys_path
fixtures.build_files({'\u2603': {}}, prefix=self.site_dir)
  File 
"/home/shager/cpython-buildarea/3.9.edelsohn-aix-ppc64/build/Lib/test/test_importlib/fixtures.py",
 line 202, in build_files
full_name.mkdir()
  File 
"/home/shager/cpython-buildarea/3.9.edelsohn-aix-ppc64/build/Lib/pathlib.py", 
line 1309, in mkdir
self._accessor.mkdir(self, mode)
UnicodeEncodeError: 'latin-1' codec can't encode character '\u2603' in position 
17: ordinal not in range(256)



Test report
===

Failed tests:

- test_importlib

--
nosy: +Michael.Felt

___
Python tracker 
<https://bugs.python.org/issue39791>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40244] AIX: build: _PyObject_GC_TRACK Asstertion failure

2020-06-02 Thread Michael Felt


Michael Felt  added the comment:

I think this is showing up again. Ot seemed to be away when using xlcv13 (and 
is away with xlcv11).

I switched my bot off of xlc (v13) because compile fails again - and I'll 
investigate manually using xlc again.

If you could prep a PR where the change is reverted - I would appreciate it. If 
no time, I'll get to it as soon as I can.

--

___
Python tracker 
<https://bugs.python.org/issue40244>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40680] thread_cputime isn't supported by AIX5

2020-05-19 Thread Michael Felt


New submission from Michael Felt :

issue40192 introduced the use of nanosecond reporting of time.

The new routine called is not available in AIX 5.3:

xlc_r  -O -I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 -O
-I../git/python-3.9/Include/internal -IObjects -IInclude -IPython -I. 
-I../git/python-3.9/Include -I/opt/include   -DPy_BUILD_CORE_BUILTIN  
-DPy_BUILD_CORE_BUILTIN -I../git/python-3.9/Include/internal -c 
../git/python-3.9/Modules/timemodule.c -o Modules/timemodule.o
"../git/python-3.9/Modules/timemodule.c", line 1358.22: 1506-275 (S) Unexpected 
text tc encountered.
"../git/python-3.9/Modules/timemodule.c", line 1358.5: 1506-045 (S) Undeclared 
identifier thread_cputime_t.
"../git/python-3.9/Modules/timemodule.c", line 1359.29: 1506-045 (S) Undeclared 
identifier tc.
"../git/python-3.9/Modules/timemodule.c", line 1861.19: 1506-196 (W) 
Initialization between types "void*" and "int(*)(struct _object*)" is not 
allowed.
make: 1254-004 The error code from the last command is 1.

--
components: Build, Library (Lib)
messages: 369335
nosy: Michael.Felt
priority: normal
severity: normal
status: open
title: thread_cputime isn't supported by AIX5
versions: Python 3.9

___
Python tracker 
<https://bugs.python.org/issue40680>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue39148] DatagramProtocol + IPv6 does not work with ProactorEventLoop

2020-05-18 Thread Michael Felt


Michael Felt  added the comment:

I could not "fathom" the buildbot test results - however, a manual build of 
PR29170 on 3.9 works: I'll try 3.8, but then from master (assuming it is 
already part of master) -- and that works as well.

Thanks for the quick update!

--

___
Python tracker 
<https://bugs.python.org/issue39148>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue39148] DatagramProtocol + IPv6 does not work with ProactorEventLoop

2020-05-18 Thread Michael Felt


Michael Felt  added the comment:

Bot failed for AIX https://buildbot.python.org/all/#builders/227/builds/978 
with:

0:07:11 Re-running test_asyncio in verbose mode
Failed to import test module: test.test_asyncio.test_events
Traceback (most recent call last):
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/loader.py",
 line 436, in _find_test_path
module = self._get_module_from_name(name)
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/loader.py",
 line 377, in _get_module_from_name
__import__(name)
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_asyncio/test_events.py",
 line 239, in 
class EventLoopTestsMixin:
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_asyncio/test_events.py",
 line 1262, in EventLoopTestsMixin
@unittest.skipUnless(support.IPV6_ENABLED, 'IPv6 not supported or enabled')
AttributeError: module 'test.support' has no attribute 'IPV6_ENABLED'
test test_asyncio crashed -- Traceback (most recent call last):
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/libregrtest/runtest.py",
 line 270, in _runtest_inner
refleak = _runtest_inner2(ns, test_name)
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/libregrtest/runtest.py",
 line 234, in _runtest_inner2
test_runner()
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/libregrtest/runtest.py",
 line 208, in _test_module
raise Exception("errors while loading tests")
Exception: errors while loading tests
1 test failed again:
test_asyncio

--
nosy: +Michael.Felt

___
Python tracker 
<https://bugs.python.org/issue39148>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40424] AIX: parallel build and ld WARNINGS

2020-04-28 Thread Michael Felt


Change by Michael Felt :


--
keywords: +patch
pull_requests: +19081
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/19759

___
Python tracker 
<https://bugs.python.org/issue40424>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40424] AIX: parallel build and ld WARNINGS

2020-04-28 Thread Michael Felt


New submission from Michael Felt :

Currently, on AIX, whenever the -j option is passed to make there are many 
WARNINGS from the loader (ld) re: duplicate symbols.

While it is not possible to eliminate these warnings completely - as some are 
not related to the Python build, but external (3rd party) packaging - MOST of 
these warnings can be eliminated by ensuring that the export file creation 
completes before additional steps try to use it.

By adding a small test to see if the export file is in the process of being 
made - and waiting for that to finish - the messages "go away".

The PR that is being proposed only affects AIX (a script named makeaix_exp). 
The script has not been modified in 22 years - so I guess the -j option is 
something that showed up after 1998 :)

I know it is not perfect - but removes a tremendous amount of noise - most of 
the time.

Michael

p.s. requesting backport to 3.8 so all buildbots benefit.

--
components: Build
messages: 367541
nosy: Michael.Felt
priority: normal
severity: normal
status: open
title: AIX: parallel build and ld WARNINGS
type: behavior
versions: Python 3.8, Python 3.9

___
Python tracker 
<https://bugs.python.org/issue40424>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40370] AIX: ld_so_aix not found during test of test_peg_generator

2020-04-24 Thread Michael Felt


Michael Felt  added the comment:

Thanks for the quick response. I see both bots are good.

--

___
Python tracker 
<https://bugs.python.org/issue40370>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40370] AIX: ld_so_aix not found during test of test_peg_generator

2020-04-23 Thread Michael Felt

Michael Felt  added the comment:

Thanks for the quick work. I’ll test with xlc as well, as the builds behave 
differently this afternoon. 

Sent from my iPhone

> On 23 Apr 2020, at 16:31, Pablo Galindo Salgado  
> wrote:
> 
> 
> Pablo Galindo Salgado  added the comment:
> 
> Tested on an AIX system:
> 
> [pablo@ibm_machine cpython (master)]$ uname -a
> AIX ibm_machine 1 7 *** powerpc  AIX
> [pablo@ibm1 cpython (master)]$ ./python -m test test_peg_generator
> 0:00:00 Run tests sequentially
> 0:00:00 [1/1] test_peg_generator
> 
> == Tests result: SUCCESS ==
> 
> 1 test OK.
> 
> Total duration: 5.0 sec
> Tests result: SUCCESS
> 
> I will mark this issue as fixed as It was failing before on this machine and 
> now the test suceeds. Feel free to reopen if is not fixes in your system :)
> 
> --
> resolution:  -> fixed
> stage: patch review -> resolved
> status: open -> closed
> 
> ___
> Python tracker 
> <https://bugs.python.org/issue40370>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40370>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40370] AIX: ld_so_aix not found during test of test_peg_generator

2020-04-23 Thread Michael Felt


Michael Felt  added the comment:

More `make test` output:

1 test failed:
test_peg_generator

18 tests skipped:
test_devpoll test_epoll test_gdb test_ioctl test_kqueue
test_msilib test_ossaudiodev test_spwd test_startfile test_tix
test_tk test_ttk_guionly test_unicode_file
test_unicode_file_functions test_winconsoleio test_winreg
test_winsound test_zipfile64
0:05:24
0:05:24 Re-running failed tests in verbose mode
0:05:24 Re-running test_peg_generator in verbose mode
test_advanced_left_recursive 
(test.test_peg_generator.test_c_parser.TestCParser) ... ERROR
test_c_parser (test.test_peg_generator.test_c_parser.TestCParser) ... ERROR
test_cut (test.test_peg_generator.test_c_parser.TestCParser) ... ERROR
test_error_in_rules (test.test_peg_generator.test_c_parser.TestCParser) ... 
ERROR
test_gather (test.test_peg_generator.test_c_parser.TestCParser) ... ERROR
test_gather_action_ast (test.test_peg_generator.test_c_parser.TestCParser) ... 
ERROR
test_headers_and_trailer (test.test_peg_generator.test_c_parser.TestCParser) 
... ok
test_if_stmt_action (test.test_peg_generator.test_c_parser.TestCParser) ... 
ERROR
test_left_recursion (test.test_peg_generator.test_c_parser.TestCParser) ... 
ERROR
test_lookahead (test.test_peg_generator.test_c_parser.TestCParser) ... 
/tmp/tmpte0se473/parse.c: In function 'start_rule':
/tmp/tmpte0se473/parse.c:32:35: warning: passing argument 2 of 
'_PyPegen_lookahead' from incompatible pointer type 
[-Wincompatible-pointer-types]
 _PyPegen_lookahead(1, _PyPegen_name_token, p)
   ^~~
In file included from /tmp/tmpte0se473/parse.c:2:0:
/home/aixtools/python/cpython-master/Parser/pegen/pegen.h:90:5: note: expected 
'void * (*)(Parser *) {aka void * (*)(struct  *)}' but argument is 
of type 'struct _expr * (*)(Parser *) {aka struct _expr * (*)(struct 
 *)}'
 int _PyPegen_lookahead(int, void *(func)(Parser *), Parser *);
 ^~
ERROR
test_mutually_left_recursive 
(test.test_peg_generator.test_c_parser.TestCParser) ... ERROR
test_nasty_mutually_left_recursive 
(test.test_peg_generator.test_c_parser.TestCParser) ... ERROR
test_negative_lookahead (test.test_peg_generator.test_c_parser.TestCParser) ... 
/tmp/tmpyyc57e2e/parse.c: In function 'start_rule':
/tmp/tmpyyc57e2e/parse.c:32:35: warning: passing argument 2 of 
'_PyPegen_lookahead' from incompatible pointer type 
[-Wincompatible-pointer-types]
 _PyPegen_lookahead(0, _PyPegen_name_token, p)
   ^~~
In file included from /tmp/tmpyyc57e2e/parse.c:2:0:
/home/aixtools/python/cpython-master/Parser/pegen/pegen.h:90:5: note: expected 
'void * (*)(Parser *) {aka void * (*)(struct  *)}' but argument is 
of type 'struct _expr * (*)(Parser *) {aka struct _expr * (*)(struct 
 *)}'
 int _PyPegen_lookahead(int, void *(func)(Parser *), Parser *);
 ^~
ERROR
test_pass_stmt_action (test.test_peg_generator.test_c_parser.TestCParser) ... 
ERROR
test_return_stmt_noexpr_action 
(test.test_peg_generator.test_c_parser.TestCParser) ... ERROR
test_same_name_different_types 
(test.test_peg_generator.test_c_parser.TestCParser) ... ERROR
test_syntax_error_for_string 
(test.test_peg_generator.test_c_parser.TestCParser) ... []
ERROR
test_ternary_operator (test.test_peg_generator.test_c_parser.TestCParser) ... 
ERROR
test_with_stmt_with_paren (test.test_peg_generator.test_c_parser.TestCParser) 
... ERROR
test_advance_left_recursion 
(test.test_peg_generator.test_first_sets.TestFirstSets) ... ok
test_alternatives (test.test_peg_generator.test_first_sets.TestFirstSets) ... ok
test_epsilon_production_in_start_rule 
(test.test_peg_generator.test_first_sets.TestFirstSets) ... ok
test_gather (test.test_peg_generator.test_first_sets.TestFirstSets) ... ok
test_left_recursion (test.test_peg_generator.test_first_sets.TestFirstSets) ... 
ok
test_multiple_nullable_rules 
(test.test_peg_generator.test_first_sets.TestFirstSets) ... ok
test_mutual_left_recursion 
(test.test_peg_generator.test_first_sets.TestFirstSets) ... ok
test_nasty_left_recursion 
(test.test_peg_generator.test_first_sets.TestFirstSets) ... ok
test_negative_lookahead (test.test_peg_generator.test_first_sets.TestFirstSets) 
... ok
test_nullable_rule (test.test_peg_generator.test_first_sets.TestFirstSets) ... 
ok
test_optional_after (test.test_peg_generator.test_first_sets.TestFirstSets) ... 
ok
test_optional_before (test.test_peg_generator.test_first_sets.TestFirstSets) 
... ok
test_optional_literal (test.test_peg_generator.test_first_sets.TestFirstSets) 
... ok
test_optional_operator (test.test_peg_generator.test_first_sets.TestFirstSets) 
... ok
test_optionals (test.test_peg_generator.test_first_sets.TestFirstSets) ... ok
test_positive_lookahead (test.test_peg_generator.test_first_sets.TestFirstSets) 
... ok
test_repeat_0 (test.test_peg_generator.test_first_sets.TestFirstSets) ... ok
test_repeat_0_with_group

[issue40370] AIX: ld_so_aix not found during test of test_peg_generator

2020-04-23 Thread Michael Felt


Michael Felt  added the comment:

with the xlc-v11 environment yet another issue:

Stop.
/usr/bin/make returned an error
root@x065:[/data/prj/python/python-3.9]make V=1
xlc_r -c   -O -I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 -O
-I../git/python-3.9/Include/internal -IObjects -IInclude -IPython -I. 
-I../git/python-3.9/Include -I/opt/include   -DPy_BUILD_CORE -o Modules/_math.o 
../git/python-3.9/Modules/_math.c
 CC='xlc_r' LDSHARED='Modules/ld_so_aix xlc_r -bI:Modules/python.exp' 
OPT='-O'  _TCLTK_INCLUDES='' _TCLTK_LIBS=''  ./python -E 
../git/python-3.9/setup.py  build
make: 1254-059 The signal code from the last command is 11.

** All I can test using PR19674 ** Hope it helps.

--

___
Python tracker 
<https://bugs.python.org/issue40370>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40370] AIX: ld_so_aix not found during test of test_peg_generator

2020-04-23 Thread Michael Felt


Michael Felt  added the comment:

Currently build using xlc-v13 hangs during creation of _json.so. Trying xlc-v11.

--

___
Python tracker 
<https://bugs.python.org/issue40370>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40370] AIX: ld_so_aix not found during test of test_peg_generator

2020-04-23 Thread Michael Felt


Michael Felt  added the comment:

New issue with test during PR19764:

0:03:29 [416/423/1] test_peg_generator failed (2 min 34 sec) -- running: 
test_pathlib (3 min 19 sec), test_bufio (3 min 17 sec), test_concurrent_futures 
(3 min 10 sec), test_multiprocessing_fork (3 min), test_subprocess (2 min 49 
sec), test_multiprocessing_forkserver (3 min 18 sec), 
test_multiprocessing_spawn (2 min 56 sec)
[]

\u2514\u2500\u2500Rule
   \u2514\u2500\u2500Rhs
  \u2514\u2500\u2500Alt
 \u251c\u2500\u2500NamedItem
 \u2502  \u2514\u2500\u2500StringLeaf("'a'")
 \u2514\u2500\u2500NamedItem
\u2514\u2500\u2500Opt
   \u2514\u2500\u2500Rhs
  \u2514\u2500\u2500Alt
 \u251c\u2500\u2500NamedItem
 \u2502  \u2514\u2500\u2500StringLeaf("'b'")
 \u2514\u2500\u2500NamedItem
\u2514\u2500\u2500Opt
   \u2514\u2500\u2500Rhs
  \u2514\u2500\u2500Alt
 \u251c\u2500\u2500NamedItem
 \u2502  \u2514\u2500\u2500StringLeaf("'c'")
 \u2514\u2500\u2500NamedItem
\u2514\u2500\u2500Opt
   \u2514\u2500\u2500Rhs
  \u2514\u2500\u2500Alt
 \u2514\u2500\u2500NamedItem

\u2514\u2500\u2500StringLeaf("'d'")

start() ... (looking at 1.0: OP:'(')
  expect('(') ... (looking at 1.0: OP:'(')
  ... expect('(') -> TokenInfo(type=54 (OP), string='(', start=(1, 0), end=(1, 
1), line='(1)')
  expr() ... (looking at 1.1: NUMBER:'1')
number() ... (looking at 1.1: NUMBER:'1')
... number() -> TokenInfo(type=2 (NUMBER), string='1', start=(1, 1), 
end=(1, 2), line='(1)')
  ... expr() -> [TokenInfo(type=2 (NUMBER), string='1', start=(1, 1), end=(1, 
2), line='(1)')]
  expect(')') ... (looking at 1.2: OP:')')
  ... expect(')') -> TokenInfo(type=54 (OP), string=')', start=(1, 2), end=(1, 
3), line='(1)')
... start() -> [TokenInfo(type=54 (OP), string='(', start=(1, 0), end=(1, 1), 
line='(1)'), [TokenInfo(type=2 (NUMBER), string='1', start=(1, 1), end=(1, 2), 
line='(1)')], TokenInfo(type=54 (OP), string=')', start=(1
Rule('start', None, Rhs([Alt([NamedItem(None, Gather(StringLeaf("','"), 
NameLeaf('thing'))), NamedItem(None, NameLeaf('NEWLINE'))])]))
/tmp/tmp9nzhxvu1/parse.c: In function 'start_rule':
/tmp/tmp9nzhxvu1/parse.c:32:35: warning: passing argument 2 of 
'_PyPegen_lookahead' from incompatible pointer type 
[-Wincompatible-pointer-types]
 _PyPegen_lookahead(1, _PyPegen_name_token, p)
   ^~~
In file included from /tmp/tmp9nzhxvu1/parse.c:2:0:
/home/aixtools/python/cpython-master/Parser/pegen/pegen.h:90:5: note: expected 
'void * (*)(Parser *) {aka void * (*)(struct  *)}' but argument is 
of type 'struct _expr * (*)(Parser *) {aka struct _expr * (*)(struct 
 *)}'
 int _PyPegen_lookahead(int, void *(func)(Parser *), Parser *);
 ^~
/tmp/tmp1qne6lpy/parse.c: In function 'start_rule':
/tmp/tmp1qne6lpy/parse.c:32:35: warning: passing argument 2 of 
'_PyPegen_lookahead' from incompatible pointer type 
[-Wincompatible-pointer-types]
 _PyPegen_lookahead(0, _PyPegen_name_token, p)
   ^~~
In file included from /tmp/tmp1qne6lpy/parse.c:2:0:
/home/aixtools/python/cpython-master/Parser/pegen/pegen.h:90:5: note: expected 
'void * (*)(Parser *) {aka void * (*)(struct  *)}' but argument is 
of type 'struct _expr * (*)(Parser *) {aka struct _expr * (*)(struct 
 *)}'
 int _PyPegen_lookahead(int, void *(func)(Parser *), Parser *);
 ^~
test test_peg_generator failed -- multiple errors occurred; run in verbose mode 
for details
0:03:47 [417/423/1] test_pathlib passed (3 min 36 sec) -- running: test_bufio 
(3 min 35 sec), test_concurrent_futures (3 min 27 sec), 
test_multiprocessing_fork (3 min 18 sec), test_subprocess (3 min 6 sec), 
test_multiprocessing_forkserver (3 min 35 sec), test_multiprocessing_spawn (3 
min 14 sec)
0:03:51 [418/423/1] test_multiprocessing_fork passed (3 min 21 sec) -- running: 
test_bufio (3 min 39 sec), test_concurrent_futures (3 min 32 sec), 
test_subprocess (3 min 11 sec), test_multiprocessing_forkserver (3 min 40 sec), 
test_multiprocessing_spawn (3 min 18 sec)
/home/aixtools/python/cpython-master/Lib/multiprocessing/resource_tracker.py:216:
 UserWarning: resource_tracker: There appear to be 1 leaked shared_memory 
objects to clean up at shutdown
  warnings.warn('resource_tracker: There appear to be %d '
/home/aixtools/python/cpython-master/Lib/multiprocessing/resource_tracker.py:229:
 UserWarning: resource_tracker: '/psm_35e4dd20': [Err

[issue40370] AIX: ld_so_aix not found during test of test_peg_generator

2020-04-22 Thread Michael Felt


New submission from Michael Felt :

As part, I assume, of PR19503, that includes 91 changed files with 27,058 
additions and 147 deletions the AIX buildbot is broken.

Rather than looking/finding Modules/ld_so_aix (where I expect it to be) tests 
are failing, ulitmately because they look/expect it to be in a new location, 
and with a name dependent on being debug (or not) as the bots are configured 
using --pydebug.

Examples:
FileNotFoundError: [Errno 2] No such file or directory: 
'/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/target/lib/python3.9/config-3.9d/ld_so_aix'

or

FileNotFoundError: [Errno 2] No such file or directory: 
'/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/target/lib/python3.9/config-3.9d/ld_so_aix'

This is (only?) in test_peg_generator.

One traceback example:
Captured traceback
==

Traceback (most recent call last):
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Lib/test/test_peg_generator/test_c_parser.py",
 line 174, in test_nasty_mutually_left_recursive
self.check_input_strings_for_grammar(grammar, self.tmp_path, valid_cases, 
invalid_cases)
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Lib/test/test_peg_generator/test_c_parser.py",
 line 40, in check_input_strings_for_grammar
extension = generate_parser_c_extension(grammar, Path(tmp_path))
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Tools/peg_generator/pegen/testutil.py",
 line 95, in generate_parser_c_extension
extension_path = compile_c_extension(str(source), build_dir=str(path / 
"build"))
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Tools/peg_generator/pegen/build.py",
 line 73, in compile_c_extension
cmd.run()
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Lib/distutils/command/build_ext.py",
 line 340, in run
self.build_extensions()
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Lib/distutils/command/build_ext.py",
 line 449, in build_extensions
self._build_extensions_serial()
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Lib/distutils/command/build_ext.py",
 line 474, in _build_extensions_serial
self.build_extension(ext)
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Lib/distutils/command/build_ext.py",
 line 551, in build_extension
self.compiler.link_shared_object(
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Lib/distutils/ccompiler.py",
 line 713, in link_shared_object
self.link(CCompiler.SHARED_OBJECT, objects,
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Lib/distutils/unixccompiler.py",
 line 204, in link
self.spawn(linker + ld_args)
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Lib/distutils/ccompiler.py",
 line 910, in spawn
spawn(cmd, dry_run=self.dry_run)
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Lib/distutils/spawn.py",
 line 74, in spawn
proc = subprocess.Popen(cmd, env=env)
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Lib/subprocess.py", 
line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
  File 
"/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/Lib/subprocess.py", 
line 1819, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 
'/home/aixtools/buildarea/3.x.aixtools-aix-power6/build/target/lib/python3.9/config-3.9d/ld_so_aix'

See https://buildbot.python.org/all/#builders/119/builds/720 and 
https://buildbot.python.org/all/#builders/227/builds/723

--
components: Build, Tests
messages: 367081
nosy: Michael.Felt
priority: normal
severity: normal
status: open
title: AIX: ld_so_aix not found during test of test_peg_generator
type: behavior
versions: Python 3.9

___
Python tracker 
<https://bugs.python.org/issue40370>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40244] AIX: build: _PyObject_GC_TRACK Asstertion failure

2020-04-22 Thread Michael Felt


Michael Felt  added the comment:

When I have more time I hope to investigate specifically what is
different in the assembly code - with/without the __noreturn__ change.

On 19/04/2020 08:20, Batuhan Taskaya wrote:
> Batuhan Taskaya  added the comment:
>
> Moving assertion from _PyObject_GC_TRACK to gen_dealloc (just before the 
> _PyObject_GC_TRACK call) results with success ()
>
>  if (gen->gi_weakreflist != NULL)
>  PyObject_ClearWeakRefs(self);
> -
> +_PyObject_ASSERT_FROM(self, !_PyObject_GC_IS_TRACKED(self),
> +  "object already tracked by they garbage collector",
> +  __FILE__, __LINE__, "_PyObject_GC_TRACK");
>  _PyObject_GC_TRACK(self);
>  
>  if (PyObject_CallFinalizerFromDealloc(self))
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40244>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40244>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue39953] Let's update ssl error codes

2020-04-16 Thread Michael Felt


Michael Felt  added the comment:

Checked with latest version - and working as expected. Sorry for the noise.

On 15/04/2020 17:53, SilentGhost wrote:
> SilentGhost  added the comment:
>
> Michael, could you try with the latest fix in 584a3cfda4?
>
> --
> nosy: +SilentGhost
>
> ___
> Python tracker 
> <https://bugs.python.org/issue39953>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue39953>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue39953] Let's update ssl error codes

2020-04-15 Thread Michael Felt

Michael Felt  added the comment:

I did update, and saw that there was one more patch applied. 

I think that fixed the define issues, but there may be a new concern. Ran out 
of time to document it today. 

Will post tomorrow. 

Sent from my iPhone

> On 15 Apr 2020, at 17:53, SilentGhost  wrote:
> 
> 
> SilentGhost  added the comment:
> 
> Michael, could you try with the latest fix in 584a3cfda4?
> 
> --
> nosy: +SilentGhost
> 
> ___
> Python tracker 
> <https://bugs.python.org/issue39953>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue39953>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue39953] Let's update ssl error codes

2020-04-15 Thread Michael Felt


Michael Felt  added the comment:

And when I use a standard OpenSSL library (on AIX):

building '_ssl' extension
gcc -pthread -Wno-unused-result -Wsign-compare -g -Og -Wall -std=c99 -Wextra 
-Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers 
-Werror=implicit-function-declaration -fvisibility=hidden -I./Include/internal 
-I/opt/freeware/include -I./Include -I. 
-I/home/aixtools/python/cpython-master/Include 
-I/home/aixtools/python/cpython-master -c 
/home/aixtools/python/cpython-master/Modules/_ssl.c -o 
build/temp.aix-7200-1543-32-3.9-pydebug/home/aixtools/python/cpython-master/Modules/_ssl.o
Modules/ld_so_aix gcc -pthread -bI:Modules/python.exp 
build/temp.aix-7200-1543-32-3.9-pydebug/home/aixtools/python/cpython-master/Modules/_ssl.o
 -L/opt/freeware/lib -lssl -lcrypto -o 
build/lib.aix-7200-1543-32-3.9-pydebug/_ssl.so
ld: 0711-317 ERROR: Undefined symbol: .SSL_SESSION_get_ticket_lifetime_hint
ld: 0711-317 ERROR: Undefined symbol: .SSL_SESSION_has_ticket
ld: 0711-317 ERROR: Undefined symbol: .SSL_session_reused
ld: 0711-317 ERROR: Undefined symbol: .COMP_get_type
ld: 0711-317 ERROR: Undefined symbol: .SSL_is_init_finished
ld: 0711-317 ERROR: Undefined symbol: .SSL_CTX_get_options
ld: 0711-317 ERROR: Undefined symbol: .SSL_CTX_clear_options
ld: 0711-317 ERROR: Undefined symbol: .SSL_CTX_set_options
ld: 0711-317 ERROR: Undefined symbol: .SSL_CIPHER_is_aead
ld: 0711-317 ERROR: Undefined symbol: .SSL_CIPHER_get_cipher_nid
ld: 0711-317 ERROR: Undefined symbol: .SSL_CIPHER_get_digest_nid
ld: 0711-317 ERROR: Undefined symbol: .SSL_CIPHER_get_kx_nid
ld: 0711-317 ERROR: Undefined symbol: .SSL_CIPHER_get_auth_nid
ld: 0711-317 ERROR: Undefined symbol: .X509_STORE_get0_objects
ld: 0711-317 ERROR: Undefined symbol: .X509_OBJECT_get0_X509
ld: 0711-317 ERROR: Undefined symbol: .OPENSSL_sk_num
ld: 0711-317 ERROR: Undefined symbol: .OPENSSL_sk_value
ld: 0711-317 ERROR: Undefined symbol: .X509_OBJECT_get_type
ld: 0711-317 ERROR: Undefined symbol: .X509_NAME_ENTRY_set
ld: 0711-317 ERROR: Undefined symbol: .SSL_CTX_get_default_passwd_cb
ld: 0711-317 ERROR: Undefined symbol: .SSL_CTX_get_default_passwd_cb_userdata
ld: 0711-317 ERROR: Undefined symbol: .OpenSSL_version_num
ld: 0711-317 ERROR: Undefined symbol: .TLS_method
ld: 0711-317 ERROR: Undefined symbol: .TLS_client_method
ld: 0711-317 ERROR: Undefined symbol: .TLS_server_method
ld: 0711-317 ERROR: Undefined symbol: .BIO_up_ref
ld: 0711-317 ERROR: Undefined symbol: .OPENSSL_sk_pop_free
ld: 0711-317 ERROR: Undefined symbol: .X509_get_version
ld: 0711-317 ERROR: Undefined symbol: .X509_getm_notBefore
ld: 0711-317 ERROR: Undefined symbol: .X509_getm_notAfter
ld: 0711-317 ERROR: Undefined symbol: .OpenSSL_version
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information.

$ lslpp -L | grep openssl
  aixtools.openssl.rte  1.0.2.16C Faixtools openssl 27-Aug-2018
  openssl.base 1.0.1.515CEFOpen Secure Socket Layer
  openssl.man.en_US1.0.1.515C FOpen Secure Socket Layer
  openssl  1.1.0g-1withsslv2C RSecure Sockets Layer and
  openssl-devel1.1.0g-1withsslv2C RSecure Sockets Layer and

+++ FYI +++
IBM AIX used some strange version numbers: 1.0.1.515 is actually an OpenSSL 
1.0.2 ABI version.

The "aixtools" fileset is 1.0.2p (p == 16th character of alphabet).

In any case - the test for X509_VERIFY_PARAM_set1_host() has been passing.

--

___
Python tracker 
<https://bugs.python.org/issue39953>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue39953] Let's update ssl error codes

2020-04-15 Thread Michael Felt


Michael Felt  added the comment:

Also checking with gcc: get the following messages:

Failed to build these modules:
_ssl

Could not build the ssl module!
Python requires an OpenSSL 1.0.2 or 1.1 compatible libssl with 
X509_VERIFY_PARAM_set1_host().
LibreSSL 2.6.4 and earlier do not provide the necessary APIs, 
https://github.com/libressl-portable/portable/issues/381

messages:
building '_ssl' extension
gcc -pthread -Wno-unused-result -Wsign-compare -g -Og -Wall -std=c99 -Wextra 
-Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers 
-Werror=implicit-function-declaration -fvisibility=hidden -I./Include/internal 
-I/opt/aixtools/include -I./Include -I. 
-I/home/aixtools/python/cpython-master/Include 
-I/home/aixtools/python/cpython-master -c 
/home/aixtools/python/cpython-master/Modules/_ssl.c -o 
build/temp.aix-7200-1543-32-3.9-pydebug/home/aixtools/python/cpython-master/Modules/_ssl.o
In file included from /home/aixtools/python/cpython-master/Modules/_ssl.c:136:0:
/home/aixtools/python/cpython-master/Modules/_ssl_data.h:650:28: error: 
'ERR_LIB_ASYNC' undeclared here (not in a function); did you mean 
'ERR_LIB_ASN1'?
 {"FAILED_TO_SET_POOL", ERR_LIB_ASYNC, 101},
^
ERR_LIB_ASN1
/home/aixtools/python/cpython-master/Modules/_ssl_data.h:1510:29: error: 
'ERR_LIB_CT' undeclared here (not in a function); did you mean 'ERR_LIB_CMS'?
 {"BASE64_DECODE_ERROR", ERR_LIB_CT, 108},
 ^~
 ERR_LIB_CMS
/home/aixtools/python/cpython-master/Modules/_ssl_data.h:2650:24: error: 
'ERR_LIB_KDF' undeclared here (not in a function); did you mean 'ERR_LIB_BUF'?
 {"INVALID_DIGEST", ERR_LIB_KDF, 100},
^~~
ERR_LIB_BUF

--

___
Python tracker 
<https://bugs.python.org/issue39953>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue39953] Let's update ssl error codes

2020-04-15 Thread Michael Felt


Michael Felt  added the comment:

Do I need to open a new issue?

This breaks building _ssl on AIX.

building '_ssl' extension
xlc_r -O -I./Include/internal -I/opt/aixtools/include -I./Include -I. 
-I/home/aixtools/python/cpython-master/Include 
-I/home/aixtools/python/cpython-master -c 
/home/aixtools/python/cpython-master/Modules/_ssl.c -o 
build/temp.aix-7200-1543-32-3.9-pydebug/home/aixtools/python/cpython-master/Modules/_ssl.o
"/home/aixtools/python/cpython-master/Modules/_ssl_data.h", line 650.28: 
1506-045 (S) Undeclared identifier ERR_LIB_ASYNC.
"/home/aixtools/python/cpython-master/Modules/_ssl_data.h", line 1510.29: 
1506-045 (S) Undeclared identifier ERR_LIB_CT.
"/home/aixtools/python/cpython-master/Modules/_ssl_data.h", line 2650.24: 
1506-045 (S) Undeclared identifier ERR_LIB_KDF.
"/home/aixtools/python/cpython-master/Modules/_ssl.c", line 579.17: 1506-196 
(W) Initialization between types "void*" and "struct _object*(*)(struct 
{...}*)" is not allowed.



commit 909b87d2bb3d6330d39c48e43f7f50f4d086cc41
Author: Benjamin Peterson 
Date:   Sun Apr 12 13:59:31 2020 -0500

closes bpo-39953: Generate ifdefs around library code definitions. 
(GH-19490)

commit 3e0dd3730b5eff7e9ae6fb921aa77cd26efc9e3a
Author: Benjamin Peterson 
Date:   Sat Apr 11 15:36:12 2020 -0500

closes bpo-39953: Update OpenSSL error codes table. (GH-19082)

I updated the error codes using the OpenSSL 1.1.1f source tree.

commit 173ad83b074b3bf0c9e86eb8bd101c2841f74297
Author: Antoine Pitrou 
Date:   Sun Jan 18 17:39:32 2015 +0100

Issue #23248: Update ssl error codes from latest OpenSSL git master.

commit f7338f65fb8bdb85c52dc54d06d003a82a06bbb3
Author: Antoine Pitrou 
Date:   Fri Jun 22 21:12:59 2012 +0200

Add forgotten files for #14837.
$

--
nosy: +Michael.Felt

___
Python tracker 
<https://bugs.python.org/issue39953>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40244] AIX: build: _PyObject_GC_TRACK Asstertion failure

2020-04-15 Thread Michael Felt


Michael Felt  added the comment:

On 14/04/2020 19:28, Michael Felt wrote:
> Michael Felt  added the comment:
>
> On 14/04/2020 14:54, Batuhan Taskaya wrote:
>> Batuhan Taskaya  added the comment:
>>
>>> With the print statements - it does not crash:
>> I think this isn't directly relevant with prints but about re-compiling? 
>> (just guessing).
> I only recompiled the one .c file. With that one file re-compiled -
> wqith fprintf statements it succeeds, restore the original .c file (git
> checkout -- Objects/whatever.c; make - it fails.
>
> Tomorrow I'll search for the option(s) needed to get (complete) assembly
> code listing and try to see (and understand) the difference between what
> xlc-v13 and xlc-v16 makes. And, what I shall also test - is to recompile
> only this one file using xlc-v13 and see if the make then proceeds normally.
>
>
Many pages of output - and I confess - I do have some difficulty reading
code every now and then.

As the "bug" wherever it may be is related, I am guessing, to compiler
optimization and how to deal with routines with "no return".

Trying to understand the listings - I ran across:

./Include/object.h:typedef void (*destructor)(PyObject *);

Could the error be related to compilers confusing a routine with no
return, versus a routine returning a pointer to a "void"?

recall the code:

static void
gen_dealloc(PyGenObject *gen)

Comments?

Michael

> As Victor commented earlier - very much looking like a compiler bug.
> That said, still do not know what to say/write to software support as a
> complaint.
>
>> --
>>
>> ___
>> Python tracker 
>> <https://bugs.python.org/issue40244>
>> ___
>>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40244>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40244>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40244] AIX: build: _PyObject_GC_TRACK Asstertion failure

2020-04-14 Thread Michael Felt


Michael Felt  added the comment:

On 14/04/2020 14:54, Batuhan Taskaya wrote:
> Batuhan Taskaya  added the comment:
>
>> With the print statements - it does not crash:
> I think this isn't directly relevant with prints but about re-compiling? 
> (just guessing).

I only recompiled the one .c file. With that one file re-compiled -
wqith fprintf statements it succeeds, restore the original .c file (git
checkout -- Objects/whatever.c; make - it fails.

Tomorrow I'll search for the option(s) needed to get (complete) assembly
code listing and try to see (and understand) the difference between what
xlc-v13 and xlc-v16 makes. And, what I shall also test - is to recompile
only this one file using xlc-v13 and see if the make then proceeds normally.

>  Because I experienced when I compile python for the first time on a clean 
> AIX environment, all extension modules failed to build.

I only see this happen (on occasion) when I use make -j4 (or greater) -
and I have seen it happen to a lessor extent with -j2. On the subsequent
passes, whatever it is that setup.py (guessing) really needs is now
available - and the modules build as expected.

This is also why, for the last 4 years I have used my own personal
server - where I control everything (mainly NO other party OSS packaged
software and their artifacts).

>  When I recompiled (with keeping all artifacts from previous build) some of 
> them successfully got compiled. When I try to compile again, most of them 
> successfully compiled. I'm sorry but I don't know why this happens or how to 
> solve it.
why - I do not understand the finer details either, but my guess is that
it is related to linking. I am nearly "amazed" - yet happy - that the
PPC64 AIX 3.X compile succeeds - but acknowledge the 22K+ lines of
warnings is related to the over parallelization of the linking.
> We can always revert that change but I guess that isn't the real problem.

No. I do not think it is the real problem either. And I do not know
compiler behavior well enough. Actually, considering the setting is
still -O0 (aka no optimization) I am surprised it has any effect. if I
understood correctly "no return" is intended to help the optimizer make
"informed" decisions.

As Victor commented earlier - very much looking like a compiler bug.
That said, still do not know what to say/write to software support as a
complaint.

>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40244>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40244>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40244] AIX: build: _PyObject_GC_TRACK Asstertion failure

2020-04-14 Thread Michael Felt

Michael Felt  added the comment:

Also tried this:

 ./python -E -S -m sysconfig --generate-posix-vars ; if test $?
-ne 0 ; then  echo "generate-posix-vars failed" ;  rm -f
./pybuilddir.txt ;  exit 1 ;  fi
Objects/genobject.c:127: _PyObject_GC_TRACK: Assertion "!(((PyGC_Head
*)(op)-1)->_gc_next != 0)" failed: object already tracked by the garbage
collector
Enable tracemalloc to get the memory block allocation traceback

object address  : 30084150
object refcount : 0
object type : 20013718
object type name: generator
object repr : 

Fatal Python error: _PyObject_AssertFailed: _PyObject_AssertFailed
Python runtime state: core initialized

Current thread 0x0001 (most recent call first):
  File "", line 1593 in _setup
  File "", line 1634 in _install
  File "", line 1189 in
_install_external_importers
/bin/sh: 17302202 IOT/Abort trap(coredump)
make: 1254-004 The error code from the last command is 134.

Stop.
$ git diff
diff --git a/Objects/genobject.c b/Objects/genobject.c
index d3455f8..e783636 100644
--- a/Objects/genobject.c
+++ b/Objects/genobject.c
@@ -119,7 +119,7 @@ gen_dealloc(PyGenObject *gen)
 {
 PyObject *self = (PyObject *) gen;

-    _PyObject_GC_UNTRACK(gen);
+    _PyObject_GC_UNTRACK(self);

 if (gen->gi_weakreflist != NULL)
 PyObject_ClearWeakRefs(self);
$

On 14/04/2020 00:18, Batuhan Taskaya wrote:
> Batuhan Taskaya  added the comment:
>
> By the noticed something that looks kind of weird, not sure if it is 
> intentional or not but shouldn't this be self instead of gen
>
> static void
> gen_dealloc(PyGenObject *gen)
> {
> PyObject *self = (PyObject *) gen;
> <<<<
> _PyObject_GC_UNTRACK(gen);
> <<<<
> if (gen->gi_weakreflist != NULL)
> PyObject_ClearWeakRefs(self);
> _PyObject_GC_TRACK(self);
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40244>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40244>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40244] AIX: build: _PyObject_GC_TRACK Asstertion failure

2020-04-14 Thread Michael Felt

Michael Felt  added the comment:

With the print statements - it does not crash:

 ./python -E -S -m sysconfig --generate-posix-vars ; if test $?
-ne 0 ; then  echo "generate-posix-vars failed" ;  rm -f
./pybuilddir.txt ;  exit 1 ;  fi
Objects/genobject.c:122:537318120
Objects/genobject.c:126:0
Objects/genobject.c:131:0
Objects/genobject.c:135:537318120
Objects/genobject.c:122:805942488
Objects/genobject.c:126:0
Objects/genobject.c:131:0
Objects/genobject.c:135:537318120
...

diff --git a/Objects/genobject.c b/Objects/genobject.c
index d3455f8..b8287a3 100644
--- a/Objects/genobject.c
+++ b/Objects/genobject.c
@@ -117,14 +117,23 @@ exc_state_clear(_PyErr_StackItem *exc_state)
 static void
 gen_dealloc(PyGenObject *gen)
 {
+#include 
 PyObject *self = (PyObject *) gen;
+    fprintf(stderr,"%s:%d:%ld\n", __FILE__,__LINE__,
_Py_AS_GC(self)->_gc_next);
+    fflush(stderr);

 _PyObject_GC_UNTRACK(gen);
+    fprintf(stderr,"%s:%d:%ld\n", __FILE__,__LINE__,
_Py_AS_GC(self)->_gc_next);
+    fflush(stderr);

 if (gen->gi_weakreflist != NULL)
 PyObject_ClearWeakRefs(self);
+    fprintf(stderr,"%s:%d:%ld\n", __FILE__,__LINE__,
_Py_AS_GC(self)->_gc_next);
+    fflush(stderr);

 _PyObject_GC_TRACK(self);
+    fprintf(stderr,"%s:%d:%ld\n", __FILE__,__LINE__,
_Py_AS_GC(self)->_gc_next);
+    fflush(stderr);

 if (PyObject_CallFinalizerFromDealloc(self))
 return; /* resurrected.  :( */
$

On 13/04/2020 23:19, Batuhan Taskaya wrote:
> Batuhan Taskaya  added the comment:
>
> @Michael.Felt can you just insert some prints between these 3 to see what is 
> going on (and re-compile)
>
> static void
> gen_dealloc(PyGenObject *gen)
> {
> PyObject *self = (PyObject *) gen;
> <<<<
> _PyObject_GC_UNTRACK(gen);
> <<<<
> if (gen->gi_weakreflist != NULL)
> PyObject_ClearWeakRefs(self);
> <<<<
> _PyObject_GC_TRACK(self);
>
>
> something like this should work: printf("%ld\n", _Py_AS_GC(self)->_gc_next);
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40244>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40244>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40244] AIX: build: _PyObject_GC_TRACK Asstertion failure

2020-04-13 Thread Michael Felt

Michael Felt  added the comment:

After my build I have the following:

$ ./python -m test.pythoninfo|grep -E 'CFLAGS|CC|OPT|LDFLAGS'
Objects/genobject.c:127: _PyObject_GC_TRACK: Assertion "!(((PyGC_Head
*)(op)-1)->_gc_next != 0)" failed: object already tracked by the garbage
collector
Enable tracemalloc to get the memory block allocation traceback

object address  : 30084150
object refcount : 0
object type : 20013710
object type name: generator
object repr : 

Fatal Python error: _PyObject_AssertFailed: _PyObject_AssertFailed
Python runtime state: core initialized

Current thread 0x0001 (most recent call first):
  File "", line 1593 in _setup
  File "", line 1634 in _install
  File "", line 1189 in
_install_external_importers
ksh: 22151670 IOT/Abort trap(coredump)

See attached file for the script capture.

On 11/04/2020 15:13, Batuhan Taskaya wrote:
> Batuhan Taskaya  added the comment:
>
> I've just compiled python with (xlc 16.1.0, debug build) and can't experience 
> that compile failure, can you give a specific spot that failure happens?
>
> -bash-4.4$ ./python -m test.pythoninfo|grep -E 'CFLAGS|CC|OPT|LDFLAGS'
> sysconfig[CC]: /opt/IBM/xlc/16.1.0/bin/xlc_r
> sysconfig[CFLAGS]: -DNDEBUG -O
> sysconfig[CONFIG_ARGS]: 'CC=/opt/IBM/xlc/16.1.0/bin/xlc_r'
> sysconfig[OPT]: -DNDEBUG -O
> sysconfig[PY_CFLAGS]: -DNDEBUG -O
> sysconfig[PY_CFLAGS_NODIST]: -I./Include/internal
> sysconfig[PY_STDMODULE_CFLAGS]: -DNDEBUG -O -I./Include/internal -I. 
> -I./Include
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40244>
> ___
>

--
Added file: https://bugs.python.org/file49058/issue40170.txt

___
Python tracker 
<https://bugs.python.org/issue40244>
___Script command is started on Mon Apr 13 06:29:37 CDT 2020.
$ .kxlc16-envc166xlc16
$ echo $PATH $CC
/opt/IBM/xlc/16.1.0/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java7_64/jre/bin:/usr/java7_64/bin:/home/aixtools/bin
 xlc_r
$ updategit
Checking out files: 100% (160/160), done.
Previous HEAD position was 0003c2d... bpo-40096: Support 
__attribute__((__noreturn__)) on xlc (GH-19204)
Switched to branch 'master'
Your branch is up-to-date with 'upstream/master'.
remote: Enumerating objects: 610, done.K
remote: Counting objects: 100% (610/610), done.K
remote: Compressing objects: 100% (2/2), done.K
remote:nTotale775:(delta(608),7reused 609 (delta 608), pack-reused 165K
Receiving objects: 100% (775/775), 533.45 KiB | 0 bytes/s, done.
Resolving deltas: 100% (645/645), completed with 287 local objects.
>From https://github.com/python/cpython
   38aefc5..0c13e1f  master -> upstream/master
   8a0a500..7a41638  2.7-> upstream/2.7
   44c1cdd..0a9ec9f  3.7-> upstream/3.7
   f7b0259..ee691b0  3.8-> upstream/3.8
 * [new tag] v2.7.18rc1 -> v2.7.18rc1
>From https://github.com/python/cpython
 * branchmaster -> FETCH_HEAD
Updating 38aefc5..0c13e1f
Checking out files: 100% (195/195), done.
Fast-forward
 Doc/c-api/gcsupport.rst |  
 18 
 Doc/howto/unicode.rst   |  
  5 
 Doc/library/dis.rst |  
  6 
 Doc/library/multiprocessing.rst |  
 13 
 Doc/library/socket.rst  |  
 11 
 Doc/library/ssl.rst |  
  3 
 Doc/library/threading.rst   |  
  8 -
 Doc/whatsnew/3.9.rst|  
 28 
 Include/Python.h|  
  1 
 Include/cpython/abstract.h  |  
 10 
 Include/cpython/objimpl.h   |  
111 
 Include/cpython/pystate.h   |  
  7 
 Include/errcode.h   |  
  1 
 Include/genericaliasobject.h|  
 14 
 Include/internal/pycore_abstract.h  |  
 22 
 Include/internal/pycore_ceval.h |  
 11 
 Include/internal/pycore_gc.h|  
 69 ++
 Include/internal/pycore_interp.h|  
183 
 Include/internal/pycore_object.h|  
 11 
 Include/internal/pycore_pymem.h  

[issue40112] AIX: xlc - default path changed and no longer recognized

2020-04-13 Thread Michael Felt


Michael Felt  added the comment:

Thank you!

On 09/04/2020 17:33, STINNER Victor wrote:
> STINNER Victor  added the comment:
>
> I backported the fix to 3.8 to fix AIX 3.8 buildbots.
>
> --
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40112>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40112>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40244] AIX: build: _PyObject_GC_TRACK Asstertion failure

2020-04-10 Thread Michael Felt

Michael Felt  added the comment:

On 10/04/2020 14:01, STINNER Victor wrote:
> STINNER Victor  added the comment:
>
> The assertion failure occurs in _PyObject_GC_TRACK() at:
>
> static void
> gen_dealloc(PyGenObject *gen)
> {
> PyObject *self = (PyObject *) gen;
>
> _PyObject_GC_UNTRACK(gen);
>
> if (gen->gi_weakreflist != NULL)
> PyObject_ClearWeakRefs(self);
>
> _PyObject_GC_TRACK(self);  // < HERE
>
> ...
> }
>
> It's surprising that the generator is still tracked by the GC after 
> _PyObject_GC_UNTRACK().
>
>
>> Calling this a compile error - as it seems to be compiler dependent.
> Do you reproduce the bug if you build Python with GCC?

To be clear - gcc does not not have an issue. As I stated elsewhere - it
is specific to xlc-v16, so likely it is a compiler error.

See also the result of `git bisect` study.

>
> Which ./configure command did you use? What are the compiler and linker flags?
>
> You can try:
>
> ./python -m test.pythoninfo|grep -E 'CFLAGS|CC|OPT|LDFLAGS'

With:

$ ./python -m test.pythoninfo|grep -E 'CFLAGS|CC|OPT|LDFLAGS'
Objects/genobject.c:127: _PyObject_GC_TRACK: Assertion "!(((PyGC_Head
*)(op)-1)->_gc_next != 0)" failed: object already tracked by the garbage
collector
Enable tracemalloc to get the memory block allocation traceback

object address  : 30084150
object refcount : 0
object type : 200144a8
object type name: generator
object repr : 

Fatal Python error: _PyObject_AssertFailed: _PyObject_AssertFailed
Python runtime state: core initialized

Current thread 0x0001 (most recent call first):
  File "", line 1593 in _setup
  File "", line 1634 in _install
  File "", line 1189 in
_install_external_importers
ksh: 27328848 IOT/Abort trap(coredump)

Without error:

$ ./python -m test.pythoninfo|grep -E 'CFLAGS|CC|OPT|LDFLAGS'
os.environ[CC]: xlc_r
sysconfig[CC]: xlc_r
sysconfig[CFLAGS]: -O
sysconfig[CONFIG_ARGS]: '--with-openssl=/opt/aixtools'
'--without-computed-gotos' '--with-pydebug' 'CC=xlc_r'
sysconfig[OPT]: -O
sysconfig[PY_CFLAGS]: -O
sysconfig[PY_CFLAGS_NODIST]: -I./Include/internal
sysconfig[PY_STDMODULE_CFLAGS]: -O -I./Include/internal -I. -I./Include

> --
> nosy: +vstinner
>
> ___
> Python tracker 
> <https://bugs.python.org/issue40244>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue40244>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40244] AIX: build: _PyObject_GC_TRACK Asstertion failure

2020-04-10 Thread Michael Felt


Michael Felt  added the comment:

It is only XLC-v16 that fails. XLC-v11 and XLC-v13 work fine. Am digging to see 
which version (< v16, or >= v16) is not working as expected.

--

___
Python tracker 
<https://bugs.python.org/issue40244>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40244] AIX: build: _PyObject_GC_TRACK Asstertion failure

2020-04-10 Thread Michael Felt


Michael Felt  added the comment:

After git bisect - comes down to:

Bisecting: 0 revisions left to test after this (roughly 0 steps)
[0003c2dc1d4cf5b122e73e83177fd274fa9a9913] bpo-40096: Support 
__attribute__((__noreturn__)) on xlc (GH-19204)

--

___
Python tracker 
<https://bugs.python.org/issue40244>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40244] AIX: build: _PyObject_GC_TRACK Asstertion failure

2020-04-10 Thread Michael Felt


Michael Felt  added the comment:

dbx output:

Again: help appreciated.

(dbx) run  -X tracemalloc
Objects/genobject.c:127: _PyObject_GC_TRACK: Assertion "!(((PyGC_Head 
*)(op)-1)->_gc_next != 0)" failed: object already tracked by the garbage 
collector
Enable tracemalloc to get the memory block allocation traceback

object address  : 30085150
object refcount : 0
object type : 20014188
object type name: generator
object repr : 

Fatal Python error: _PyObject_AssertFailed: _PyObject_AssertFailed
Python runtime state: core initialized

Current thread 0x0001 (most recent call first):
  File "", line 1593 in _setup
  File "", line 1634 in _install
  File "", line 1189 in _install_external_importers

IOT/Abort trap in pthread_kill at 0xd057a02c ($t1)
0xd057a02c (pthread_kill+0xac) 80410014lwz   r2,0x14(r1)
(dbx) where
pthread_kill(??, ??) at 0xd057a02c
_p_raise(??) at 0xd0579408
raise.raise(??) at 0xd0123344
abort() at 0xd0189918
IPRA.$fatal_error(stream = 0x2006e370, header = 805397344, prefix = (nil), msg 
= (nil), status = 0), line 2183 in "pylifecycle.c"
_Py_FatalErrorFunc(func = "", msg = "\n"), line 2283 in "pylifecycle.c"
_PyObject_AssertFailed(obj = 0x30086038, expr = "", msg = (nil), file = 
"\177\200", line = 537322352, function = ""), line 2195 in "object.c"
gen_dealloc(gen = 0x2004af44), line 65532 in "pycore_object.h"
_Py_Dealloc(op = 0x0013), line 2206 in "object.c"
unnamed block in _PyEval_EvalFrameDefault(tstate = 0x2006e370, f = 0x30023b0c, 
throwflag = 804397120), line 1046 in "object.h"
_PyEval_EvalFrameDefault(tstate = 0x2006e370, f = 0x30023b0c, throwflag = 
804397120), line 1046 in "object.h"
unnamed block in IPRA.$function_code_fastcall(tstate = 0x2004af44, co = 
0x20030848, args = 0x30066f7c, nargs = 805735610, globals = 0x30068cb8), line 
40 in "pycore_ceval.h"
IPRA.$function_code_fastcall(tstate = 0x2004af44, co = 0x20030848, args = 
0x30066f7c, nargs = 805735610, globals = 0x30068cb8), line 40 in 
"pycore_ceval.h"
_PyFunction_Vectorcall(func = 0x0006, stack = 0x30083898, nargsf = 
804397328, kwnames = 0x3006e110), line 366 in "call.c"
unnamed block in _PyEval_EvalFrameDefault(tstate = 0x2004af44, f = 0xffe2, 
throwflag = 804397584), line 739 in "abstract.h"
_PyEval_EvalFrameDefault(tstate = 0x2004af44, f = 0xffe2, throwflag = 
804397584), line 739 in "abstract.h"
unnamed block in IPRA.$function_code_fastcall(tstate = 0x2004af44, co = 
0x20030848, args = 0x30023b14, nargs = 805682254, globals = 0x3005bc38), line 
40 in "pycore_ceval.h"
IPRA.$function_code_fastcall(tstate = 0x2004af44, co = 0x20030848, args = 
0x30023b14, nargs = 805682254, globals = 0x3005bc38), line 40 in 
"pycore_ceval.h"
_PyFunction_Vectorcall(func = 0x0005, stack = 0x3005da78, nargsf = 
804397856, kwnames = 0xdeadbeef), line 366 in "call.c"
unnamed block in _PyEval_EvalFrameDefault(tstate = 0x100fbeb8, f = 0x2006e370, 
throwflag = 804398128), line 739 in "abstract.h"
_PyEval_EvalFrameDefault(tstate = 0x100fbeb8, f = 0x2006e370, throwflag = 
804398128), line 739 in "abstract.h"
unnamed block in IPRA.$function_code_fastcall(tstate = 0x10073f50, co = 
0x2000a350, args = 0x20011a58, nargs = 537167132, globals = 0x30049118), line 
40 in "pycore_ceval.h"
IPRA.$function_code_fastcall(tstate = 0x10073f50, co = 0x2000a350, args = 
0x20011a58, nargs = 537167132, globals = 0x30049118), line 40 in 
"pycore_ceval.h"
_PyFunction_Vectorcall(func = 0xd98069bf, stack = 0x0008, nargsf = 
4029698048, kwnames = 0x2006e370), line 366 in "call.c"
IPRA.$_PyObject_CallFunctionVa(tstate = 0x100f6cb0, callable = (nil), format = 
"/\362%\340-zj\244^P^O\242\234/\362&\340^\220K\250 ^D\205^\^PCl\243/\362&\340", 
va = "", is_size_t = 272852043), line 62 in "abstract.h"
IPRA.$callmethod(tstate = 0x100fa29c, callable = 0x2ff226e0, format = (invalid 
char ptr (0x5e904ba8)), va = "", is_size_t = 272854179), line 614 in "call.c"
PyObject_CallMethod(obj = 0x102c266c, name = "", format = "", ... = 0x20077748, 
0x, 0x20077748, 0x20, 0x10), line 634 in "call.c"
init_importlib_external(tstate = 0xdeadbeef), line 209 in "pylifecycle.c"
IPRA.$init_interp_main(tstate = 0x0001), line 993 in "pylifecycle.c"
pyinit_main(tstate = 0x2003c984), line 1097 in "pylifecycle.c"
Py_InitializeFromConfig(config = 0xf078b380), line 1141 in "pylifecycle.c"
pymain_init(args = 0x0001), line 66 in "main.c"
pymain_main(args = 0x0003), line 653 in "main.c"
Py_BytesMain(argc = -559038737, argv = 0xdeadbeef), line 686 in "main.c"
python.main(argc = 0, argv = (nil)), line 16 in "python.c"

--

___
Python tracker 
<https://bugs.python.org/issue40244>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40244] AIX: build: _PyObject_GC_TRACK Asstertion failure

2020-04-10 Thread Michael Felt


New submission from Michael Felt :

Calling this a compile error - as it seems to be compiler dependent.

In other projects - when I have experienced issues as this it has been an 
uninitiated variable - somewhere.

I would appreciate some suggestions on how to best debug this - as it seems to 
occur even before tracemalloc can be activated.

$ ./python -X tracemalloc
Objects/genobject.c:127: _PyObject_GC_TRACK: Assertion "!(((PyGC_Head 
*)(op)-1)->_gc_next != 0)" failed: object already tracked by the garbage 
collector
Enable tracemalloc to get the memory block allocation traceback

object address  : 30085150
object refcount : 0
object type : 20013ea0
object type name: generator
object repr : 

Fatal Python error: _PyObject_AssertFailed: _PyObject_AssertFailed
Python runtime state: core initialized

Current thread 0x0001 (most recent call first):
  File "", line 1593 in _setup
  File "", line 1634 in _install
  File "", line 1189 in _install_external_importers
IOT/Abort trap(coredump)

p.s. I can always build using a different compiler and try to get it to report 
on this object using the values listed above - and/or insert more debug code.

Next step I'll try is using dbx (AIX debugger) for a stacktrace.

Thanks!

--
components: Build
messages: 366112
nosy: David.Edelsohn, Michael.Felt
priority: normal
severity: normal
status: open
title: AIX: build: _PyObject_GC_TRACK Asstertion failure
type: compile error
versions: Python 3.9

___
Python tracker 
<https://bugs.python.org/issue40244>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue37009] Threading and THREAD_SAFE for AIX

2020-04-07 Thread Michael Felt


Michael Felt  added the comment:

Yes, looks like I need to find that. thx for the reminder.

--

___
Python tracker 
<https://bugs.python.org/issue37009>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40112] AIX: xlc - default path changed and no longer recognized

2020-04-07 Thread Michael Felt


Michael Felt  added the comment:

requesting backport of PR19225.

After switching my bot to xlc-v13 it fails this test.

See botstatus mail excerpt:

The Buildbot has detected a failed build on builder POWER6 AIX 3.8 while 
building python/cpython.
Full details are available at:
https://buildbot.python.org/all/#builders/181/builds/216

Buildbot URL: https://buildbot.python.org/all/

Worker for this Build: aixtools-aix-power6

Build Reason: 
Blamelist: Miss Islington (bot) 
<31488909+miss-isling...@users.noreply.github.com>

BUILD FAILED: failed test (failure)


Summary of the results of the build (if available):
===

== Tests result: FAILURE then FAILURE ==

404 tests OK.

10 slowest tests:
- test_multiprocessing_spawn: 2 min 49 sec
- test_concurrent_futures: 2 min 46 sec
- test_bufio: 2 min 18 sec
- test_subprocess: 2 min 4 sec
- test_tokenize: 1 min 43 sec
- test_multiprocessing_forkserver: 1 min 41 sec
- test_tools: 1 min 39 sec
- test_pathlib: 1 min 35 sec
- test_multiprocessing_fork: 1 min 31 sec
- test_ssl: 1 min 23 sec

1 test failed:
test_distutils

--
versions: +Python 3.8

___
Python tracker 
<https://bugs.python.org/issue40112>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40170] [C API] Make PyTypeObject structure an opaque structure in the public C API

2020-04-06 Thread Michael Felt


Michael Felt  added the comment:

Just checked - seems to be SPECIFIC to xlc-v16 as neither xlv-v11 nor xlc-v13 
have any issues building.

--

___
Python tracker 
<https://bugs.python.org/issue40170>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40170] [C API] Make PyTypeObject structure an opaque structure in the public C API

2020-04-06 Thread Michael Felt


Michael Felt  added the comment:

Just manually verified that PR19377, when compiled against xlc - crashes during 
make:

rm -f libpython3.9d.a
ar rcs libpython3.9d.a Modules/getbuildinfo.o  Parser/acceler.o  
Parser/grammar1.o  Parser/listnode.o  Parser/node.o  Parser/parser.o  
Parser/token.o   Parser/myreadline.o Parser/parsetok.o Parser/tokenizer.o  
Objects/abstract.o  Objects/accu.o  Objects/boolobject.o  
Objects/bytes_methods.o  Objects/bytearrayobject.o  Objects/bytesobject.o  
Objects/call.o  Objects/capsule.o  Objects/cellobject.o  Objects/classobject.o  
Objects/codeobject.o  Objects/complexobject.o  Objects/descrobject.o  
Objects/enumobject.o  Objects/exceptions.o  Objects/genobject.o  
Objects/fileobject.o  Objects/floatobject.o  Objects/frameobject.o  
Objects/funcobject.o  Objects/interpreteridobject.o  Objects/iterobject.o  
Objects/listobject.o  Objects/longobject.o  Objects/dictobject.o  
Objects/odictobject.o  Objects/memoryobject.o  Objects/methodobject.o  
Objects/moduleobject.o  Objects/namespaceobject.o  Objects/object.o  
Objects/obmalloc.o  Objects/picklebufobject.o  Objects/rangeobject.o  
Objects/setobject.o 
  Objects/sliceobject.o  Objects/structseq.o  Objects/tupleobject.o  
Objects/typeobject.o  Objects/unicodeobject.o  Objects/unicodectype.o  
Objects/weakrefobject.o  Python/_warnings.o  Python/Python-ast.o  Python/asdl.o 
 Python/ast.o  Python/ast_opt.o  Python/ast_unparse.o  Python/bltinmodule.o  
Python/ceval.o  Python/codecs.o  Python/compile.o  Python/context.o  
Python/dynamic_annotations.o  Python/errors.o  Python/frozenmain.o  
Python/future.o  Python/getargs.o  Python/getcompiler.o  Python/getcopyright.o  
Python/getplatform.o  Python/getversion.o  Python/graminit.o  Python/hamt.o  
Python/import.o  Python/importdl.o  Python/initconfig.o  Python/marshal.o  
Python/modsupport.o  Python/mysnprintf.o  Python/mystrtoul.o  
Python/pathconfig.o  Python/peephole.o  Python/preconfig.o  Python/pyarena.o  
Python/pyctype.o  Python/pyfpe.o  Python/pyhash.o  Python/pylifecycle.o  
Python/pymath.o  Python/pystate.o  Python/pythonrun.o  Python/pytime.o  
Python/bootstrap_hash.o  Python/structmember.o 
  Python/symtable.o  Python/sysmodule.o  Python/thread
.o  Python/traceback.o  Python/getopt.o  Python/pystrcmp.o  Python/pystrtod.o  
Python/pystrhex.o  Python/dtoa.o  Python/formatter_unicode.o  
Python/fileutils.o  Python/dynload_shlib.oModules/config.o  
Modules/getpath.o  Modules/main.o  Modules/gcmodule.o  Modules/posixmodule.o  
Modules/errnomodule.o  Modules/pwdmodule.o  Modules/_sre.o  
Modules/_codecsmodule.o  Modules/_weakref.o  Modules/_functoolsmodule.o  
Modules/_operator.o  Modules/_collectionsmodule.o  Modules/_abc.o  
Modules/itertoolsmodule.o  Modules/atexitmodule.o  Modules/signalmodule.o  
Modules/_stat.o  Modules/timemodule.o  Modules/_threadmodule.o  
Modules/_localemodule.o  Modules/_iomodule.o Modules/iobase.o Modules/fileio.o 
Modules/bytesio.o Modules/bufferedio.o Modules/textio.o Modules/stringio.o  
Modules/faulthandler.o  Modules/_tracemalloc.o Modules/hashtable.o  
Modules/symtablemodule.o  Modules/xxsubtype.o  Python/frozen.o
./Modules/makexp_aix Modules/python.exp . libpython3.9d.a;  xlc_r 
-Wl,-bE:Modules/python.exp -lld -o python Programs/python.o libpython3.9d.a 
-lintl -ldl  -lm   -lm 
 ./python -E -S -m sysconfig --generate-posix-vars ; if test $? -ne 0 ; 
then  echo "generate-posix-vars failed" ;  rm -f ./pybuilddir.txt ;  exit 1 ;  
fi
Objects/genobject.c:127: _PyObject_GC_TRACK: Assertion "!(((PyGC_Head 
*)(op)-1)->_gc_next != 0)" failed: object already tracked by the garbage 
collector
Enable tracemalloc to get the memory block allocation traceback
object address  : 30084150
object refcount : 0
object type : 20013aa8
object type name: generator
object repr : 
Fatal Python error: _PyObject_AssertFailed: _PyObject_AssertFailed
Python runtime state: core initialized
Current thread 0x0001 (most recent call first):
  File "", line 1593 in _setup
  File "", line 1634 in _install
  File "", line 1189 in _install_external_importers
/bin/sh: 24117648 IOT/Abort trap(coredump)
make: 1254-004 The error code from the last command is 134.
Stop.

FYI: about two hours ago I verified that xlc and 
08050e959e6c40839cd2c9e5f6a4fd1513e3d605 : bpo-40147: Fix a compiler warning on 
Windows in Python/compile.c (GH-19389)

all was green.

--
nosy: +Michael.Felt

___
Python tracker 
<https://bugs.python.org/issue40170>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40155] AIX: test_builtin.test_input_no_stdout_fileno() hangs

2020-04-03 Thread Michael Felt


Michael Felt  added the comment:

Thanks for the fix!

--

___
Python tracker 
<https://bugs.python.org/issue40155>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40155] AIX: test_builtin.test_input_no_stdout_fileno() hangs

2020-04-02 Thread Michael Felt


Change by Michael Felt :


--
keywords: +patch
pull_requests: +18671
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/19308

___
Python tracker 
<https://bugs.python.org/issue40155>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31160] Enhance support.reap_children()

2020-04-02 Thread Michael Felt


Change by Michael Felt :


--
pull_requests: +18670
pull_request: https://github.com/python/cpython/pull/19308

___
Python tracker 
<https://bugs.python.org/issue31160>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40155] AIX: test_builtin.test_input_no_stdout_fileno() hangs

2020-04-02 Thread Michael Felt


Michael Felt  added the comment:

To get it to move forward: as it is not solely and AIX thing (see bpo-40-140) 

This works: but is it what is wanted?

Tests result: SUCCESS
aixtools@x064:[/home/aixtools/py39-3.9]git diff
diff --git a/Lib/test/test_builtin.py b/Lib/test/test_builtin.py
index eaada1b504..4a5addc6fe 100644
--- a/Lib/test/test_builtin.py
+++ b/Lib/test/test_builtin.py
@@ -1893,12 +1893,18 @@ class PtyTests(unittest.TestCase):
 self.fail("got %d lines in pipe but expected 2, child output 
was:\n%s"
   % (len(lines), child_output))

-# Wait until the child process completes before closing the PTY to
-# prevent sending SIGHUP to the child process.
-support.wait_process(pid, exitcode=0)
+if sys.platform == "linux" or not os.name == "posix":
+# Wait until the child process completes before closing the PTY to
+# prevent sending SIGHUP to the child process.
+support.wait_process(pid, exitcode=0)

-# Close the PTY
-os.close(fd)
+# Close the PTY
+os.close(fd)
+else:
+# Other posix need to close the pty for the child to exit normally
+# Close the PTY
+os.close(fd)
+support.wait_process(pid, exitcode=0)

--
type:  -> behavior

___
Python tracker 
<https://bugs.python.org/issue40155>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40155] AIX: test_builtin.test_input_no_stdout_fileno() hangs

2020-04-02 Thread Michael Felt


Michael Felt  added the comment:

FYI: in child block:

calling os.exit(0), rather than os._exit() gives same result.

--

___
Python tracker 
<https://bugs.python.org/issue40155>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40155] AIX: test_builtin.test_input_no_stdout_fileno() hangs

2020-04-02 Thread Michael Felt


Michael Felt  added the comment:

Next debug info:

I am child - this is my PID:8519830
I am parent:18284612 with child:8519830fd:6 input:b'quux\r'
I am parent:18284612 with lines:[]
I am child - exiting PID:8519830
I am parent:18284612 with lines:['stdin.isatty(): True']
I am parent:18284612 with lines:['stdin.isatty(): True', "captured: 'prompt'"]
I am parent:18284612 starting wait_process(8519830, exitcode=0)[2] + Stopped 
(SIGTSTP)./python -m test test_builtin
aixtools@x064:[/home/aixtools/py39-3.9]ps -p 8519830
  PIDTTY  TIME CMD
  8519830- 
aixtools@x064:[/home/aixtools/py39-3.9]kill 8519830
aixtools@x064:[/home/aixtools/py39-3.9]ps -p 8519830
  PIDTTY  TIME CMD
  8519830- 
aixtools@x064:[/home/aixtools/py39-3.9]kill -9 8519830
aixtools@x064:[/home/aixtools/py39-3.9]ps -p 8519830
  PIDTTY  TIME CMD
  8519830- 
aixtools@x064:[/home/aixtools/py39-3.9]fg
./python -m test test_builtin
[2] + Stopped (SIGTSTP)./python -m test test_builtin
aixtools@x064:[/home/aixtools/py39-3.9]ps -p 8519830
  PIDTTY  TIME CMD
  8519830- 

--

___
Python tracker 
<https://bugs.python.org/issue40155>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40155] AIX: test_builtin.test_input_no_stdout_fileno() hangs

2020-04-02 Thread Michael Felt


Michael Felt  added the comment:

I tried moving the child/parent logic blocks and get this as debug output:

aixtools@x064:[/home/aixtools/py39-3.9]./python -m test test_builtin
0:00:00 Run tests sequentially
0:00:00 [1/1] test_builtin

I am child - this is my PID:8519822
I am parent:6422696 with child:8519822fd:6 input:b'quux\r'
I am child - exiting PID:8519822
I am parent:6422696 with lines:[]
I am parent:6422696 with lines:['stdin.isatty(): True']
I am parent:6422696 with lines:['stdin.isatty(): True', "captured: 'prompt'"]
I am parent:6422696 starting wait_process(8519822, exitcode=0)

+++
Diff as attachment...

--
Added file: https://bugs.python.org/file49027/test_builtin.txt

___
Python tracker 
<https://bugs.python.org/issue40155>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40155] AIX: test_builtin.test_input_no_stdout_fileno() hangs

2020-04-02 Thread Michael Felt


Michael Felt  added the comment:

If I move the close to before the support.waitprocess() call I get:

aixtools@x064:[/home/aixtools/py39-3.9]./python -m test test_builtin
0:00:00 Run tests sequentially
0:00:00 [1/1] test_builtin

I am child - this is my PID:2254
I am parent:21954666 with child:2254fd:6 input:b'quux\r'
I am parent:21954666 with lines:[]
I am child - exiting PID:2254
I am parent:21954666 with lines:['stdin.isatty(): True']
I am parent:21954666 with lines:['stdin.isatty(): True', "captured: 'prompt'"]
I am parent:21954666 starting wait_process(2254, exitcode=0)
I am parent:21954666 with child:2256fd:6 input:b'quux\r\n'
I am parent:21954666 with lines:[]
I am child - this is my PID:2256
I am child - exiting PID:2256
I am parent:21954666 with lines:['tty = True']
I am parent:21954666 with lines:['tty = True', "'quux'"]
I am parent:21954666 starting wait_process(2256, exitcode=0)
I am parent:21954666 with child:2258fd:6 input:b'quux\xe9\r\n'
I am parent:21954666 with lines:[]
I am child - this is my PID:2258
I am child - exiting PID:2258
I am parent:21954666 with lines:['tty = True']
I am parent:21954666 with lines:['tty = True', "'quux\\udce9'"]
I am parent:21954666 starting wait_process(2258, exitcode=0)
I am parent:21954666 with child:22544450fd:6 input:b'quux\xe9\r\n'
I am parent:21954666 with lines:[]
I am child - this is my PID:22544450
I am child - exiting PID:22544450
I am parent:21954666 with lines:['tty = True']
I am parent:21954666 with lines:['tty = True', "'quux\\udce9'"]
I am parent:21954666 starting wait_process(22544450, exitcode=0)
== Tests result: SUCCESS ==

1 test OK.

--

___
Python tracker 
<https://bugs.python.org/issue40155>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40155] AIX: test_builtin.test_input_no_stdout_fileno() hangs

2020-04-02 Thread Michael Felt


Michael Felt  added the comment:

Now consistently - stalled.

aixtools@x064:[/home/aixtools/py39-3.9]git diff
diff --git a/Lib/test/test_builtin.py b/Lib/test/test_builtin.py
index eaada1b504..89c4ebc2bd 100644
--- a/Lib/test/test_builtin.py
+++ b/Lib/test/test_builtin.py
@@ -1849,26 +1849,40 @@ class PtyTests(unittest.TestCase):

 if pid == 0:
 # Child
+pid = os.getpid() # get my PID
+tty = open("/dev/pts/3", "a")
+tty.write("\nI am child - this is my PID:{}".format(pid))
+tty.close()
 try:
 # Make sure we don't get stuck if there's a problem
-signal.alarm(2)
+# signal.alarm(2)
 os.close(r)
 with open(w, "w") as wpipe:
 child(wpipe)
 except:
 traceback.print_exc()
 finally:
+tty = open("/dev/pts/3", "a")
+tty.write("\nI am child - exiting PID:{}".format(pid))
+tty.close()
 # We don't want to return to unittest...
 os._exit(0)

 # Parent
 os.close(w)
+tty = open("/dev/pts/3", "a")
+tty.write("\nI am parent:{} with child:{}".format(os.getpid(), pid))
+tty.write("fd:{} input:{}".format(fd, terminal_input))
+tty.close()
 os.write(fd, terminal_input)

 # Get results from the pipe
 with open(r, "r") as rpipe:
 lines = []
 while True:
+tty = open("/dev/pts/3", "a")
+tty.write("\nI am parent:{} with lines:{}".format(os.getpid(), 
lines))
+tty.close()
 line = rpipe.readline().strip()
 if line == "":
 # The other end was closed => the child exited
@@ -1895,6 +1909,9 @@ class PtyTests(unittest.TestCase):

 # Wait until the child process completes before closing the PTY to
 # prevent sending SIGHUP to the child process.
+tty = open("/dev/pts/3", "a")
+tty.write("\nI am parent:{} starting wait_process({}, 
exitcode=0)".format(os.getpid(), pid))
+tty.close()
 support.wait_process(pid, exitcode=0)

 # Close the PTY

 Debug 
aixtools@x064:[/home/aixtools/py39-3.9]./python -m test test_builtin
0:00:00 Run tests sequentially
0:00:00 [1/1] test_builtin

I am child - this is my PID:2250
I am parent:21954660 with child:2250fd:6 input:b'quux\r'
I am parent:21954660 with lines:[]
I am child - exiting PID:2250
I am parent:21954660 with lines:['stdin.isatty(): True']
I am parent:21954660 with lines:['stdin.isatty(): True', "captured: 'prompt'"]
I am parent:21954660 starting wait_process(2250, exitcode=0)

--

___
Python tracker 
<https://bugs.python.org/issue40155>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40155] AIX: bot status: stuck at: failed test (failure) uploading test-results.xml (failure)

2020-04-02 Thread Michael Felt


Michael Felt  added the comment:

did not get issue numbers in above: issue31160 and issue40094.

I waited a day, before posting - in the hope it would go away.

Also, I have been testing manually (no -j arguments) - and test_builtin passes 
when run manually. So, becoming hard to dissect and propose a "cure".

I have started with:

./python  ./Tools/scripts/run_tests.py -j 1 -u all -W --slowest 
--fail-env-changed --timeout=1200 -j2

and now see the test stalled:

0:39:41 running: test_builtin (5 min 14 sec)
0:40:11 running: test_builtin (5 min 44 sec)
0:40:41 running: test_builtin (6 min 14 sec)
0:41:11 running: test_builtin (6 min 44 sec)
0:41:41 running: test_builtin (7 min 14 sec)
0:42:11 running: test_builtin (7 min 44 sec)
0:42:41 running: test_builtin (8 min 14 sec)
0:43:11 running: test_builtin (8 min 44 sec)

--

___
Python tracker 
<https://bugs.python.org/issue40155>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40155] AIX: bot status: stuck at: failed test (failure) uploading test-results.xml (failure)

2020-04-02 Thread Michael Felt


New submission from Michael Felt :

related to 

Two AIX bots - different environments - continue to fail the test: 
`test_builtin` since

During the first run - the test fails with something such as:

0:31:47 [215/420] test_abc passed -- running: test_builtin (14 min 10 sec)
0:32:17 running: test_builtin (14 min 40 sec), test_decimal (30.0 sec)
0:32:37 [216/420] test_decimal passed (49.4 sec) -- running: test_builtin (15 
min)
0:32:37 [217/420/1] test_builtin crashed (Exit code 1)
Timeout (0:15:00)!
Thread 0x0001 (most recent call first):

And in the second pass (re-run of failed tests) the failure goes:

test_zip (test.test_builtin.BuiltinTest) ... ok
test_zip_bad_iterable (test.test_builtin.BuiltinTest) ... ok
test_zip_pickle (test.test_builtin.BuiltinTest) ... ok
Timeout (0:15:00)!
Thread 0x0001 (most recent call first):
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/support/__init__.py",
 line 3435 in wait_process
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/test_builtin.py",
 line 1898 in run_child
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/test_builtin.py",
 line 1952 in test_input_no_stdout_fileno
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/case.py", 
line 616 in _callTestMethod
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/case.py", 
line 659 in run
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/case.py", 
line 719 in __call__
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/suite.py", 
line 122 in run
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/suite.py", 
line 84 in __call__
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/suite.py", 
line 122 in run
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/suite.py", 
line 84 in __call__
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/suite.py", 
line 122 in run
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/suite.py", 
line 84 in __call__
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/runner.py",
 line 176 in run
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/support/__init__.py",
 line 2079 in _run_suite
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/support/__init__.py",
 line 2201 in run_unittest
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/runtest.py",
 line 209 in _test_module
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/runtest.py",
 line 234 in _runtest_inner2
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/runtest.py",
 line 270 in _runtest_inner
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/runtest.py",
 line 153 in _runtest
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/runtest.py",
 line 193 in runtest
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/main.py",
 line 318 in rerun_failed_tests
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/main.py",
 line 691 in _main
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/main.py",
 line 634 in main
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/main.py",
 line 712 in main
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/__main__.py", 
line 2 in 
  File "/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/runpy.py", 
line 87 in _run_code
  File "/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/runpy.py", 
line 197 in _run_module_as_main
make: 1254-004 The error code from the last command is 1.
Stop.
program finished with exit code 2
elapsedTime=3610.362052
test_input_no_stdout_fileno (test.test_builtin.PtyTests) ... 

NOTE: the run has stopped with the line

test_input_no_stdout_fileno (test.test_builtin.PtyTests) ... 

and, so the results also fail to get uploaded.

--
components: Tests
messages: 365583
nosy: Michael.Felt
priority: normal
severity: normal
status: open
title: AIX: bot status: stuck at: failed test (failure) uploading 
test-results.xml (failure)
versions: Python 3.9

___
Python tracker 
<https://bugs.python.org/issue40155>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31160] Enhance support.reap_children()

2020-04-01 Thread Michael Felt


Michael Felt  added the comment:

I think something is not yet what it needs to be:

the bots both finish test with:

test_zip_pickle (test.test_builtin.BuiltinTest) ... ok
Timeout (0:15:00)!
Thread 0x0001 (most recent call first):
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/support/__init__.py",
 line 3435 in wait_process
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/test_builtin.py",
 line 1898 in run_child
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/test_builtin.py",
 line 1952 in test_input_no_stdout_fileno
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/case.py", 
line 616 in _callTestMethod
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/case.py", 
line 659 in run
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/case.py", 
line 719 in __call__
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/suite.py", 
line 122 in run
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/suite.py", 
line 84 in __call__
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/suite.py", 
line 122 in run
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/suite.py", 
line 84 in __call__
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/suite.py", 
line 122 in run
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/suite.py", 
line 84 in __call__
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/unittest/runner.py",
 line 176 in run
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/support/__init__.py",
 line 2079 in _run_suite
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/support/__init__.py",
 line 2201 in run_unittest
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/runtest.py",
 line 209 in _test_module
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/runtest.py",
 line 234 in _runtest_inner2
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/runtest.py",
 line 270 in _runtest_inner
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/runtest.py",
 line 153 in _runtest
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/runtest.py",
 line 193 in runtest
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/main.py",
 line 318 in rerun_failed_tests
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/main.py",
 line 691 in _main
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/main.py",
 line 634 in main
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/libregrtest/main.py",
 line 712 in main
  File 
"/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/test/__main__.py", 
line 2 in 
  File "/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/runpy.py", 
line 87 in _run_code
  File "/home/buildbot/buildarea/3.x.aixtools-aix-power6/build/Lib/runpy.py", 
line 197 in _run_module_as_main
make: 1254-004 The error code from the last command is 1.
Stop.
program finished with exit code 2
elapsedTime=3501.292487
test_input_no_stdout_fileno (test.test_builtin.PtyTests) ... 

And the bot status is still FAIL (aka red): failed test (failure) uploading 
test-results.xml (failure)

--

___
Python tracker 
<https://bugs.python.org/issue31160>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31160] Enhance support.reap_children()

2020-04-01 Thread Michael Felt


Michael Felt  added the comment:

Ah - great. Sorry for the noise then.

--

___
Python tracker 
<https://bugs.python.org/issue31160>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31160] Enhance support.reap_children()

2020-04-01 Thread Michael Felt


Michael Felt  added the comment:

With PR19263 The AIX bots are now red.

==
ERROR: test_input_no_stdout_fileno (test.test_builtin.PtyTests)
--
Traceback (most recent call last):
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_builtin.py",
 line 1952, in test_input_no_stdout_fileno
lines = self.run_child(child, b"quux\r")
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_builtin.py",
 line 1898, in run_child
support.wait_process(pid, exitcode=0)
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/support/__init__.py",
 line 3432, in wait_process
os.kill(pid, signal.SIGKILL)
NameError: name 'signal' is not defined
--
Ran 101 tests in 30.348s
FAILED (errors=1, skipped=7)
1 test failed again:
test_builtin

+++
The Buildbot has detected a failed build on builder PPC64 AIX 3.x while 
building python/cpython.
Full details are available at:
https://buildbot.python.org/all/#builders/227/builds/565

Buildbot URL: https://buildbot.python.org/all/

Worker for this Build: edelsohn-aix-ppc64
Worker for this Build: aixtools-aix-power6

--
nosy: +Michael.Felt

___
Python tracker 
<https://bugs.python.org/issue31160>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40112] AIX: xlc - default path changed and no longer recognized

2020-03-30 Thread Michael Felt


Change by Michael Felt :


--
keywords: +patch
pull_requests: +18587
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/19225

___
Python tracker 
<https://bugs.python.org/issue40112>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40112] AIX: xlc - default path changed and no longer recognized

2020-03-30 Thread Michael Felt


New submission from Michael Felt :

The is a check if compiler is xlc, and skips a test if it is.

XLC no longer installs in /usr/vac, and the test_search_cpp fails (again)

--
components: Distutils
messages: 365302
nosy: Michael.Felt, dstufft, eric.araujo
priority: normal
severity: normal
status: open
title: AIX: xlc - default path changed and no longer recognized
type: behavior

___
Python tracker 
<https://bugs.python.org/issue40112>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40069] Clear .lst files for AIX

2020-03-30 Thread Michael Felt


Michael Felt  added the comment:

FYI: IMHO it is artifact of the way an xlc compiler is setup. Maybe this is a 
new default (I see they changed the names of config files).

On my server (with xlc v11) I do not get them, but on a different server (with 
xlc v13) I do get .lst files.

So, seems it is now a good idea to have this.

--

___
Python tracker 
<https://bugs.python.org/issue40069>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue18987] distutils.utils.get_platform() for 32-bit Python on a 64-bit machine

2020-03-26 Thread Michael Felt


Michael Felt  added the comment:

Back again - I understood a lot less then, maybe more now..

iirc, get_platform() asin sysconfig.get_platform() and 
distutils.util.get_platform() are suppposed to return a suitable PEP425 tag 
that identifies the ABI of the running interpreter - eg.g, 32-bit even though 
operating on 64-bot OS and hardware.

As far as AIX goes, for years this was not the case. More recently (for Python 
3.9) the logic has been added so that the bitness of the interpreter can be 
identified.

i.e., on AIX `get_platform()` now returns:
'aix-5307-0747-64' - where the 64 (or 32) identifies the bitness of the 
interpreter.

So, my question now - are the PEP425 tags returned by other platforms adequate? 
If yes, then I see little reason to not close this issue as resolved 
(elsewhere).

--

___
Python tracker 
<https://bugs.python.org/issue18987>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40073] AIX: python3 points to "air"

2020-03-26 Thread Michael Felt


Michael Felt  added the comment:

I see that it is also incorrect for v3.5.9

What is surprising - is that the logic is okay for python-config -> 
python-config3.X -> python-config-3.Xm

root@x065:[/data/prj/python/python3-3.5.9/X32]ls -l opt/bin
total 8728
lrwxrwxrwx   1 root system8 Mar 26 13:14 2to3 -> 2to3-3.5
-rwxr-xr-x   1 bin  bin  95 Mar 26 10:47 2to3-3.5
-rwxr-xr-x   1 bin  bin 236 Mar 26 10:47 easy_install-3.5
lrwxrwxrwx   1 root system7 Mar 26 13:14 idle3 -> idle3.5
-rwxr-xr-x   1 bin  bin  93 Mar 26 10:47 idle3.5
-rwxr-xr-x   1 bin  bin 208 Mar 26 10:47 pip3
-rwxr-xr-x   1 bin  bin 208 Mar 26 10:47 pip3.5
lrwxrwxrwx   1 root system8 Mar 26 13:14 pydoc3 -> pydoc3.5
-rwxr-xr-x   1 bin  bin  78 Mar 26 10:47 pydoc3.5
lrwxrwxrwx   1 root system9 Mar 26 13:14 python3 -> python3.5
lrwxrwxrwx   1 root system   16 Mar 26 13:14 python3-config -> 
python3.5-config
lrwxrwxrwx   1 root system   17 Mar 26 13:14 python3.5-config -> 
python3.5m-config
-rwxr-xr-x   1 bin  bin 4429283 Mar 26 10:45 python3.5m
-rwxr-xr-x   1 bin  bin3005 Mar 26 10:47 python3.5m-config
lrwxrwxrwx   1 root system   10 Mar 26 13:14 pyvenv -> pyvenv-3.5
-rwxr-xr-x   1 bin  bin 230 Mar 26 10:47 pyvenv-3.5

--

___
Python tracker 
<https://bugs.python.org/issue40073>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40073] AIX: python3 points to "air"

2020-03-26 Thread Michael Felt


Change by Michael Felt :


--
versions: +Python 3.5

___
Python tracker 
<https://bugs.python.org/issue40073>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40073] AIX: python3 points to "air"

2020-03-26 Thread Michael Felt


Michael Felt  added the comment:

I tried looking at the blurbs to get an idea of what might have been the change 
- but nothing to indicate a change to the install process in any of "next" NEWS 
blurbs that are currently in branch 3.7

NEWS.d/next/Build/README.rst
NEWS.d/next/C API/2020-03-08-22-56-22.bpo-38643.k2ixx6.rst
NEWS.d/next/C API/2020-03-12-00-27-26.bpo-39884.CGOJBO.rst
NEWS.d/next/C API/README.rst
NEWS.d/next/Core and Builtins/2018-09-23-16-32-58.bpo-22490.8e0YDf.rst
NEWS.d/next/Core and Builtins/2020-02-02-00-12-07.bpo-39520.uicBq6.rst
NEWS.d/next/Core and Builtins/2020-03-06-06-12-37.bpo-39871.dCAj_2.rst
NEWS.d/next/Core and Builtins/2020-03-06-21-04-39.bpo-38894.nfcGKv.rst
NEWS.d/next/Core and Builtins/2020-03-23-18-08-34.bpo-20526.NHNZIv.rst
NEWS.d/next/Core and Builtins/README.rst
NEWS.d/next/Documentation/2020-02-18-14-28-31.bpo-39677.vNHqoX.rst
NEWS.d/next/Documentation/README.rst
NEWS.d/next/IDLE/2020-03-06-01-55-14.bpo-39852.QjA1qF.rst
NEWS.d/next/IDLE/2020-03-08-14-27-36.bpo-39885.29ERiR.rst
NEWS.d/next/IDLE/2020-03-09-02-45-12.bpo-27115.8hSHMo.rst
NEWS.d/next/IDLE/README.rst
NEWS.d/next/Library/2020-03-05-00-57-49.bpo-39828.yWq9NJ.rst
NEWS.d/next/Library/2020-03-09-01-45-06.bpo-39850.eaJNIE.rst
NEWS.d/next/Library/2020-03-23-17-52-00.bpo-40014.Ya70VG.rst
NEWS.d/next/Library/2020-03-09-18-56-27.bpo-39916.BHHyp3.rst
NEWS.d/next/Library/2020-03-10-15-32-31.bpo-38662.o1DMXj.rst
NEWS.d/next/Library/2020-03-11-23-08-25.bpo-39652.gbasrk.rst
NEWS.d/next/Library/2020-03-19-19-40-27.bpo-40016.JWtxqJ.rst
NEWS.d/next/Library/README.rst
NEWS.d/next/Security/2020-03-14-14-57-44.bpo-38576.OowwQn.rst
NEWS.d/next/Security/README.rst
NEWS.d/next/Tests/2020-03-18-16-04-33.bpo-27807.9gKjET.rst
NEWS.d/next/Tests/README.rst
NEWS.d/next/Tools-Demos/2020-03-07-18-01-30.bpo-39889.l1czT6.rst
NEWS.d/next/Tools-Demos/2020-03-09-13-28-13.bpo-36184.BMPJ0D.rst
NEWS.d/next/Tools-Demos/README.rst
NEWS.d/next/Windows/2020-03-04-17-05-11.bpo-39847.C3N2m3.rst
NEWS.d/next/Windows/2020-03-11-10-15-56.bpo-39930.LGHw1j.rst
NEWS.d/next/Windows/README.rst
NEWS.d/next/macOS/README.rst

--

___
Python tracker 
<https://bugs.python.org/issue40073>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue40073] AIX: python3 points to "air"

2020-03-26 Thread Michael Felt


New submission from Michael Felt :

This is a regression in v3.6.10 and v3.7.6

`make install` creates a symbolic link `python3` that points to the executable 
python3.X

In versions v3.6.10 and v3.7.6 the executable is created as python3.Xm while 
the symbolic link still points to python3.X

Note: v3.8.2 and v3.9 (master) do not appear to be affected)

--
components: Build
messages: 365058
nosy: Michael.Felt
priority: normal
severity: normal
status: open
title: AIX: python3 points to "air"
type: behavior
versions: Python 3.6, Python 3.7

___
Python tracker 
<https://bugs.python.org/issue40073>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



  1   2   3   4   5   6   7   8   >