This annoyance affects every build `all`.

The function that's getting too big and throwing the compiler message is `__static_initialization_and_destruction_0(int,int)`. This grows with the # of namespace-scope objects, and in these cases that's going to be the objects defined by TEST and TEST_F macros.

I think that if these massive files were simply broken up the problem would go away.

[918/919] CXX build/dynamic_gcc_ninja/mongo/s/transaction_router_test.o
src/mongo/s/transaction_router_test.cpp: In function ‘void __static_initialization_and_destruction_0(int, int)’:
src/mongo/s/transaction_router_test.cpp:4777:1: note: variable tracking size limit exceeded with -fvar-tracking-assignments, retrying without

As part of this ticket we should look to see whether we can make fvar-tracking-assignments trigger a compiler error rather than a warning.