Closed evandrocoan closed 7 months ago
It seems to a dirty fix. I would rather check the source if the error: why coverage was not installed or detected?
After working on it, I finally figured it out why the coverage dependency is missing. On the commit:
You added:
COV_PATH="$STP/coverage"
rm -rf "$COV_PATH"
Now, guess why coverage
is missing? I removed these lines now it is working without the hack I had committed. Usually package control would install missing dependencies, I use it locally, and it works as expected.
coverage
is removed in that line because it would soon be installed by Package Control
I see AppVeyor also do that, but there are no problems over there. Somehow Package Control cannot install the missing dependency on Travis, while it can install on AppVeyour.
If UnitTesting package could capture the whole Sublime Text console, we could know why Package Control is failing in install the missing dependency on Travis. I also think that capturing the whole console would help most users to figure out errors on the remote machine.
Correction, AppVeyor does not delete the coverage dependency.
I managed to implement to capture the whole Sublime Text console on my fork with:
Required libraries (former dependencies) are now resolved automatically via Package Control when running setup
action. The mechanism is identical to how it would work locally.
Here you can see everything passing for the others, including Sublime Text on Mac OS:
I had added
echo "first6 ls"; ls "/home/travis/.config/sublime-text-3/Packages"
on .travis.yml, and we can see thecoverage
dependency there:I manage to fix it by editing
pc_help.py
:Now the tests are passing: