Skip to content

Plugin Action stays locked even when previous generation is finished …#1175

Merged
Vassiliy-Kudryashov merged 2 commits intomainfrom
Vassiliy-Kudryashov/1173-plugin-action-stays-locked-even-when-previous-generation-is-finished
Oct 18, 2022
Merged

Plugin Action stays locked even when previous generation is finished …#1175
Vassiliy-Kudryashov merged 2 commits intomainfrom
Vassiliy-Kudryashov/1173-plugin-action-stays-locked-even-when-previous-generation-is-finished

Conversation

@Vassiliy-Kudryashov
Copy link
Member

#1173

Description

"unlock" calling was put in a wrong place, actually locking process should correspond to "try-finally" concept

Fixes #1173

Type of Change

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual Scenario

See the issue, lock should be removed after tests generation

Checklist (remove irrelevant options):

  • The change followed the style guidelines of the UTBot project
  • Self-review of the code is passed
  • No new warnings

Loading
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.

Plugin Action stays locked even when previous generation is finished

2 participants