The python3-buildlog-consultant package now has a "analyse-sbuild-log"
command that can parse and analyse sbuild logs and in most cases
identity the line or lines that explain why a build failed.
E.g.:
% analyse-sbuild-log --json ~/build.log
{"stage": "build", "section": "Build", "lineno": 857, "kind": "missing-python-module", "details": {"module": "setuptools", "python_version": 3, "minimum_version": null}}
This is what powers the line selection for the fragments shown by the
Debian janitor for failed builds.
Cheers,
Jelmer
--
Jelmer Vernooij <jelmer@jelmer.uk>
PGP Key: https://www.jelmer.uk/D729A457.asc
Attachment:
signature.asc
Description: PGP signature