Triage and Migration report

[Christian Ehrhardt]

On Tue, Jan 28, 2020 at 9:52 AM Christian Ehrhardt <
christian.ehrhardt at canonical.com> wrote:

> ## Bug Triage ##
>
> Got 27 bugs from last Friday
> But most of them were updates to caes in progress slightly amplified by
> merges that touched a lot of bugs to mark them fixed.
>
> Eventually it came down to a few task/status updates some IRC pings to get
> things moving and just one real new triage.
>
>
> ## Proposed Migration ##
>
> - Qemu:
>   There is a qemu 4.0 with some CVEs hanging on failed build.
>   But I have a qemu 4.2 soon to be ready that works and will fix the same
> issues (and more).
>
> - nss:
>   Is blocked by some JDK tests on arm
>   Two of them seem odd and always fail or skip.
>   The only one that sometimes works is
>   http://autopkgtest.ubuntu.com/packages/o/openjdk-lts/focal/arm64
>   The result is literally "jdk   FLAKY timed out"
>   For now I restarted, but maybe the test should be masked.
>   @Doko - from the uploader it seems you handle openjdk-lts opinions on how
>   to handle its tests?
>
> - crmsh:
>   tests block on new python3-default
>   "crmsh.minieval.FeatureNotAvailable: Sorry, Constant is not available in
> this evaluator"
>   The issue is reproducible outside the test environment.
>   It seems ast processing changed in py3.8
>   Found other changes like "py3.8 uses ast.Constant instead of ast.Num,
> ast.Str,
>   ast.NameConstant" in other projects [2].
>   Seems crmsh needs py3.8 fixes for [3].
>   I came up with a fix and submitted it upstream for review and
> integration there [4]
>   [2]:
> https://github.com/mommothazaz123/simpleeval/commit/65ab6c510563a490f22b7307b7370457cd839afe
> [3]: https://docs.python.org/3/library/ast.html#ast.AST
> [4]: https://github.com/ClusterLabs/crmsh/issues/518
>

I created a PR based on my issue and it got upstream accepted.
I prepared an MP for an Ubuntu upload with the fix.
=>
https://code.launchpad.net/~paelzer/ubuntu/+source/crmsh/+git/crmsh/+merge/378235

- Some more rebuilds got triggered for python3-defaults bump and have issues
>   - samba (andreas is on it)
>   - sssd (andreas will do that as well).
>
> - DPDK breaks indirectly on the new python as well.
>   The tests have a unversioned python dependency that e.g. breaks pciutils
> now.
>   I have a fix [1] in Debian already - needs an upload to debian to merge
> it from there.
>   [1]:
> https://salsa.debian.org/debian/dpdk/commit/bda4445c38450c38adb45a7f833155eaff3e3bf0
>

I have 19.11-3 in Debian now which is python3 compatible.
I could re-merge now but there is no gain as doko uploaded 19.11-2ubuntu2
dumping it to use python2.
That works as well for now and we have no need to merge it for any other
reason.
Therefore - no re-merge needed for now.


>
> P.S. On Focal tests related to python I have seen a zillion of these
> "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering
> (buffering=1) isn't supported in binary mode, the default buffer size will
> be used"
> None in server packages, but I assume some cleanup for that has to follow.
>
> --
> Christian Ehrhardt
> Staff Engineer, Ubuntu Server
> Canonical Ltd
>


-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-server/attachments/20200129/08e15120/attachment.html>