Storages: Only print errno instead of its string when CPU affinity of SegmentReader bind fail

[JinheLin]

What problem does this PR solve?

Issue Number: close #9389

Problem Summary: printing the strerrno may cause data race under the new CI pipeline

      0x1141614e	StackTrace::StackTrace() [gtests_dbms+289497422]
       0x7e6baa4	fault_signal_handler(int) [gtests_dbms+132561572]
  0x7f054334c400	<unknown symbol> [libc.so.6+222208]
  0x7f054334f2bd	getenv [libc.so.6+234173]
  0x7f0543346e2e	__dcigettext [libc.so.6+200238]
  0x7f05433a2cde	strerror_r [libc.so.6+576734]
       0xdf52693	DB::DM::SegmentReader::setCPUAffinity() [gtests_dbms+234170003]
       0xdf52329	DB::DM::SegmentReader::run() [gtests_dbms+234169129]
       0xdf55de9	decltype(*(static_cast<DB::DM::SegmentReader*>(fp0)).*fp()) std::__1::__invoke<void (DB::DM::SegmentReader::*)(), DB::DM::SegmentReader*, void>(void (DB::DM::SegmentReader::*&&)(), DB::DM::SegmentReader*&&) [gtests_dbms+234184169]
       0xdf55d6e	void std::__1::__thread_execute<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (DB::DM::SegmentReader::*)(), DB::DM::SegmentReader*, 2ul>(std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (DB::DM::SegmentReader::*)(), DB::DM::SegmentReader*>&, std::__1::__tuple_indices<2ul>) [gtests_dbms+234184046]
       0xdf55a82	void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (DB::DM::SegmentReader::*)(), DB::DM::SegmentReader*> >(void*) [gtests_dbms+234183298]
  0x7f0543901ea5	start_thread [libpthread.so.0+32421]
  0x7f0543414b0d	clone [libc.so.6+1043213]

What is changed and how it works?

Only print the errno instead of its string

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

None

[JinheLin]

/debug pull-unit-test

[purelind]

/debug pull-unit-test

The pipeline triggered in the current debug mode will not report the task link. The current triggered pipeline link is: https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftiflash%2Fpull_unit_test/detail/pull_unit_test/11/pipeline

[JaySon-Huang]

/debug pull-unit-test

[JaySon-Huang]

/debug pull-unit-test

[JaySon-Huang]

/debug pull-unit-test

[JaySon-Huang]

comes from #8737 (comment)

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JaySon-Huang, Lloyd-Pottiger

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [JaySon-Huang,Lloyd-Pottiger]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-01-31 07:53:45.486816461 +0000 UTC m=+1552067.051114150: ☑️ agreed by JaySon-Huang.
• 2024-01-31 08:39:44.641388278 +0000 UTC m=+1554826.205685983: ☑️ agreed by Lloyd-Pottiger.

[JaySon-Huang]

/run-all-tests

[JaySon-Huang]

/run-unit-test

[purelind]

/run-unit-test

[Lloyd-Pottiger]

/cherry-pick-release-7.5

[Lloyd-Pottiger]

/cherry-pick release-7.5

[ti-chi-bot]

@Lloyd-Pottiger: new pull request created to branch release-7.5: #9388.

In response to this:

/cherry-pick release-7.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.