Skip to content

[backport 3.5] core: do not rename user threads#12183

Merged
sergepetrenko merged 1 commit intorelease/3.5from
backport/release/3.5/12177
Dec 26, 2025
Merged

[backport 3.5] core: do not rename user threads#12183
sergepetrenko merged 1 commit intorelease/3.5from
backport/release/3.5/12177

Conversation

@TarantoolBot
Copy link
Collaborator

@TarantoolBot TarantoolBot commented Dec 25, 2025

(This PR is a backport of #12177 to release/3.5 to a future 3.5.2 release.)


When a user thread uses Tarantool C API functions, user thread can be renamed because of creation of cord on demand. The commit removes thread renaming for these cords.

There is no portable way to set/get thread name, so let's simply run the test only on Linux.

Closes #12175

When a user thread uses Tarantool C API functions, user thread can be
renamed because of creation of cord on demand. The commit removes thread
renaming for these cords.

There is no portable way to set/get thread name, so let's simply run the
test only on Linux.

Closes #12175

NO_DOC=bugfix

(cherry picked from commit 495740f)
@TarantoolBot TarantoolBot requested a review from a team as a code owner December 25, 2025 15:12
@TarantoolBot TarantoolBot changed the title [Backport release/3.5] core: do not rename user threads [backport 3.5] core: do not rename user threads Dec 25, 2025
@coveralls
Copy link

Coverage Status

coverage: 87.613% (-0.02%) from 87.634%
when pulling 4d54db8 on backport/release/3.5/12177
into 00fe50f
on release/3.5
.

@sergepetrenko sergepetrenko merged commit 56bb4cd into release/3.5 Dec 26, 2025
25 checks passed
@sergepetrenko sergepetrenko deleted the backport/release/3.5/12177 branch December 26, 2025 08:49
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.

4 participants