CI job passed and test script exit 0, but failed by timeout

[yih-redhat]

Container platform

No response

Version

No response

OS version of the container image

No response

Bugzilla, Jira

No response

Description

Please check log at http://artifacts.osci.redhat.com/testing-farm/7df7ef54-3fa5-46fd-8801-b1ce2e37f94b/

I can see the job is already finished and exit with 0, but however it still wait for that process to finish and finally timeout.

• sudo podman system reset --force
  A "/etc/containers/storage.conf" config file exists.
  Remove this file if you did not modify the configuration.
• sudo rm -rf /tmp/tmp.tbHrQIG4kt
• exit 0

Maximum test time '150m' exceeded.
Adjust the test 'duration' attribute if necessary.
https://tmt.readthedocs.io/en/stable/spec/tests.html#duration

A new job that can print out leftover or orphaned process has been created and is running now. yih-redhat/tmt-demo#36

Reproducer

No response

[yih-redhat]

Changed from v1 to main at https://github.com/yih-redhat/tmt-demo/blob/main/.github/workflows/rhel-9-4.yaml#L452

Now this test is run with main branch now yih-redhat/tmt-demo#37

[yih-redhat]

@phracek Hi, do you have time to take a look of this issue this week?

[zmiklank]

Hello @yih-redhat, is this issue related to tfaga v2?

[yih-redhat]

What do you mean "tfaga v2"?
I changed to sclorg/testing-farm-as-github-action@v2, and still have the same issue.

[zmiklank]

I meant version 2 of testing farm as github action. So then yes.
Thanks for creating the issue, we will look into it. Also contributions are welcome.

[zmiklank]

@yih-redhat
I see, that the action is failing as it should be:

Isn't the reason of this behavior in your setup?

[jamacku]

Also:

Maximum test time '150m' exceeded.
Adjust the test 'duration' attribute if necessary.