Enable TSAN builds on CI

[mrjerryjohns]

This enables TSAN checking when running the functional tests in CI.

This is currently only enabled on Linux since the various races there were fixed when #7478 landed.

When Darwin races are fixed, tsan can be enabled for those too.

[woody-apple]

Love to see failing (new) tests :)

[bzbarsky-apple]

The filenames for the failure-case artifact uploads probably need to include matrix.type, or we (more plausibly) should only do the uploads for the non-tsan case.

[mspang]

bikeshed: Can we change the name from no_tsan to something else? default? Naming it what it's not isn't a scalable scheme (don't want to end up calling no_tsan_no_asan_no_*).

[mspang]

bikeshed: Can we change the name from no_tsan to something else? default? Naming it what it's not isn't a scalable scheme (don't want to end up calling no_tsan_no_asan_no_*).

Or maybe "debug".

[mrjerryjohns]

debug and with_tsan feel like an odd pairing...(isn't with_tsan debug too?)

Would default and with_tsan be preferable?

[mspang]

debug and with_tsan feel like an odd pairing...(isn't with_tsan debug too?)

Would default and with_tsan be preferable?

The default is optimized for debug & test (optimizations are limited, debug-only assertions enabled, etc) which is why it is usually called "debug". These names are or should be understood in a broader context than just this workflow.

"default" and "tsan" seem OK though

[github-actions]

Size increase report for "nrfconnect-example-build" from 039dfbd

File	Section	File	VM
chip-lock.elf	[LOAD #3 [RW]]	0	-4
chip-lock.elf	device_handles	-12	-12
chip-lock.elf	rodata	-16	-16
chip-lock.elf	text	-20	-20
chip-lock.elf	bss	0	-28

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-lock.elf and ./pull_artifact/chip-lock.elf:

sections,vmsize,filesize
.debug_ranges,0,24
.debug_abbrev,0,23
.debug_loc,0,5
.debug_str,0,-1
[LOAD #3 [RW]],-4,0
device_handles,-12,-12
rodata,-16,-16
.debug_line,0,-20
text,-20,-20
bss,-28,0
.debug_info,0,-71

Comparing ./master_artifact/chip-shell.elf and ./pull_artifact/chip-shell.elf:

sections,vmsize,filesize

[github-actions]

Size increase report for "esp32-example-build" from 039dfbd

File	Section	File	VM
chip-all-clusters-app.elf	.flash.text	-24	-24
chip-all-clusters-app.elf	.flash.rodata	-224	-224
chip-all-clusters-app.elf	.dram0.bss	0	-472

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-pigweed-app.elf and ./pull_artifact/chip-pigweed-app.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-all-clusters-app.elf and ./pull_artifact/chip-all-clusters-app.elf:

sections,vmsize,filesize
[Unmapped],0,224
.debug_ranges,0,24
.debug_abbrev,0,23
.debug_str,0,2
.debug_loc,0,-4
.flash.text,-24,-24
.debug_line,0,-46
.debug_info,0,-67
.flash.rodata,-224,-224
.dram0.bss,-472,0

[github-actions]

Size increase report for "gn_qpg6100-example-build" from 039dfbd

File	Section	File	VM
chip-qpg6100-lighting-example.out	.heap	0	32
chip-qpg6100-lighting-example.out	.bss	0	-32
chip-qpg6100-lighting-example.out	.text	-32	-32

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-qpg6100-lighting-example.out and ./pull_artifact/chip-qpg6100-lighting-example.out:

sections,vmsize,filesize
.heap,32,0
[Unmapped],0,32
.debug_ranges,0,24
.debug_abbrev,0,23
.debug_str,0,-8
.debug_line,0,-20
.bss,-32,0
.text,-32,-32
.debug_info,0,-71

Comparing ./master_artifact/chip-qpg6100-lighting-example.out.map and ./pull_artifact/chip-qpg6100-lighting-example.out.map:

BLOAT EXECUTION FAILED WITH CODE 1:
bloaty: unknown file type for file './pull_artifact/chip-qpg6100-lighting-example.out.map'