action #51296
closed
[functional][u][aarch64][ppc64le][s390x] test fails in transactional_update - missing file utt-sle-aarch64.tgz
Added by dheidler almost 5 years ago.
Updated almost 5 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 24
- Priority changed from Normal to High
- Description updated (diff)
- Assignee set to SLindoMansilla
- Related to action #51314: [sle][functional][u] test fails in transactional_update - never worked before added
- Subject changed from [functional][u] test fails in transactional_update to [functional][u] test fails in transactional_update - wrong test module schedule
- Description updated (diff)
- Related to deleted (action #51314: [sle][functional][u] test fails in transactional_update - never worked before)
- Has duplicate action #51314: [sle][functional][u] test fails in transactional_update - never worked before added
- Status changed from New to Feedback
- Target version set to Milestone 24
- Status changed from Feedback to Resolved
- Subject changed from [functional][u] test fails in transactional_update - wrong test module schedule to [functional][u][aarch64] test fails in transactional_update - missing file utt-sle-aarch64.tgz
- Status changed from Resolved to Workable
- Assignee changed from SLindoMansilla to mkravec
- Priority changed from High to Normal
- Subject changed from [functional][u][aarch64] test fails in transactional_update - missing file utt-sle-aarch64.tgz to [functional][u][aarch64][ppc64le][s390x] test fails in transactional_update - missing file utt-sle-aarch64.tgz
- Description updated (diff)
Tests suite transactional_server moved from main job group to development job group for all architectures until we have a passed test that matches the acceptance criteria.
please, no dirty hacks ;)
- Description updated (diff)
- Description updated (diff)
- Status changed from Workable to Resolved
- Status changed from Resolved to Workable
- Assignee changed from mkravec to SLindoMansilla
AC's are in the description.
Since the test suite are again using the setting INSTALLONLY, this ticket is not resolved.
As spoken I will take over.
Ah, I see :)
AC 3,4 should be met.
About AC 1,2 - we don't need INSTALLONLY for HDD export, we run 1 scenario per platform.
It seems like nice-to-have feature, not hard requirement. Just my 2c - feel free to fix that :)
Can we move jobs back to functional group? I don't think INSTALLONLY variable should be reason for devel group.
- Parent task set to #51362
Should actually be "new", but is not available. Waiting for parent task to be refined.
- Description updated (diff)
- Status changed from Workable to Resolved
- Assignee changed from SLindoMansilla to mkravec
As discussed with Sergio, setting the ticket to resolved, as we now have an poo#51362 as epic to target AC 1 and 2, since it's part of a bigger discussion.
- Parent task deleted (
#51362)
- Related to action #51767: [functional][u] test fails in rebootmgr - No logs uploaded added
Also available in: Atom
PDF