Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Ran Benita <ran@unusedvar.com>
|
|
|
|
ci: fix deprecation message & couple updates
|
|
We want to reserve other tags for our own purposes without it creating a
release.
|
|
|
|
Supposed to be faster.
|
|
|
|
|
|
|
|
We don't have any jobs that should go beyond that, so let's be nicer to
the CI host and quicker to report the failure.
|
|
|
|
|
|
This allows us to remove the `ATTRS_EQ_FIELD` thing which is causing
some annoyance.
|
|
|
|
Co-authored-by: Bruno Oliveira <nicoddemus@gmail.com>
Co-authored-by: Thomas Grainger <tagrain@gmail.com>
Co-authored-by: Kyle Altendorf <sda@fstab.net>
|
|
should be a noop (despite the major version bump) -- I rewrote the action to be more stable and need fewer security updates
|
|
cache the pre-commit environment
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Instead of trying to handle unittest-async functions in pytest_pyfunc_call,
let the unittest framework handle them instead.
This lets us remove the hack in pytest_pyfunc_call, with the upside that
we should support any unittest-async based framework.
Also included 'asynctest' as test dependency for py37-twisted, and renamed
'twisted' to 'unittestextras' to better reflect that we install 'twisted' and
'asynctest' now.
This also fixes the problem of cleanUp functions not being properly called
for async functions.
Fix #7110
Fix #6924
|
|
twisted started to use `attr.s(eq)` argument which was added recently,
so it fails with oldattrs. One of the CI jobs ran twisted and oldattrs
together, so it started to fail.
Move the twisted code to be covered by another job, and remove it from
the job with the oldattrs.
|
|
Issue events don't contain a 'comment' entry:
https://developer.github.com/v3/issues/events/#response-2
Issue comments also contain the original issue body:
https://developer.github.com/v3/activity/events/types/#issuecommentevent
That's why it was triggering even for comments on the issue.
Also changed to startsWith because there's no need to support
the command anywhere in the body IMO.
Fix #6895
|
|
* Automate release by comment notifications
* Only run if @pytestbot is mentioned
|
|
Co-Authored-By: Daniel Hahler <git@thequod.de>
|
|
* Explicitly state on the PR template that we can squash commits
This way we don't need to ask every time, and users who for some reason
would not like us to squash their commits can explicitly state so.
|
|
This often might be causing for jobs to take longer than 10 minutes,
which is a timeout Codecov uses to wait for successful CI.
Also it is good in general to have CI finish faster, of course.
|
|
|
|
|
|
It helps to know upfront that e.g. linting failed, and makes finding the
error easier.
|
|
This would help with debugging missing coverage when removing Travis
jobs.
|
|
Following jobs get aborted on failure.
Ref: https://github.com/pytest-dev/pytest/pull/6530
|
|
|
|
Fix #6369
|
|
|
|
This overwrites the `codecov.yml` file in the root of the repository with
`codecov-upstream.yml` file (which contains the code-cov token)ยด, so PRs
and branches on the repository can upload coverage.
Suggestion from here:
https://github.com/pytest-dev/pytest/pull/6421#issuecomment-571934112
Security concerns: the token might be misused, but only to upload bogus coverage
to `codecov.io`, so the team believe this is harmless. If we decide to fallback
from this decision , we just need to revoke the token.
Related to #6369
|
|
This includes our current full matrix (windows, linux and macos), for evaluting
purposes.
We should disconsider failures when evaluating PRs.
TODO:
- deploy
- coverage
- github release notes
Even with the above missing, I still believe it would be nice to merge
this and have GitHub actions working in parallel so we can evaluate performance
and usability from now on.
|
|
This makes easier for contributors to get the CHANGELOG entry
right the first time.
|
|
|
|
|
|
This creates a separate section from 'features' for small changes which
don't usually require user intervention, such as:
* Human readable session duration
* New junitxml fields
* Improved colors in terminal
* etc.
The idea is to better match user expectations about new actual
features in the "Features" section of the changelog.
|
|
|