action #105217
closed
deprecate and prepare removal of os-autoinst backend::amt because it is likely unused and remove if we have no significant code coverage
Added by okurz almost 3 years ago.
Updated almost 3 years ago.
Category:
Feature requests
Description
Motivation¶
I conducted a poll in SUSE QE Tools workshop 2022-01-21 about if people know any test where os-autoinst backends are used and the "backend::amt" came up with 0 matches. Also on OSD I called SQL select * from machines where backend ~ 'amt'; and found no matches. Unless we have significant test code coverage we should mark the amt backend as deprecated and prepare removal because likely no one uses it and it's unlikely to work as expected.
- Status changed from New to In Progress
- Assignee set to okurz
https://app.codecov.io/gh/os-autoinst/os-autoinst shows that the AMT backend is not covered in tests. However it was introduced not that long ago in
commit 396a8b6d
Author: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Date: Tue Aug 7 15:01:42 2018 +0200
I thought it might have been older. So I vote against deprecating and removing it (for now). But we can try to add tests.
- Due date set to 2022-02-04
- Status changed from In Progress to Feedback
PR ready. All checks passed. Waiting for review.
- Due date deleted (
2022-02-04)
- Status changed from Feedback to Resolved
PR merged. With this amt is marked deprecated. Whenever enough time has passed and especially if the backend poses a problem for us we can remove it.
Also available in: Atom
PDF