action #36313
open[qe-core][sle][opensuse][qem] enhance update_packagekit tests
0%
Description
Observation¶
In the update tests we depend highly on which types of updates are available, so we do not test every branch in every build (e.g. we have no updates that require a reboot)
To test as much as possible there are update tests in: http://download.opensuse.org/update/leap/15.0/oss/x86_64/
We should try to integrate this to our tests, not only for leap but for all products
Acceptance criteria¶
AC1: Tests are not broken
AC2: All sorts of updates are being tested on opensuse
AC3: All sorts of updates are being tested on sle
Suggestions¶
- Do not test updates on openSUSE Tumbleweed because updates there are less important and seldom and we do not have an update repo with test packages
- For SLE or Leap make sure that the published update-repo with test update packages (see #36451) are available, at least as long as BETA=1 is set
Updated by jorauch almost 6 years ago
- Copied from action #28875: [sle][functional][sporadic][hard][u] test fails in updates_packagekit_gpk - updater should not be started when already running added
Updated by jorauch almost 6 years ago
- Status changed from Feedback to Workable
- Priority changed from High to Normal
Updated by okurz almost 6 years ago
- Priority changed from Normal to Low
- Target version changed from Milestone 16 to Milestone 18
It's a cool idea but that high prio for now. So sure, you can continue to work on this as a fall-back task for now and eventually we should also pick it up with higher prio again.
Updated by jorauch almost 6 years ago
- Priority changed from Low to Normal
- Target version changed from Milestone 18 to Milestone 16
The question here is at wich point we should add the new repo.
I would do this in a seperate module to keep it flexible enough for all products and architectures
Maybe we could use zypper_ar for this
Updated by okurz almost 6 years ago
- Related to action #36451: [functional][y] Testing presence or absence of update-test* packages on iso, based on BETA flag added
Updated by okurz almost 6 years ago
did you change the prio + milestone intentionally?
Updated by jorauch almost 6 years ago
- Priority changed from Normal to Low
- Target version changed from Milestone 16 to Milestone 18
Nope, that happened when adding the last comment, sorry for that
Updated by okurz almost 6 years ago
- Target version changed from Milestone 18 to Milestone 18
Updated by jorauch over 5 years ago
related PR by dheidler:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5477
Updated by mgriessmeier over 5 years ago
- Blocked by action #38393: [functional][u] updates_packagekit_kde must not be scheduled before zypper_clear_repos added
Updated by mgriessmeier over 5 years ago
- Status changed from Workable to Blocked
blocked by https://progress.opensuse.org/issues/38393
Updated by okurz over 5 years ago
- Status changed from Blocked to Workable
blocker resolved. I think this covers "do not look for updates on TW" already. If in doubt talk to @dheidler please.
Updated by okurz over 5 years ago
- Due date changed from 2018-08-14 to 2018-08-28
bulk move to next sprint as could not be discussed in SR
Updated by okurz over 5 years ago
- Due date changed from 2018-08-28 to 2018-09-11
- Target version changed from Milestone 18 to Milestone 19
we got interrupted on that one for the time being. We have too many tickets planned for current S24 so let's delay some time
Updated by jorauch over 5 years ago
I would like to delay this until the return of dheidler
Updated by mgriessmeier over 5 years ago
- Due date changed from 2018-09-11 to 2018-09-25
Updated by mgriessmeier over 5 years ago
- Due date changed from 2018-09-25 to 2018-10-09
- Assignee deleted (
jorauch)
Updated by okurz over 5 years ago
- Due date deleted (
2018-10-09) - Target version changed from Milestone 19 to future
@riafarov is currently working on harmonizing the update schedule which might have an impact and someone from QAM plans to look into update_packagekit_kde as well. We can look into this but … not now.
Updated by mgriessmeier about 4 years ago
- Status changed from Workable to Rejected
We don't know currently what parts of this is already covered and what not - please reopen or create a proper one with explicit request
Updated by okurz about 4 years ago
- Subject changed from [sle][opensuse][functional][medium][u] enhance update_packagekit tests to [sle][opensuse][qam] enhance update_packagekit tests
- Status changed from Rejected to Workable
mgriessmeier wrote:
We don't know currently what parts of this is already covered and what not - please reopen or create a proper one with explicit request
this is a bit lame explanation. The link to test updates needs an update of course: http://download.opensuse.org/update/leap/15.2/oss/x86_64/
This shows all different categories of updates:
- update-test-32bit-pkg
- update-test-affects-package-manager
- update-test-broken
- update-test-feature
- update-test-interactive
- update-test-optional
- update-test-reboot-needed
- update-test-relogin-suggested
- update-test-security
- update-test-trivial
but I think by now it fits better the scope of [qam].
Updated by tjyrinki_suse over 3 years ago
- Subject changed from [sle][opensuse][qam] enhance update_packagekit tests to [qe-core][sle][opensuse][qam] enhance update_packagekit tests
Updated by tjyrinki_suse over 3 years ago
- Subject changed from [qe-core][sle][opensuse][qam] enhance update_packagekit tests to [qe-core][sle][opensuse][qem] enhance update_packagekit tests