[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#988998: lava: autopkgtest needs update for new version of pyyaml



Source: lava
Version: 2020.12-3
Severity: serious
X-Debbugs-CC: debian-ci@lists.debian.org, pyyaml@packages.debian.org
Tags: sid bullseye
User: debian-ci@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pyyaml

Dear maintainer(s),

With a recent upload of pyyaml the autopkgtest of lava fails in testing
when that autopkgtest is run with the binary packages of pyyaml from
unstable. It passes when run with only packages from testing. In tabular
form:

                       pass            fail
pyyaml                 from testing    5.3.1-4
lava                   from testing    2020.12-3
all others             from testing    from testing

I copied some of the output at the bottom of this report. It seems that
Ubuntu already has a patch since half of April [0].

Currently this regression is blocking the migration of pyyaml to testing
[1]. Of course, pyyaml shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in pyyaml was
intended and your package needs to update to the new situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from pyyaml should really add
a versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.

More information about this bug and the reason for filing it can be found 
on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] https://patches.ubuntu.com/l/lava/lava_2020.12-1ubuntu2.patch
[1] https://qa.debian.org/excuses.php?package=pyyaml

https://ci.debian.net/data/autopkgtest/testing/amd64/l/lava/12512203/log.gz
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
/usr/lib/python3/dist-packages/lava_common/compat.py:60: in yaml_load
    return yaml.load(data, Loader=Loader)  # nosec
/usr/lib/python3/dist-packages/yaml/__init__.py:114: in load
    return loader.get_single_data()
/usr/lib/python3/dist-packages/yaml/constructor.py:51: in get_single_data
    return self.construct_document(node)
/usr/lib/python3/dist-packages/yaml/constructor.py:60: in construct_document
    for dummy in generator:
/usr/lib/python3/dist-packages/yaml/constructor.py:413: in
construct_yaml_map
    value = self.construct_mapping(node)
/usr/lib/python3/dist-packages/yaml/constructor.py:218: in construct_mapping
    return super().construct_mapping(node, deep=deep)
/usr/lib/python3/dist-packages/yaml/constructor.py:143: in construct_mapping
    value = self.construct_object(value_node, deep=deep)
/usr/lib/python3/dist-packages/yaml/constructor.py:100: in construct_object
    data = constructor(self, node)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

self = <yaml.cyaml.CFullLoader object at 0x2d46280>
node =
MappingNode(tag='tag:yaml.org,2002:python/object/new:lava_dispatcher.device.PipelineDevice',
value=[(ScalarNode(tag='t...ScalarNode(tag='tag:yaml.org,2002:str',
value='target'), ScalarNode(tag='tag:yaml.org,2002:str',
value='black02'))]))])

    def construct_undefined(self, node):
>       raise ConstructorError(None, None,
                "could not determine a constructor for the tag %r" %
node.tag,
                node.start_mark)
E       yaml.constructor.ConstructorError: could not determine a
constructor for the tag
'tag:yaml.org,2002:python/object/new:lava_dispatcher.device.PipelineDevice'
E         in
"/tmp/lava-tests-pecpxeiwqT/tests/lava_scheduler_app/pipeline_refs/connection-description.yaml",
line 2, column 9

/usr/lib/python3/dist-packages/yaml/constructor.py:427: ConstructorError

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: