Skip to content
This repository was archived by the owner on Apr 20, 2023. It is now read-only.

Automatic coverage file collection disabled on Appveyor #138

Closed
mpeterv opened this issue Feb 10, 2018 · 2 comments
Closed

Automatic coverage file collection disabled on Appveyor #138

mpeterv opened this issue Feb 10, 2018 · 2 comments

Comments

@mpeterv
Copy link

mpeterv commented Feb 10, 2018

When Appveyor is detected, coverage files are not collected automatically. This seems to be intentional (d334f5c), however, it would be convenient if automatic collection did work for Appveyor. Additionally, this restriction doesn't seem to be mentioned in README.

@altendky
Copy link

altendky commented Nov 8, 2018

@stevepeak, do you know what happened to codecov/support? I was specifically going to mention codecov/support#402 but it has disappeared. I don't recall there being a specific reason given for this though looking at my email apparently the powershell uploader was suggested. Was there some reason to explicitly disable collection on AppVeyor? Is there now?

Anyways, I ran into this a year and a half ago and worked 'around' (before) it in twisted/twisted#831 where I just pinned to codecov==2.0.5 before that commit linked above. Twisted is still using that.

https://github.com/twisted/twisted/blob/88e0b450f1215ac889cd3feaf4d082527c65d078/tox.ini#L55

crwood pushed a commit to twisted/qt5reactor that referenced this issue Nov 30, 2018
* First pass at tox/pytest/codecov/travis/appveyor

* Add versioneer

* Drop py37 on windows until twisted supports it; use 3.6 for dist

* use py3.6 for dist on travis

* add get_version.py for AppVeyor

* skip 3.5 on AppVeyor due to it being 3.5.3

* update requirements.test.txt

* print python version in codecov tox env

* tidy tox.ini

* require tox 3.1

* try again for 3.6 for dist...

* try again for appveyor

* try again for appveyor... again

* tidy appveyor.yml

* fix actual tests on appveyor

* Add badges to README.rst

* twisted==18.9.0rc1 and py35/37 testing on AppVeyor

* First pass at a circle config

* try to fix circle templates

* again

* Revert "again"

This reverts commit 2eb1ed6.

* just checking

* virtualenv for circle

* $PYTHON -> python3

* correct to .circleci/pyenvinstall.py

* correct to python3

* add missing checkout step for osx

* decode pyenv list

* rework aliases

* fix yaml errors

* fix yaml errors

* fix yaml errors

* try to cache pyenv

* cache brew and pyenv together

* skip existing when pyenv installing

* pyenv update

* tray again for caching

* and maybe cache this time

* Revert "pyenv update"

This reverts commit 88828bf.

* this is weird

* hmmph

* eehhh

* ...

* ,,,

* just explicitly define the pyenv python version

* ---

* ugh

* env vars wrong all this time

* once more

* workaround

* 2.1

* Rework .circleci/config.yml to version 2.1

* names and environment for osx

* take 2

* add dist jobs

* drop useless steps indirection

* $PYENV_PYTHON_VERSION -> << parameters.pyenv_python_version >>

* correct artifact path on circle

* use specified pyenv python version directly for cache key

* Set PATH directly in environment

* separate codecov to it's own step

* correct previous

* Revert "correct previous"

This reverts commit 104902d.

* Revert "Set PATH directly in environment"

This reverts commit b406625.

* Add Circle build status badge

* codecov --verbose

* Revert "codecov --verbose"

This reverts commit 0dddff3.

* Add CIrcleCI variables to passenv

* codecov==2.0.5

codecov/codecov-python#138
twisted/twisted#831
https://twistedmatrix.com/trac/ticket/9196
https://github.com/codecov/support/issues/402

* Revert "codecov==2.0.5"

This reverts commit ba6dcd5.

* WIP

* Test against both PyQt5 and PySide2

* attempt at unique names on circle again with qtness

* take two at circle names

* pick pyqt5 as qtness for dist

* pass through qtness

* hacky fix for dist on circle#

* add missing qtness passthrough for osx

* Update requirements.test.txt

* Update requirements.tox.txt
@thomasrockhu
Copy link
Contributor

I'm going to close this out due to age, but if this is still a need, please open an issue on our community boards

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants