Skip to content

Conversation

@noname0443
Copy link
Collaborator

@noname0443 noname0443 commented Oct 14, 2025

It is annoying to wait for tests which are going to fail :(

@noname0443 noname0443 force-pushed the optimize_test_process_in_case_of_cancellation branch from 9589873 to 75734c5 Compare October 14, 2025 14:46
@noname0443
Copy link
Collaborator Author

For some reason, tasks that are already running cannot be canceled :\
image
Supposedly, we have to specify hard timeouts

jobs:
  test:
    timeout-minutes: 90

@noname0443 noname0443 force-pushed the optimize_test_process_in_case_of_cancellation branch from cec12ec to 6223623 Compare October 16, 2025 07:57
@noname0443
Copy link
Collaborator Author

noname0443 commented Oct 16, 2025

In the previous comment, it might be an error of a representation - the jobs under the hood don't run.
Screenshot_20251016_105906
Let's cancel the tasks and check again their number.

@noname0443
Copy link
Collaborator Author

I see the same result:

Screenshot_20251016_110407

And there are 20 "in progress" tasks:
Screenshot_20251016_110309

At least, "leaked" jobs do not affect us.

@noname0443 noname0443 force-pushed the optimize_test_process_in_case_of_cancellation branch from 7e484fc to 96b570b Compare October 16, 2025 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant