Possible bug in STATUS: RUNNING dependencies

[kinow]

In GitLab by @franra9 on Oct 16, 2024, 15:52

Hello @dbeltrankyl and @kinow,

Autosubmit Version

4.1.10

Expid affected(If applicable)

a1q3

Which task has issues? Where is the log(If applicable)

• Full_name: does not apply

• Log_Path: does not apply

Summary

DN is submitted on SIM submission and not on running despite the jobs.yml does not say so.

Steps to reproduce

Try copying a1q3 but there is some issue before.

What is the current bug behavior?

DN submitted on SIM on submission instead of Running (SIM is on the queue but DN already running)

What is the expected correct behavior?

DN submitted on SIM on running instead.

Relevant logs and/or screenshots(if applicable)

Job a1q3_20200101_fc0_1_SIM is QUEUING
Checking 1 jobs for platform LUMI-LOGIN
Job a1q3_20200101_fc0_1_1_DN is RUNNING

(...)
  DN:
    CHECK: on_submission
    DEPENDENCIES:
      APP_ENERGY_ONSHORE-1:
        SPLITS_FROM:
          '0':
            SPLITS_TO: '%JOBS.DN.SPLITS%'
      DN:
        SPLITS_FROM:
          all:
            SPLITS_TO: previous
      REMOTE_SETUP:
        STATUS: COMPLETED
      SIM:
        STATUS: RUNNING
(...)

Any other relevant information(if applicable)

()

[kinow]

In GitLab by @dbeltrankyl on Oct 16, 2024, 15:54

But it didn't happen until now, no?

Can you try to remove the

REMOTE_SETUP:
        STATUS: COMPLETED # <- this

[kinow]

In GitLab by @franra9 on Oct 18, 2024, 11:49

Hi @dbeltrankyl , you are right this is a misconfiguration in the jobs.yml

I don't know if this did not happen or we just didn't see it.

in any case,

Does it make sense though to have an OR instead of an AND here? I mean, tell me if what I say is not correct, but it seems that in this case AS is proceeding with the downstream execution when not all the conditions described in JOBS are fulfilled. Maybe you can explain to me how this works exactly via slack if you wish.

[kinow]

In GitLab by @franra9 on Oct 18, 2024, 16:29

mentioned in merge request digital-twins/de_340-2/workflow!322

[kinow]

In GitLab by @dbeltrankyl on Oct 23, 2024, 15:08

Hello @franra9

I'll check this today/tomorrow.

The behavior should/will(wip) be the one described in #1316.

When the key '?' (WIP) is not introduced, the dependencies will always be an AND.

Currently, they're always an AND so

AS is proceeding with the downstream execution when not all the conditions described in JOBS are fulfilled. Maybe you can explain to me how this works exactly via slack if you wish.

This shouldn't be the case

[kinow]

In GitLab by @dbeltrankyl on Oct 28, 2024, 09:31

mentioned in commit e787950

[kinow]

In GitLab by @franra9 on Oct 28, 2024, 09:52

🎉 great @dbeltrankyl ! 😄