See:

• https://bitbucket.org/ned/coveragepy/issues/530/deprecationwarning-you-passed-a-bytestring
• https://bitbucket.org/ned/coveragepy/commits/f8e9d62f1412

So it looks like this is blocked upstream until there is a 4.3 release of coverage which includes that patch.

I'm not 100% certain, that this is an issue here. I will at least try to confirm it changing coverage version from current to the tip of bitbucket/github repository.

BTW what aproach should we take here, as I'm really trying to make all jobs to be green on Travis? Should we skip that test?

And why this happens only on one job, why not in all 2.6/2.7?

In T152638#2875967, @Magul wrote:

I'm not 100% certain, that this is an issue here. I will at least try to confirm it changing coverage version from current to the tip of bitbucket/github repository.

Definitly the first thing to do =)

BTW what aproach should we take here, as I'm really trying to make all jobs to be green on Travis? Should we skip that test?

From a quick look at the logs I would say this is primarily caused by the "ensure all scripts mention you can use -help" test in script_tests.

Since that has a lot of other asserts all roled into one so @unittest.skipIf( sys.version_info < (3, 0) ) would probably ignore to much.

Could we simply add an if sys.version_info >= (3, 0) before that particular assert (with a comment pointing to this Task (or one specifically about updating)?

In T152638#2875971, @Magul wrote:

And why this happens only on one job, why not in all 2.6/2.7?

I can't figure out what setting makes that one different :/