[GH-ISSUE #2172] Add `run_tests_using_sanitizers.sh` to CI #1104

New issue

Closed

opened 2026-03-04 01:51:24 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:51:24 +03:00

Owner

Originally created by @gaul on GitHub (May 28, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2172

This will help avoid memory and thread safety regressions. We only need to run these on one distro, e.g., Fedora 38.

Originally created by @gaul on GitHub (May 28, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2172 This will help avoid memory and thread safety regressions. We only need to run these on one distro, e.g., Fedora 38.

kerem closed this issue

2026-03-04 01:51:25 +03:00

kerem commented

2026-03-04 01:51:25 +03:00

Author

Owner

@ggtakec commented on GitHub (May 28, 2023):

I posted Draft PR #2173 for this issue.

I considered the code to call run_tests_using_sanitizers.sh but gave up and wrote it directly in ci.yaml.
That is each test in run_tests_using_sanitizers.sh seem best to be a CI Job because all of test several patterns require execution from the build.
And the testing base container is Ubuntu:22.04.

However, some test results are failing, so I think it is necessary to modify the source code. (This is one of the reasons why it is a draft.)

Please check and review it.

@ggtakec commented on GitHub (May 28, 2023): I posted Draft PR #2173 for this issue. I considered the code to call `run_tests_using_sanitizers.sh` but gave up and wrote it directly in `ci.yaml`. That is each test in `run_tests_using_sanitizers.sh` seem best to be a CI Job because all of test several patterns require execution from the build. And the testing base container is Ubuntu:22.04. However, some test results are failing, so I think it is necessary to modify the source code. (This is one of the reasons why it is a draft.) Please check and review it.

kerem commented

2026-03-04 01:51:26 +03:00

Author

Owner

@ggtakec commented on GitHub (May 28, 2023):

Additinal Information about #2173

The valgrind test is taking too long (maybe not finished) and has been aborted by manual.
The sanitaize thread/memory test is failing.

@ggtakec commented on GitHub (May 28, 2023): Additinal Information about #2173 - The `valgrind` test is taking too long (maybe not finished) and has been aborted by manual. - The `sanitaize thread/memory` test is failing.

kerem commented

2026-03-04 01:51:26 +03:00

Author

Owner

@ggtakec commented on GitHub (Jul 16, 2023):

This issue is closed.
ThreadSanitizer tests still detect errors, which are discussed in #2220.

@ggtakec commented on GitHub (Jul 16, 2023): This issue is closed. ThreadSanitizer tests still detect errors, which are discussed in #2220.

kerem referenced this issue

2026-03-04 02:02:18 +03:00

[PR #1104] [MERGED] Eagerly initialize sysconf variables #1817