Actions
coordination #47003
closed[qe-core][epic][functional][ppc64le] test runs into MAX_JOB_TIME - split extra_tests_in_textmode
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA (private) - Milestone 31
Start date:
2019-09-19
Due date:
% Done:
100%
Estimated time:
(Total: 42.00 h)
Difficulty:
Description
Motivation¶
Recently more and more test modules where added as "extra tests" but they are all more easily controlled by the variable "EXTRATEST" which can take a comma-separated list of test groups. We should parallelize better by not running them all sequentially.
Acceptance criteria¶
- AC1: Each scenario takes significantly less than 2h to complete
- AC2: We do not need MAX_JOB_TIME anymore in the test suite
Suggestions¶
- Simply try out to schedule tests with less groups in
EXTRATEST
. This can even easily be done on production - Make sure all test groups are still covered
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 6 years ago
- Copied from action #47000: [functional][u][ppc64le] test runs into MAX_JOB_TIME added
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 23 to Milestone 25
no capacity in M24, moving to M25
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 25 to Milestone 30+
Updated by SLindoMansilla about 5 years ago
- Priority changed from Normal to High
Updated by SLindoMansilla about 5 years ago
- Subject changed from [functional][u][ppc64le] test runs into MAX_JOB_TIME - split extra_tests_in_textmode to [epic][functional][u][ppc64le] test runs into MAX_JOB_TIME - split extra_tests_in_textmode
Updated by SLindoMansilla about 5 years ago
- Due date set to 2019-10-28
- Start date changed from 2019-09-24 to 2019-10-28
due to changes in a related task
Updated by SLindoMansilla about 5 years ago
- Has duplicate action #54428: [functional][u] long runtime of extra_test_in_textmode (~2h) added
Updated by SLindoMansilla about 5 years ago
- Due date set to 2019-09-19
- Start date changed from 2019-10-28 to 2019-09-19
due to changes in a related task
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 30+ to Milestone 31
Updated by SLindoMansilla over 4 years ago
- Status changed from New to Workable
- Assignee set to SLindoMansilla
Tracking, working on sub-ticket, removing from "tickets to be refined"
Updated by SLindoMansilla over 4 years ago
- Due date set to 2019-09-19
due to changes in a related task: #57290
Updated by zluo over 4 years ago
- Due date set to 2019-09-19
Grund: Änderung an zugehörigem Ticket: #57290
Updated by szarate about 4 years ago
- Tracker changed from action to coordination
- Status changed from Workable to New
Updated by szarate about 4 years ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html
Updated by tjyrinki_suse about 4 years ago
- Subject changed from [epic][functional][u][ppc64le] test runs into MAX_JOB_TIME - split extra_tests_in_textmode to [qe-core][epic][functional][ppc64le] test runs into MAX_JOB_TIME - split extra_tests_in_textmode
Actions