dpkg-architecture is printed to stdout

[Thomi Richards]

The Autopilot test 'test_can_access_custom_emulator_properties_twice' calls dpkg-architecture, which prints the following warning:

sh: 1: gcc: not found
dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation)

but then returns the right thing. We ought to hide this output from autopilot stdout, which is where it's currently printed.

[Max Brustkern (nuclearbob)]

At this point I can only see a call to dpkg-architecture in test_introspection_features.py. Is this still a problem?

[Cris Dywan (kalikiana)]

When I confirmed the bug it was based on the message being printed for every single AP test case in the UITK or tests using its test classes. That was addressed in the UITK by doing stderr=subprocess.PIPE which discards those messages.

[Christopher Lee (veebers)]

I don't see this happening any more and the +1 was an issue with a different testsuite.