search

google / vim-coverage

Apache License 2.0
101 stars 22 forks source link

Travis: test against coveragepy 4.x #31

Open blueyed opened 6 years ago

dbarnett commented 6 years ago

I couldn't tell, was there a reason we needed a particular version range? If so, could you capture that reason in comments somewhere?

blueyed commented 6 years ago

@dbarnett It currently runs against older coveragepy only, i.e. it fails with the current version - as this PR shows.

dbarnett commented 6 years ago

Travis runs are failing saying "No module named coverage". Is there something missing still?

dbarnett commented 3 years ago

Did you end up figuring out the failures any further?

We do have issues like #39 where the problem turned out to be specific to newer versions of coveragepy.

blueyed commented 3 years ago

I do not remember. With https://travis-ci.org/github/google/vim-coverage/jobs/396767645 however it looks like it worked to test with coverage.py 4, which caused an error then - likely what I wanted: testing with an older version to see/show that there are compatibility issues / cover them on CI. Likely related to https://github.com/google/vim-coverage/pull/35.

blueyed commented 3 years ago

Rebased (to fix conflict).

dbarnett commented 3 years ago

I am not sure if putting more time into the Travis config is worth it, given that it likely will run out of OSS credits in the long run anyway...

Oof, I hadn't realized that was a risk.

I'll probably still pick this up and try to get it working at some point regardless. It will still be useful to figure out a working set of commands for testing against different coveragepy versions, whatever CI system we may end up using. Anyway, thanks for getting the ball rolling!