Spam in Travis-CI for some Python versions only

[awwad]

In only some builds on Python 3.4 builds on Travis-CI, you can see long spans of spam like the following in the Travis-CI logs.

Here's one example where the Python 3.4 build) has some bizarre spam, but not the 2.7 and 3.6 builds:

• ...ampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTimestampLargeTime...
• ...Adding a verification key that has already been used. Adding a verification key that has already been used. Adding a verification key that has already been used. Adding a verification key that has already been used. Adding a verification key that has already been used. Adding a verification key that has already been used. Adding a verification key that has already been used. ...
• ...We do not have a console handler. We do not have a console handler. We do not have a console handler. We do not have a console handler. We do not have a console handler....

In another set of builds, the 2.7 is quiet, 3.4 is fairly quiet, and 3.6 is quite noisy with such fascinating output strings as ...badbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbadbad...

One would expect the behavior to be similar.... I can't think of how a few odd Travis-CI instances might explain all this.

[MVrachev]

I don't think I have seen such cases of spam from the time I started contributing to TUF.

This issue is somehow related to #838, but I feel we don't need it anymore.
Have you seen spams like this @joshuagl @lukpueh ?

[jku]

No, not like this. I suggest closing.

From the logs I can make a wild guess and say that running test_log.py somehow broke the logging at the time (as the "console handler" spam is always first) and any tests after that got their default output (warning and above) printed.

[joshuagl]

Thanks both, closing