Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix codecov for testing matrix #354

Closed
wants to merge 15 commits into from
Closed

Fix codecov for testing matrix #354

wants to merge 15 commits into from

Conversation

eurunuela
Copy link
Collaborator

Closes #

Opened this PR to avoid opening PRs to #353

Proposed Changes

Change Type

  • bugfix (+0.0.1)
  • minor (+0.1.0)
  • major (+1.0.0)
  • refactoring (no version update)
  • test (no version update)
  • infrastructure (no version update)
  • documentation (no version update)
  • other

Checklist before review

  • I added everything I wanted to add to this PR.
  • [Code or tests only] I wrote/updated the necessary docstrings.
  • [Code or tests only] I ran and passed tests locally.
  • [Documentation only] I built the docs locally.
  • My contribution is harmonious with the rest of the code: I'm not introducing repetitions.
  • My code respects the adopted style, especially linting conventions.
  • The title of this PR is explanatory on its own, enough to be understood as part of a changelog.
  • I added or indicated the right labels.
  • I added information regarding the timeline of completion for this PR.
  • Please, comment on my PR while it's a draft and give me feedback on the development!

yarikoptic and others added 15 commits November 16, 2020 21:05
…sion

It is really mostly a blind attempt since I have little to no circle experience,
and surprisingly I have failed to find a good python-oriented example upon
a quick search, so just read a bit on matrix specs.  Some notes

- I decided to not bother with non-important here prefixes to the environment
  names etc to harmonize it all.  I guess they could be returned if necessary
  but would require extending the boiler plate
- If it all fails -- it might still be not my fault! since with extensive
  caching of environments I wonder if such as CI setup would stick to stale
  caches (no setup.cfg changes) while dependencies would progress forward
  thus possibly introducing regressions which would go unnoticed.

It is unlikely that this RF "just works", but I am an optimist
According to Azure/azure-functions-python-worker#753 it seems 3.9
should be supported on azure
Co-authored-by: Stefano Moia <[email protected]>
Co-authored-by: Stefano Moia <[email protected]>
@eurunuela eurunuela mentioned this pull request Jan 7, 2021
18 tasks
@smoia smoia closed this in #375 Jan 19, 2021
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.

2 participants