Stages - teardown job is triggered even if all other jobs are not finished

[kumada626]

What happened:
Stage teardown job is triggered soon after one of a last job in the stage is finished even if there is a running job in that stage.
In the following pipeline, stage@sandbox:teardown job is triggered after sandbox-e2e-test finishes while sandbox-test is still running.

What you expected to happen:
Teardown job should be triggered after all other jobs in the stage are finished.

How to reproduce it:

1. provide a pipeline that has following screwdriver.yaml.

shared:
  image: node:20
  steps:
    - test: echo 'test'
 
stages:
  sandbox:
    requires: [ ~commit ]
    description: Deploy sandbox and test
    jobs: [ sandbox-deploy, sandbox-e2e-test, sandbox-test ]
    teardown:
      steps:
        - init: echo 'sandbox teardown'
 
jobs:
  sandbox-deploy:
    description: empty
  sandbox-e2e-test:
    requires: [ sandbox-deploy ]
  sandbox-test:
    requires: [ sandbox-deploy ]
    steps:
      - sleep: sleep 60

2. start this pipeline.
3. stage@sandbox:teardown job is triggered before sandbox-test job is finished.

[kumada626]

@VonnyJap I check this behavior on current OSS-SD(API v7.0.188) and still occurs this bug. Like below screenshot, stage@sandbox:teardown job is triggered after stage@sandbox:sandbox-e2e-test is finished even if stage@sandbox:sandbox-test still running.

If stage@sandbox:sandbox-e2e-test is failed, stage@sandbox:teardown correctly triggered after stage@sandbox:sandbox-test is finished. So I think this issue is caused when a job triggering teardown job is success.

[VonnyJap]

@tkyi - Could you help investigate why the teardown is being triggered even though not all upstream jobs have completed?