Project

General

Profile

Bug #16355

Test suite: please detect and warn about “Known issues”…

Added by CyrilBrulebois 4 months ago. Updated 4 months ago.

Status:
In Progress
Priority:
Normal
Category:
Test suite
Target version:
-
Start date:
01/14/2019
Due date:
% Done:

0%

QA Check:
Ready for QA
Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

So I've discovered the fun related to #12142 (i.e. https://bugs.debian.org/851694), after having wasted quite some time on the USB test suite development (#16004).

It has been freshly documented in master (7a6bddabe047a8ba9fb554fc3442d4fa1260e8e1 -- by the way, why not mention the binaries available in the same suite, instead of suggesting a local rebuild?), but I'd hate it to see others (maybe future me with a different setup) lose time over this again.

I'm therefore proposing an extra check, ensuring we have the known good qemu version when running on Debian stretch. This should be a no-op on the isotesters, which have this version installed already.

FWIW, this might also be the reason why I've had so many issues with snapshots while working on the test suite updates for feature/buster (#16314)… I'm currently checking this hypothesis, and will update #16314 accordingly.

Target branches: devel and feature/buster.

0001-Test-suite-check-for-known-issues-to-avoid-wasting-t.patch View (2.02 KB) CyrilBrulebois, 01/14/2019 03:03 AM

History

#1 Updated by CyrilBrulebois 4 months ago

  • Description updated (diff)

#2 Updated by intrigeri 4 months ago

  • Status changed from New to In Progress
  • Assignee changed from intrigeri to CyrilBrulebois

by the way, why not mention the binaries available in the same suite, instead of suggesting a local rebuild?),

I was assuming that at least some developers would be reluctant to add third-party binary APT sources, i.e. to trust our infra to be root on their system. Perhaps I was overly cautious? I'm fine adding the binary APT source if you want.

but I'd hate it to see others (maybe future me with a different setup) lose time over this again.

OK!

I'm therefore proposing an extra check, ensuring we have the known good qemu version when running on Debian stretch. This should be a no-op on the isotesters, which have this version installed already.

Code looks good to me. Please push this to a branch so we confirm it's a no-op on Jenkins before we deploy it :)

Also available in: Atom PDF