Closed xabolcs closed 8 years ago
This is mozdownload and not memchaser, right? I think you want to file this issue on the other repository. :) Btw, the container based infrastructure is easy to do and has a lot of benefits. We already did that for firefox-ui-tests. But yes, this will be a separate issue.
This is mozdownload and not memchaser, right?
The Travis build for MemChaser errored. Of course, something gone wrong with mozdownload.
So at least a mozdownload version bump needed for MemChaser.
Oh! Totally! I see its using version 1.12! Wow... But we have to wait for https://github.com/mozilla/mozdownload/issues/331.
[...] But yes, this will be a separate issue.
Issue #235 was filed.
For the mozdownload update should I stick to 1.18.1
as previously did?
Given that this is for testing with Travis only, I wouldn't mind to be loosely in the version. I would say just depend on mozdownload without any version specified. That would reduce the amount of version bumps in the future.
Thanks!
Taking care of it.
Fixed by commit ab100c59e1061d2a717cb13d632794609b274a54!
Latest CI build didn't failed, but errored.
While I'm was there, Travis CI told me that:
Before debugging any Python here, how about migrating to the new infrastructure (in a separate Issue)?
Cc: @whimboo