TESTS: Try to fix CI

[hoechenberger]

PR Description

pytest-sugar currently doesn't support pytest 5.4, see Teemu/pytest-sugar#187

Pinning pytest to <5.4 for now to hopefully make CIs work again.

Merge checklist

Maintainer, please confirm the following before merging:

• All comments resolved
• This is not your own PR
• All CIs are happy
• PR title starts with [MRG]
• whats_new.rst is updated
• PR description includes phrase "closes <#issue-number>"
• Commit history does not contain any merge commits

[GuillaumeFavelier]

@hoechenberger maybe doc/environment.yml needs to be updated too?

mne-bids/doc/environment.yml

Line 20 in 71520d6

- pytest

#!/bin/bash -eo pipefail
diff <(grep -v '^  - mne_bids~=0.3$' doc/environment.yml) <(cat environment.yml)

19c19
<   - pytest
---
>   - pytest<5.4

Exited with code exit status 1

CircleCI received exit code 1

[sappelhoff]

Thanks @hoechenberger! Travis fails because it wants you to keep environment.yml and doc/environment.yml in sync ... so adding the pytest change there will fix travis (at least that single check)

[hoechenberger]

Thanks @sappelhoff and @GuillaumeFavelier

[agramfort]

we should migrate CIs from appveyor to azure pipelines as it's much faster for windows

any objection?

[hoechenberger]

we should migrate CIs from appveyor to azure pipelines as it's much faster for windows

any objection?

None from my side, but I've never created an Azure pipeline before, so would need a little time to get this to work. Or sb else would have to do it :)

[sappelhoff]

No objection, but perhaps it can be done the next time we have issues with the CIs ... currently it's working so we can just leave it as they are?

[agramfort]

it's working but it slows down feedback on PRs to be done when someone needs to procrastinate

[agramfort]

thx @hoechenberger

[sappelhoff]

@agramfort @hoechenberger .. coming back to the CI discussion and moving Appveyor --> Azure Pipelines.

It might be possible that we can test Linux, MacOS, and Windows all using GitHub Actions (https://github.com/features/actions)

Just to keep in mind.

Maybe @larsoner knows more about this?

[agramfort]

I hear good things about github actions but never played with it

…

[larsoner]

Yes you can probably go either way. I have limited direct experience with GitHub actions. It does seem to have some annoying limitations. My guess is that Azure will be easier because there are many existing repos using it that you could use to build up an appropriate azure-pipelines.yml.

[agramfort]

I would keep circle for the doc. Just get it of appveyor which is too slow

…

[jasmainak]

I would stay away from github actions for now. Not sure how mature it is ...