RFC: test-in-container vs ld.so

[DJ Delorie <dj at redhat dot com>]

The glibc test infrastructure goes to great lengths to run test
programs in the just-built environment, running env and ld.so with
lots of arguments to get things "just right".

The test-in-container infrastructure goes to... well, less great
lengths to provide a "correct native" environment for the test
programs, yet it still runs env and ld.so within the container.

There are a few of our tests that sometimes fail due to kernel address
space randomization when run under ld.so yet work correctly all the
time when run directly.

So... should we run containerized tests without ld.so?

I see two discussion points...

1. Are there tests that *need* the env/ld.so handling within the
container?  (not counting test-specific environment variables, I mean
the environment variables we pass to *every* test)

2. how complicated would it be to remove those from the makefile
rules?  Alternatively, I suppose test-container itself could remove
them, but better not to hide that logic.