canonical-ubuntu-qa team mailing list archive

[Dave Jones <2054562@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I'm currently running through the ISO tests for Ubuntu 22.04.4
(https://iso.qa.ubuntu.com/qatracker/milestones/451/builds) on various
Raspberry Pi models. Unfortunately, the Pi 5 4GB and 8GB models are
listed as ones that should be tested (e.g.
https://iso.qa.ubuntu.com/qatracker/milestones/451/builds/295998/testcases).
These boards are unsupported on jammy, but appear because the ISO
tracker cannot show/hide/vary tests according to the release being
tested.

I don't particularly want to mark those boards "failed"; that has the
potential to hold up the release when it shouldn't be. Nor do I want to
mark them "passed"; that has the potential to confuse users ("what do
you mean unsupported? It passed on the ISO tracker!"). Obviously the
"proper" fix is to permit variation of tests by release, but perhaps a
simple stop-gap measure would be to add an "unsupported" status for
tests to indicate a state of "deliberately not tested"?

** Affects: ubuntu-qa-website
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Ubuntu QA Website.
https://bugs.launchpad.net/bugs/2054562

Title:
  ISO tracker cannot vary tests by release

Status in Ubuntu QA Website:
  New

Bug description:
  I'm currently running through the ISO tests for Ubuntu 22.04.4
  (https://iso.qa.ubuntu.com/qatracker/milestones/451/builds) on various
  Raspberry Pi models. Unfortunately, the Pi 5 4GB and 8GB models are
  listed as ones that should be tested (e.g.
  https://iso.qa.ubuntu.com/qatracker/milestones/451/builds/295998/testcases).
  These boards are unsupported on jammy, but appear because the ISO
  tracker cannot show/hide/vary tests according to the release being
  tested.

  I don't particularly want to mark those boards "failed"; that has the
  potential to hold up the release when it shouldn't be. Nor do I want
  to mark them "passed"; that has the potential to confuse users ("what
  do you mean unsupported? It passed on the ISO tracker!"). Obviously
  the "proper" fix is to permit variation of tests by release, but
  perhaps a simple stop-gap measure would be to add an "unsupported"
  status for tests to indicate a state of "deliberately not tested"?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-qa-website/+bug/2054562/+subscriptions