MySQL Bugs: #113420: testNdbProcess fails under ASan+UBSan

Bug #113420	testNdbProcess fails under ASan+UBSan
Submitted:	14 Dec 2023 13:02	Modified:	26 Feb 2024 21:40
Reporter:	Laurynas Biveinis (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	8.2.0	OS:	MacOS
Assigned to:		CPU Architecture:	Any
Tags:	sanitizer

Description:
If built with -DWITH_ASAN=ON -DWITH_ASAN_SCOPE=ON -DWITH_UBSAN=ON, testNdbProcess fails with the following output:

ok 1 - pipes connected
Started process: 93726
ok 2 - created process
ok 3 - Parent write pipe
ok 4 - Parent read pipe
not ok 5 - poll readable
Got process 93726, status: 0, ret: 0
ok 6 - test1: response arrives and wait() succeeds
ok 7 - pipes connected
Started process: 93727
ok 8 - created process
ok 9 - Parent write pipe
ok 10 - Parent read pipe
Timeout when waiting for process 93727
Stopped process 93727
ok 11 - proc->stop()
ok 12 - test2: response does not arrive and wait() fails
1..12
# Failed 1 tests!

How to repeat:
See above

Hi Mr. Biveinis,

Thank you for your bug report.

I hope that you agree that this report belongs to the category for the tests for NDB storage engine.

Also, please let us know if this is OS-specific issue. Let us know if this test is successful on some other platform. This is important for the further processing of your report.

The test passes on x86_64 Ubuntu 22.04 for me with the same build options.

Hi,

You are having issues on Intel MAC or on Mx MAC ?

Thanks

M1

Thanks for the report, I verified it on M1

Posted by developer:
 
Hi Laurynas, 

NdbProcess and its test improved significantly from 8.2.0 to 8.3.0, so the current test output does not match the bug report, but I was able to reproduce the issue.

In testNdbProcess-t read_response() uses a 50 msec. timeout waiting for a pipe to become readable. Apparently this is insufficient under ASAN. I was able to make the test pass by increasing the timeout to 250 msec.

Fixed in NDB 8.4.0.

Issues is in testing only, no user-visible changes, so no changelog entry is required.

Thanks!

Closed.