|
| 1 | +--- |
| 2 | +name: Bug Report |
| 3 | +about: Is something wrong with Pytest Celery? |
| 4 | +title: '' |
| 5 | +labels: 'bug' |
| 6 | +assignees: '' |
| 7 | + |
| 8 | +--- |
| 9 | + |
| 10 | +<!-- |
| 11 | +Please fill this template entirely and do not erase parts of it. |
| 12 | +We reserve the right to close without a response |
| 13 | +bug reports which are incomplete. |
| 14 | +--> |
| 15 | +# Checklist |
| 16 | +<!-- |
| 17 | +To check an item on the list replace [ ] with [x]. |
| 18 | +--> |
| 19 | +- [ ] I have verified that the issue exists against the `main` branch of Pytest Celery. |
| 20 | +- [ ] This has already been asked to the [discussions forum](https://github.com/celery/pytest-celery/discussions) first. |
| 21 | +- [ ] I have checked the [issues list](https://github.com/celery/pytest-celery/issues?q=is%3Aissue+label%3A%22bug%22+-label%3A%22documentation%22) |
| 22 | + for similar or identical bug reports. |
| 23 | +- [ ] I have checked the [pull requests list](https://github.com/celery/pytest-celery/pulls?q=is%3Apr+label%3A%22bug%22+-label%3A%22documentation%22) |
| 24 | + for existing proposed fixes. |
| 25 | +- [ ] I have checked the [commit log](https://github.com/celery/pytest-celery/commits/main) |
| 26 | + to find out if the bug was already fixed in the main branch. |
| 27 | +- [ ] I have included all related issues and possible duplicate issues |
| 28 | + in this issue (If there are none, check this box anyway). |
| 29 | + |
| 30 | +## Mandatory Debugging Information |
| 31 | + |
| 32 | +- [ ] I have verified that the issue exists against the `main` branch of Celery. |
| 33 | +- [ ] I have included the contents of ``pip freeze`` in the issue. |
| 34 | +- [ ] I have included all the versions of all the external dependencies required |
| 35 | + to reproduce this bug. |
| 36 | + |
| 37 | +## Related Issues and Possible Duplicates |
| 38 | +<!-- |
| 39 | +Please make sure to search and mention any related issues |
| 40 | +or possible duplicates to this issue as requested by the checklist above. |
| 41 | +
|
| 42 | +This may or may not include issues in other repositories that the Celery project |
| 43 | +maintains or other repositories that are dependencies of Celery. |
| 44 | +
|
| 45 | +If you don't know how to mention issues, please refer to Github's documentation |
| 46 | +on the subject: https://help.github.com/en/articles/autolinked-references-and-urls#issues-and-pull-requests |
| 47 | +--> |
| 48 | + |
| 49 | +#### Related Issues |
| 50 | + |
| 51 | +- None |
| 52 | + |
| 53 | +#### Possible Duplicates |
| 54 | + |
| 55 | +- None |
| 56 | + |
| 57 | +## Environment & Settings |
| 58 | + |
| 59 | +# Steps to Reproduce |
| 60 | + |
| 61 | +## Required Dependencies |
| 62 | +<!-- Please fill the required dependencies to reproduce this issue --> |
| 63 | +None |
| 64 | + |
| 65 | +## Minimally Reproducible Test Case |
| 66 | +<!-- |
| 67 | +Please provide a reproducible test case. |
| 68 | +
|
| 69 | +We prefer submitting test cases in the form of a PR to our integration test suite. |
| 70 | +If you can provide one, please mention the PR number below. |
| 71 | +If not, please attach the most minimal code example required to reproduce the issue below. |
| 72 | +If the test case is too large, please include a link to a gist or a repository below. |
| 73 | +--> |
| 74 | + |
| 75 | +<details> |
| 76 | +<p> |
| 77 | + |
| 78 | +```python |
| 79 | +``` |
| 80 | + |
| 81 | +</p> |
| 82 | +</details> |
| 83 | + |
| 84 | +# Expected Behavior |
| 85 | +<!-- Describe in detail what you expect to happen --> |
| 86 | + |
| 87 | +# Actual Behavior |
| 88 | +<!-- |
| 89 | +Describe in detail what actually happened. |
| 90 | +Please include a backtrace and surround it with triple backticks (```). |
| 91 | +--> |
0 commit comments