> Hello all,
>
> Matthias asked me to run all our available autopkgtests with python3.4 as
> default Python 3 (using the PPA [1]), to see the fallout. These should be
> fixed before we consider making 3.4 the default Python3 version. The full
> raw logs are at [2], sorted into pass/ and fail/.
>
> I went through the failures and converted them to LP bugs, so that they can
> be tracked/assigned/etc:
>
> https://bugs.launchpad.net/ubuntu/+bugs?field.tag=python3.4
>
> Please note that some autopkgtests fail due to other reasons (many of them
> have never succeeded at all). Also, this is only the list of 3.3 → 3.4
> regressions that we can detect automatically; of course we have a lot more
> Python packages and code in the archive which isn't covered by
> autopkgtest.
Unfortunately this includes some tests which did fail before too
(python-misaka). Marking these as python3.4 is "interesting".
In general I don't like the way how the introduction of autopkg tests forces
work on maintainers to do for the migration, when you don't have the time to
spend resources or want to use this time to improve packages in other areas.
Developer time is limited, and I'm tired being forced to spend time on broken
autopkg tests and to spend time to hunt down people to ignore failing or
stalling tests on the autopkg test infrastructure.
Matthias
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
