It is hard to find a specific sanitizer task in less than a second. Fix that by mentioning the sanitizer first in the task name. Less useful information (with or without depends) follows the sanitizer.
Follow up to:
It is hard to find a specific sanitizer task in less than a second. Fix that by mentioning the sanitizer first in the task name. Less useful information (with or without depends) follows the sanitizer.
Follow up to:
I understood 'sanitizers' when I had to. I would not have understood these 'Xsan' abbrevs. NAK.
219 | @@ -220,7 +220,7 @@ task: 220 | FILE_ENV: "./ci/test/00_setup_env_native_tsan.sh" 221 | 222 | task: 223 | - name: '[depends, sanitizers: memory (MSan)] [focal]'
Did you mean to drop depends here?
Yes. It is not possible to compile with MSan, but without depends, so this adds no information.
Yes. It is not possible to compile with MSan, but without depends, so this adds no information.
Sure, however, not everyone has this contextual information. For some it might change the problem from it being hard to find "which one does MSan" to "which one builds depends".
Thanks, restored.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
I would not have understood these 'Xsan' abbrevs.
The goal of the task names is not to be a wikipedia. If you want to explore the details of the ci system further, you can read the scripts in the ./ci/ folder or refer to other resources.
ACK fa459220c7b7a56bcd5426f977cbca17c7af1a5e