Generally, print should not be used for unit tests, it may pollute
the output stream. Right now, our internal build system is facing
BlockingIOError: [Errno 11] write could not complete without blocking
on prints. Especially ACL tests seem to be a big offender because they
are vary numerous and each may print several times. Many prints in other
tests are cryptic and probably just leftover from debugging.
I only leave the API unit tests where the output is arguably useful.
But I reduce it to one print per call since the input is already known.
Change-Id: Ic5aaf9624f86b39609e2db6157c98cf8e35712fc
88fd22de79