Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • qa qa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Debian QADebian QA
  • qaqa
  • Merge requests
  • !19

Fix piuparts

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged David Steele requested to merge steele/qa:fix-piuparts into master Feb 05, 2019
  • Overview 7
  • Commits 2
  • Changes 2

With all due respect, 20d35de3 and 5856ca24 were not the proper changes to effect #856324. As a result, many piuparts tests against "unstable" are no longer being reported. Also, for some reason, the tooltip information has been truncated (the reason I am here).

The right way to incorporate sid-strict into "overall" DDPO results is to include it upstream.

Which, BTW, is already the case , and has been for years (since well before this bug report) (edit, this is wrong). You can verify this by looking for URIs in https://piuparts.debian.org/summary.json including "sid-strict". You'll see that right now there are many reports of packages showing as blocked in the overall report as a result of sid-strict.

The implicit claim in #856324, that sid-strict results were not being reported in DDPO, is false.

Edited Feb 06, 2019 by David Steele
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: fix-piuparts