GNU bug report logs -
#32088
Python >=3.5 test suite failures
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 32088 in the body.
You can then email your comments to 32088 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-automake <at> gnu.org
:
bug#32088
; Package
automake
.
(Sat, 07 Jul 2018 21:01:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Lukas Fleischer <lfleischer <at> lfos.de>
:
New bug report received and forwarded. Copy sent to
bug-automake <at> gnu.org
.
(Sat, 07 Jul 2018 21:01:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi,
Currently, the automake test suite fails with recent Python versions. I
submitted two patches to address these issues to the automake-patches
mailing list ~7 weeks ago. Any chance we can get these bugs fixed
anytime soon?
Regards,
Lukas
[1] http://lists.gnu.org/archive/html/automake-patches/2018-05/msg00001.html
Information forwarded
to
bug-automake <at> gnu.org
:
bug#32088
; Package
automake
.
(Sat, 07 Jul 2018 21:37:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 32088 <at> debbugs.gnu.org (full text, mbox):
Hello Lukas,
Lukas Fleischer <lfleischer <at> lfos.de> writes:
> Currently, the automake test suite fails with recent Python versions. I
> submitted two patches to address these issues to the automake-patches
> mailing list ~7 weeks ago. Any chance we can get these bugs fixed
> anytime soon?
>
> [1] http://lists.gnu.org/archive/html/automake-patches/2018-05/msg00001.html
I am going to review those.
Thanks for reminding us about that.
--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
Information forwarded
to
bug-automake <at> gnu.org
:
bug#32088
; Package
automake
.
(Mon, 20 Jan 2020 06:27:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 32088 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
> > Currently, the automake test suite fails with recent Python versions. I
> > submitted two patches to address these issues to the automake-patches
> > mailing list ~7 weeks ago. Any chance we can get these bugs fixed
> > anytime soon?
> >
> > [1]
> > http://lists.gnu.org/archive/html/automake-patches/2018-05/msg00001.ht
> > ml>
> I am going to review those.
>
> Thanks for reminding us about that.
Any news here? I mean, Python 2 is going away (if not already gone)...
I've reviewed both patches and added them to the Gentoo version of
automake.
That said, compatibility with recent python isn't complete then.
1) With the second patch I hit the command line length limit in t/instmany-
python.sh, which then fails (no wonder if every file gets prepended
__pycache__/ ...). I've worked around that by increasing the limit in t/
instmany-python.sh from the somewhat arbitrary 2500 to 3200. Neverthlesss,
maybe a more elegant solution is possible.
2) The fix/patch of bug #38043 (Incorrect Python byte-compiling for Python
3 and PyPy3), which we also carry, interferes with t/py-compile-basedir.sh;
the number of generated files (line 47 there) is then (only for recent
Python 3) 6, not 4.
--
Andreas K. Hüttel
dilfridge <at> gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-automake <at> gnu.org
:
bug#32088
; Package
automake
.
(Mon, 20 Jan 2020 23:17:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 32088 <at> debbugs.gnu.org (full text, mbox):
instmany-python.sh from the somewhat arbitrary 2500 to 3200. Neverthlesss,
maybe a more elegant solution is possible.
Seems fine to me. Thanks for finding the workaround.
2) The fix/patch of bug #38043 (Incorrect Python byte-compiling for
Python 3 and PyPy3), which we also carry, interferes with
t/py-compile-basedir.sh; the number of generated files (line 47
there) is then (only for recent Python 3) 6, not 4.
People will surely be running make check on older machines.
Maybe the simplest way is just to accept either 4 or 6 in the stated
test $(echo "$files" | wc -l) -eq 4
as long as those are the only results ... so far ...
Jim, wdyt? --thanks, karl.
Information forwarded
to
bug-automake <at> gnu.org
:
bug#32088
; Package
automake
.
(Tue, 21 Jan 2020 01:01:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 32088 <at> debbugs.gnu.org (full text, mbox):
> 2) The fix/patch of bug #38043 (Incorrect Python byte-compiling for
> Python 3 and PyPy3), which we also carry, interferes with
> t/py-compile-basedir.sh; the number of generated files (line 47
> there) is then (only for recent Python 3) 6, not 4.
>
> People will surely be running make check on older machines.
>
> Maybe the simplest way is just to accept either 4 or 6 in the stated
> test $(echo "$files" | wc -l) -eq 4
> as long as those are the only results ... so far ...
Yep, precisely. This is what I've used:
https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-devel/automake/files/
automake-1.16.1-py3-compile-test.patch
diff -ruN automake-1.16.1.orig/t/py-compile-basedir.sh automake-1.16.1/t/
py-compile-basedir.sh
--- automake-1.16.1.orig/t/py-compile-basedir.sh 2020-01-20
05:07:12.915260159 +0100
+++ automake-1.16.1/t/py-compile-basedir.sh 2020-01-20
05:07:45.827074984 +0100
@@ -42,7 +42,7 @@
py_installed "$d2/$f.pyc"
py_installed "$d2/sub/$f.pyc"
files=$(find "$d2" | grep '\.py[co]$')
- test $(echo "$files" | wc -l) -eq 4
+ test $(echo "$files" | wc -l) -eq 4 -o $(echo "$files" | wc -l) -eq 6
case $d2 in
.|..) rm -f $files;;
*) rm -rf "$d2";;
--
Andreas K. Hüttel
dilfridge <at> gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
Information forwarded
to
bug-automake <at> gnu.org
:
bug#32088
; Package
automake
.
(Sun, 02 Feb 2020 02:15:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 32088 <at> debbugs.gnu.org (full text, mbox):
Hi Andreas, Lukas, and all - I have pushed Lukas's two patches, tweaked
per Andreas's subsequent fixes, and also adjusted for the current sources.
Hope it flies, please reopen if problems. Thanks to all! --karl
Reply sent
to
Karl Berry <karl <at> freefriends.org>
:
You have taken responsibility.
(Sun, 02 Feb 2020 02:15:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Lukas Fleischer <lfleischer <at> lfos.de>
:
bug acknowledged by developer.
(Sun, 02 Feb 2020 02:15:03 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 01 Mar 2020 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 29 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.