This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pablogsal
Recipients BTaskaya, Michael.Felt, mark.dickinson, miss-islington, ned.deily, pablogsal, skrah, tim.peters, veky
Date 2020-03-17.11:17:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584443852.68.0.62154874673.issue39576@roundup.psfhosted.org>
In-reply-to
Content
> Acknowledge that gcc builds work on the AIX buildbots (a fact that has been entirely ignored so far).

I do acknowledge that. I am not saying that I am sure there is a bug in the code. For what I know at this point
it may be something with xlc, with the OS itself, with the libc version or something misconfigured on the machine.

The only thing I know is that before I could run the test suite without any problem on 3.7.6 and now I cannot
in 3.7.7, and because 3.7 a maintenance branch I though this is a possible regression, so I reported it.

> are you using xlc or xlc_r?

I am using xlc_r. I am saying xlc because that is the name of the compiler. The _r suffix activates thread-safe compilation (which
I am doing). Apologies for the confusion.

> State the exact regression

The **exact** regression is that I could run the test suite without any crash or freeze on this AIX system
with 3.7.6 and I cannot in 3.7.7. At the very least this is due to the fact that there is a new test that crashes/hangs.
Why this happens I still have no idea as I am currently investigating. Debugging on AIX is not a pleasant task.


> n short, given the flakiness of the xlc toolchain I'm not even
sure if anything can be classified as a regression. Most xlc users
I've talked to have switched to gcc.

I notified the behaviour different here so we can discuss about this as a team. If we decide that this is xlc's fault or
is not worth to investigate or that because AIX is not really fully supported we do not want to spend resources I can totally
understand it. I thought this was important enough because this change was in 3.7, which is supposed to be stable across minor
releases (the same applies for 3.8 if the problem also appears there).
History
Date User Action Args
2020-03-17 11:17:32pablogsalsetrecipients: + pablogsal, tim.peters, mark.dickinson, ned.deily, skrah, veky, Michael.Felt, miss-islington, BTaskaya
2020-03-17 11:17:32pablogsalsetmessageid: <1584443852.68.0.62154874673.issue39576@roundup.psfhosted.org>
2020-03-17 11:17:32pablogsallinkissue39576 messages
2020-03-17 11:17:32pablogsalcreate