{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiasc3gsfp2q5cwu7aqc3tdjn2r6y36vmi7radmwejfnycqd7todh4",
    "uri": "at://did:plc:46ti67tc37qcmwp2vaynk6fq/app.bsky.feed.post/3mh5wqxwebia2"
  },
  "path": "/blog/debusine-regression-tracking/",
  "publishedAt": "2026-03-16T07:29:29.070Z",
  "site": "https://www.freexian.com",
  "tags": [
    "Debusine",
    "debian_pipeline",
    "native Debusine APT repository",
    "debusine.debian.net",
    "debian:qa-results",
    "qa",
    "for sid",
    "enabled"
  ],
  "textContent": "# Regression Tracking\n\nDebusine is a tool designed for Debian developers and Operating System developers in general. Debusine can run QA pipelines to check that Debian packages are ready to upload. This blog post describes the regression tracking mechanism that’s recently become available in Debusine QA pipelines.\n\nThe debian_pipeline workflow in Debusine can build, test, and upload a package to the Debian archive (or any other repository, such as a native Debusine APT repository). The QA tests involve running the standard Debian QA utilities (`lintian`, `autopkgtest`, `piuparts`, `blhc`) on the built artifacts. In addition we can run the autopkgtests of every other package in the archive that depends on the built package, like britney does for testing migration in Debian. Some of these other packages may have currently-failing autopkgtests that have nothing to do with the changes in the upload under test.\n\nFor example:\n\nFiguring out which of these failures are new (and thus worth investigating) has been a manual process in Debusine until now. We have just completed the basic functionality of the `regression_tracking=true` feature, and have enabled it in the `upload-to-*` workflows on debusine.debian.net.\n\nWith this enabled, you’ll get a new QA tab on your debian_pipeline workflows that shows the trend of each test:\n\nThis is determined by looking at recent task history for each task in the debian:qa-results collection. If there is no recent result for a given <package, version, architecture>, then tasks are queued under the “reference tests” qa workflow tree on the pipeline.\n\nThese reference tests are run by using the same tasks as the main qa workflow, but without the addition of the package under test. In fact, it uses the same qa workflow that we use to check the package, but with a few different parameters to populate the regression tracking results collection.\n\nThe `debian:qa-results` collection used for analyzing regressions is specified to the `debian_pipeline` with the `regression_tracking_qa_results` lookup parameter. On debusine.debian.net we have configured a `debian:qa-results` collection for sid that can be referenced and added to by tasks in any workspace.\n\nRegressions can be more subtle than a simple Success → Failure. If the number of autopkgtests that fail increases, or the number of lintian tags emitted increases, those are also considered a regressions.\n\n## Using regression tracking now\n\nIt’s enabled by default on most of the `upload-to-*` workflows on debusine.debian.net. To disable, pass `-O debusine_workflow_data.enable_regression_tracking=false` when you `dput` an upload to debusine.\n\nTo use the regression-tracking in your own workflows, use a `debian_pipeline` workflow that is configured with `enable_regression_tracking=true`. This will require a `qa_suite` to be specified, pointing to the baseline suite.\n\nWe hope this will make it easier to check QA results for packages tested on debusine.debian.net.",
  "title": "Freexian Collaborators: Regression Tracking in Debusine (by Stefano Rivera)",
  "updatedAt": "2026-03-16T00:00:00.000Z"
}