Repository navigation
Conversation
It seems reasonable to have an ASan job on Windows, especially to be able to check Windows specific code. Since the tests may take about 70 minutes, it doesn't make sense to add these for pushes, but for a nightly job that should be okay.
|
Very nice! From what I understand, ASAN is more effective in debug builds (whether that also applies to MSVC, I don't know). However, it seems |
|
Argh, completely forgot to commit this after having tested locally: a bit of a hack, but ASan builds should also pass PS: see also https://learn.microsoft.com/en-us/cpp/sanitizers/asan#command-prompt |
|
Cancelled the workflow since it is meaningless anyway for this PR. |
TimWolla
left a comment
There was a problem hiding this comment.
I trust you on the Windows changes, the changes to the GHA workflow LGTM.
|
Let's see how this goes tonight. :) |
|
@cmb69 You probably saw, but there were some failures. 🙂 |
|
@iluuu1994, yes, these have been expected; see #17086. And sapi_windows_set_ctrl_handler.phpt likely blocked. |
|
Oh, but now I saw that the ASan job was also run for other branches than master, where it makes no sense, since Any hints how this can be solved? |
|
@cmb69 It's only a cosmetic issue, but you can add an input about whether windows should run with asan, and pass this value from root.yml depending on the version. Then you can extend the |
It seems reasonable to have an ASan job on Windows, especially to be able to check Windows specific code. Since the tests may take about 70 minutes, it doesn't make sense to add these for pushes, but for a nightly job that should be okay.
I expect some tests to fail yet (see PR #17086).