Auto Package Testing

There is not consistent way to trigger a baseline test against the release pocket

Bug #1767235 reported by Steve Langasek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Auto Package Testing
Confirmed
Wishlist
Unassigned

Bug Description

I added a --no-proposed option to retry-autopkgtest-regressions which attempts to rerun the tests against only those packages in the release pocket. This fails for the case when the package to be tested does itself have a version in -proposed. Needs server-side support (and possibly the concept of a trigger-less test run) to be able to test only against the release pocket.

Steve Langasek (vorlon)
Changed in auto-package-testing:
importance: Undecided → Wishlist
Revision history for this message
Balint Reczey (rbalint) wrote :

Until this is implemented I use &trigger=hello/... with the version in the target release.

Changed in auto-package-testing:
status: New → Confirmed
Balint Reczey (rbalint)
summary: - consistent way to trigger a baseline test against the release pocket
+ There is not consistent way to trigger a baseline test against the
+ release pocket
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.