Skip to content

Conversation

gaborbernat
Copy link
Member

👍 Resolves #1024.

@obestwalter
Copy link
Member

Looks good. Something still missing?

@gaborbernat
Copy link
Member Author

Failing Windows tests on Python 2.7 (seems someone somewhere sets a unicode PYTHONPATH environ, and that what breaks the world; trying to identify it) and coverall notifications.

@@ -404,7 +404,7 @@ def mock_venv(monkeypatch):
and cannot install any packages. """

# first ensure we have a clean python path
monkeypatch.delenv("PYTHONPATH", raising=False)
monkeypatch.delenv(str("PYTHONPATH"), raising=False)
Copy link
Member Author

@gaborbernat gaborbernat Sep 28, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nicoddemus @RonnyPfannschmidt @asottile slight bug here inside pytest monkeypatch. The key passed in here is used to re-insert the value at teardown, instead of the key that was there. Because during the get unicode keys degrade to bytes keys this can mean that by invoking this operation we transform bytes key to unicode inside os.environ when the key passed into delenv is unicode.

In such cases, python 2 Windows will refuse to run subprocesses leaving the user to wonder who and where and how it set non bytes value into os.environ. It makes it even harder to discover because the effect is usually discovered later on by another test.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the ping: pytest-dev/pytest#4056

@gaborbernat
Copy link
Member Author

@obestwalter seems merge-ing the coverages by different jobs is not yet supported out of box on non-Travis CI...

@obestwalter
Copy link
Member

oh ... maybe @zooba knows more when this will hit production? Shall we just leave this hanging around for now then?

@gaborbernat
Copy link
Member Author

Hit production? Seems not supported yet, and no plans to add support.

@gaborbernat
Copy link
Member Author

Turns out coveralls does not support merge reports from Azure DevOps. Will need to do somehow a manual merge and upload that.

nicoddemus added a commit to nicoddemus/pytest that referenced this pull request Sep 29, 2018
Fixes the bug described in:

	tox-dev/tox#1025 (comment)

Which is more evident when using `unicode_literals`.
@obestwalter
Copy link
Member

Just because they are not talking about it yet, does not mean it could be supported at some point not too far in the future. But o.k. let's try coveralls, ignore my approval in the other PR then :)

nicoddemus added a commit to nicoddemus/pytest that referenced this pull request Sep 29, 2018
Fixes the bug described in:

	tox-dev/tox#1025 (comment)

Which is more evident when using `unicode_literals`.
nicoddemus added a commit to nicoddemus/pytest that referenced this pull request Sep 29, 2018
Fixes the bug described in:

	tox-dev/tox#1025 (comment)

Which is more evident when using `unicode_literals`.
nicoddemus added a commit to nicoddemus/pytest that referenced this pull request Sep 30, 2018
Fixes the bug described in:

	tox-dev/tox#1025 (comment)

Which is more evident when using `unicode_literals`.
nicoddemus added a commit to nicoddemus/pytest that referenced this pull request Oct 1, 2018
…hon 2

Fixes the bug described in:

	tox-dev/tox#1025 (comment)

Which is more evident when using `unicode_literals`.
@gaborbernat
Copy link
Member Author

Eh, feels like we got hit by:

Yes publishing artifacts from fork builds is currently blocked as we did not have a way to given a sufficiently scoped token to the agent. This is something we are working on fixing but it is going to be a few weeks.

https://github.com/Linuxbrew/brew/issues/746#issuecomment-422955300

@anthrotype
Copy link

Just curious, why the switch from codecov to coveralls?

@anthrotype
Copy link

just saw your comment #1028 (comment)

Seems codecov does not support Azure DevOps

Pity

@gaborbernat
Copy link
Member Author

@anthrotype furthermore codecov turned out to be really flaky for us in the last few months (many unexplainable results) and we got no support when reaching out to them. ``coveralls` also does not implicitly supports it but at least their API is somehow easier to integrate at some level.

@gaborbernat gaborbernat changed the title [wip] azure pipeline restructure and migration from codecov to coveralls azure pipeline restructure and migration to codeclimate Oct 3, 2018
@gaborbernat
Copy link
Member Author

Closing in favour of #1031; I've kept this option only to validate that PR-ing from a fork still works correctly (although no global coverage report). Once Azure Pipelines offers artifact uploads for forks (ETA around 3 weeks), we'll enable coverage generation on all branches. Note in case Azure Pipelines would not deliver this we can migrate to storing the coverage artifacts on Amazon S3 (for a very small cost probably).

@gaborbernat gaborbernat closed this Oct 3, 2018
@gaborbernat gaborbernat mentioned this pull request Oct 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants