Project

General

Profile

action #51716

No scheduling error generated for faulty PARALLEL_WITH config

Added by asmorodskyi almost 2 years ago. Updated 11 months ago.

Status:
Workable
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2019-05-21
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Steps to reproduce

  1. Define test suite A with variable PARALLEL_WITH=B
  2. Define test suite B with variable PARALLEL_WITH=B
  3. Add both tests to same job group
  4. Try to call /usr/bin/openqa-client isos post [all required vars DISTRI,VERSION,FLAVOR etc.] TEST=A,B

Observation

Nothing happens.

Expected

An error message that the scheduling failed due to cycle dependencies is generated.

note: In case you will try to call /usr/bin/openqa-client isos post [all required vars DISTRI,VERSION,FLAVOR etc.] (without TEST var; for the whole iso) you will get the expected error, e.g.:

{
    error_messages => [
        "There is a cycle in the dependencies of wicked_aggregate_ref at /usr/share/openqa/script/../lib/OpenQA/Schema/Result/ScheduledProducts.pm line 691.\n",
    ],
    job_id => 1038,
}

Related issues

Related to openQA Project - action #65142: Make scheduling errors more accessibleResolved2020-04-01

History

#1 Updated by asmorodskyi almost 2 years ago

  • Description updated (diff)

#2 Updated by asmorodskyi almost 2 years ago

  • Description updated (diff)

#3 Updated by okurz almost 2 years ago

  • Category set to Concrete Bugs

#4 Updated by okurz about 1 year ago

  • Subject changed from No error on scheduling faulty MM config to Make scheduling errors more accessible. There is no error on scheduling faulty MM config
  • Description updated (diff)
  • Category changed from Concrete Bugs to Feature requests
  • Status changed from New to Workable
  • Target version set to future

Merged in content from #65142

#5 Updated by okurz about 1 year ago

  • Has duplicate action #65142: Make scheduling errors more accessible added

#6 Updated by mkittler 11 months ago

  • Has duplicate deleted (action #65142: Make scheduling errors more accessible)

#7 Updated by mkittler 11 months ago

  • Related to action #65142: Make scheduling errors more accessible added

#8 Updated by mkittler 11 months ago

  • Subject changed from Make scheduling errors more accessible. There is no error on scheduling faulty MM config to No scheduling error generated for faulty PARALLEL_WITH config
  • Description updated (diff)

I moved the information copied over from #65142 out again because these are actually different issues. I keep the #65142 as related issue because both are about scheduling errors.

About the issue itself: I'm wondering whether it makes sense to assume PARALLEL_WITH dependencies can be cyclic at all. I mean, these jobs are supposed to run together at the same time making a "job cluster" in any case: If job A is supposed to run in parallel with job B that means implicitly that job B is supposed to run in parallel with A. I see no problem in specifying that explicitly. (And by the way, if B is additionally supposed to run in parallel with C that also implies A is supposed to run in parallel with C.)

Also available in: Atom PDF