From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Bronnikov <sergeyb@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit 2/2] ci: introduce testing workflow with sanitizers Date: Fri, 21 Jul 2023 08:14:36 +0000 [thread overview] Message-ID: <ZLo+bLNX/fjTspaz@tarantool.org> (raw) In-Reply-To: <67552873-63f9-b5af-bd8b-d8c54dcdfc74@tarantool.org> Sergey, Thanks for the patch! See my replies below, and the second version of the series[1] for updates. On 13.07.23, Sergey Bronnikov wrote: > Thanks for the patch! LGTM with minor comments below > > Sergey > > On 7/13/23 00:09, Igor Munkin wrote: > > This commit adds GitHub workflow running all available LuaJIT tests with > > LUAJIT_USE_ASAN option enabled. For now, sanitizers workflow works only > > for Linux/x86_64 as the most scaling setup in our CI. I believe we will > > be able to add other platforms being supported, when ARM64 and macOS > > beware that ARM64 is absent in a list of supported platforms [1] > > https://clang.llvm.org/docs/AddressSanitizer.html#supported-platforms Thanks for mentioning: removed this from commit message. > > <snipped> > > > + - name: test > > + env: > > + # Enable as much checks as possible. See more info here: > > However, some checks are *disabled*, for example "print_suppressions" > > and "heap_profile" are disabled. Is it intentionally? "print_suppressions" is disabled intentionally, to not spoil the output of the test; "heap_profile" is also disabled in Tarantool, and it is experimental, so I'm afraid introducing flaky failures when enable it. If you can suggest particular flags to be enabled, feel free to share in the second version of the series[1]. > > > + # https://github.com/google/sanitizers/wiki/AddressSanitizerFlags > there are also LeakSanitizer flags here > https://github.com/google/sanitizers/wiki/AddressSanitizerLeakSanitizer#flags > > + ASAN_OPTIONS: " \ > > + detect_invalid_pointer_pairs=1: \ > > + detect_leaks=1: \ > > + detect_stack_use_after_return=1: \ > > + dump_instruction_bytes=1: \ > > + heap_profile=0: \ > > + print_suppressions=0 \ > > + symbolize=1: \ > > + unmap_shadow_on_exit=1: \ > > + " > > + run: cmake --build . --parallel --target LuaJIT-test > > + working-directory: ${{ env.BUILDDIR }} [1]: https://lists.tarantool.org/tarantool-patches/cover.1689925402.git.imun@tarantool.org/T/#t -- Best regards, IM
next prev parent reply other threads:[~2023-07-21 8:27 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-12 21:09 [Tarantool-patches] [PATCH luajit 0/2] Add ASan support in LuaJIT Igor Munkin via Tarantool-patches 2023-07-12 21:09 ` [Tarantool-patches] [PATCH luajit 1/2] build: introduce LUAJIT_USE_ASAN option Igor Munkin via Tarantool-patches 2023-07-13 10:47 ` Sergey Kaplun via Tarantool-patches 2023-07-13 11:52 ` Sergey Bronnikov via Tarantool-patches 2023-07-21 8:13 ` Igor Munkin via Tarantool-patches 2023-07-12 21:09 ` [Tarantool-patches] [PATCH luajit 2/2] ci: introduce testing workflow with sanitizers Igor Munkin via Tarantool-patches 2023-07-13 12:12 ` Sergey Bronnikov via Tarantool-patches 2023-07-21 8:14 ` Igor Munkin via Tarantool-patches [this message] 2023-07-13 16:09 ` Sergey Kaplun via Tarantool-patches 2023-07-21 8:13 ` Igor Munkin via Tarantool-patches
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=ZLo+bLNX/fjTspaz@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=imun@tarantool.org \ --cc=sergeyb@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 2/2] ci: introduce testing workflow with sanitizers' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox