| Age | Commit message (Collapse) | Author |
|---|
|
* [pre-commit.ci] pre-commit autoupdate
* [pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
* manual fixes after configuration update
* [pre-commit.ci] auto fixes from pre-commit.com hooks
for more information, see https://pre-commit.ci
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Anthony Sottile <asottile@umich.edu>
|
|
|
|
|
|
Co-authored-by: Ran Benita <ran@unusedvar.com>
|
|
|
|
|
|
|
|
The release-on-comment script is always executed on *master*, so we should
execute the `release.py` script using tox to ensure we create the
right environment.
Also fixed errors in the error handling code.
|
|
In preparation for enforcing some docstring lints.
|
|
The links were still pointing to the latest version (instead of stable)
and also took the opportunity to update the text a bit.
|
|
|
|
|
|
(#7266)
* enable tox -e docs natively on windows using a wrapper
* rename the towncrier script; run the towncrier command in a safer manner
* use subprocess.call; call exit() around main on towncrier wrapper
* change to sys.exit() instead of builtin exit()
|
|
Somehow I've missed the failures while merging, totally my fault.
|
|
Earlier pytest-bot would only print out the exception in cases of
failure but did not provide context on failing command and error from
command. This patch adds the errors from the command to the exception
message.
`Command` provides abstraction over the command to run and helps
in collecting errors from the first failing command only.
With this, we don't need to check `returncode` from each command that
we run, we can run all the commands and will have access to the error
from the first command that failed. This pattern was taken from Go.
Please refer: https://blog.golang.org/errors-are-values
|
|
Unfortunately this is really getting in the way of the releases not because
of broken links, but because it is very flaky.
Related: #6894
|
|
* Automate release by comment notifications
* Only run if @pytestbot is mentioned
|
|
Not known with `curl` on Travis at least.
Reverts https://github.com/pytest-dev/pytest/pull/6573.
This reverts commit df1f43ee28d38350542a23acb27647feab46f473.
|
|
Follow up to #6621 after premature merge
|
|
|
|
While it might not help with the following, it certainly might happen as
well.
```
+ curl -S -L --connect-timeout 5 --retry 6 -s https://codecov.io/bash -o codecov-upload.sh
curl: (16) Error in the HTTP2 framing layer
```
|
|
This is covered by GitHub Actions now.
|
|
doc: minor fixes for the release process
|
|
|
|
|
|
This would help with debugging missing coverage when removing Travis
jobs.
|
|
|
|
Fix #6369
|
|
|
|
|
|
Now `tox -e docs` will also include the draft changelog for the
next version (locally only).
`CHANGELOG.rst` now only points to the changelog on READTHEDOCS so
sphinx diretives can be used.
Followup to https://github.com/pytest-dev/pytest/pull/6272
|
|
|
|
|
|
This should result in retries of 1+2+4+8+16+32 = 63s.
Ref: https://github.com/pytest-dev/pytest/pull/5869#issuecomment-534235437
|
|
|
|
Recently sometimes Azure has failed with:
++ curl -s https://codecov.io/bash
bash: /dev/fd/63: No such file or directory
This attempts to fix this by modifying report-coverage.sh slightly.
|
|
I was doing final tests on the script today, and forgot to change
the hardecoded "pytest-dev/pytest", which ended up publishing a
`4.99.10` release to the main repository by mistake, as my token
has access to both my fork and main repository.
I deleted the tag immeditely just a few seconds later, so hopefully
this won't cause major problems.
This change makes it safer to test this in the future, never publishing
to the main repository by mistake (as long as the tags are pushed to the
right repositories of course).
|
|
Fix #2933
|
|
|
|
|
|
Fix invalid Python file encoding "utf8"
|
|
This is no longer needed it seems
|
|
|
|
While this is not used currently, it is still good for having it covered
(it failed when running coverage with all jobs unconditionally).
|
|
This appears to be one of the reasons for timeouts on their backend.
|
|
|
|
This should not be necessary (anymore).
|
|
|
|
|
|
|
