9 ms·
> Surely the vast majority of testing happens on non-release builds, despite the fact that release builds may also be tested. Of course. > I would say that ha
by joshuamorton 6y ago
> Surely the vast majority of testing happens on non-release builds, despite the fact that release builds may also be tested.
Of course.
> I would say that hardly anyone runs unit tests on release build artifacts just because it takes forever to produce them.
I don't know that this follows: just because 99% of the invocations of your unit test are in fastbuild doesn't mean that you don't also test everything in opt at least once.
- jeffbee 6y agoI can't remember seeing any cc_test target at Google that ran with realistic release optimizations (AutoFDO/SamplePGO+LTO) and even if they did it's still not the release binary because it links in the test case and the test main function.
- joshuamorton 6y agoDid you look in the CI system for configurations there? I see FDO enabled in those tests. (Speaking at a high level, configurations can be modified in bazelrc and with flags without being explicitly listed in the cc_test rule itself) > release binary because it links in the test case and the test main function. Sure, but it's verifiably the same object files as get put into the release artifact.
- deleted 6y ago[deleted]
- tomjakubowski 6y ago> Sure, but it's verifiably the same object files as get put into the release artifact. Well, not if you use LTO.