diff options
| author | Chandan Singh <csingh43@bloomberg.net> | 2019-10-22 11:55:09 +0100 |
|---|---|---|
| committer | bst-marge-bot <marge-bot@buildstream.build> | 2019-10-22 11:18:53 +0000 |
| commit | f4503d1552d8012fa1ad4175bee1d917e4e6ff69 (patch) | |
| tree | c2db5d7f6f797df399bdf3ba3d1c12979fc0d3fb /setup.cfg | |
| parent | 735b005f62f3083f46d6cdba837aa0e320856ea3 (diff) | |
| download | buildstream-f4503d1552d8012fa1ad4175bee1d917e4e6ff69.tar.gz | |
setup.cfg: Register mark for pytest-datafileschandan/register-pytest-mark
Register the marker for `pytest-datafiles`. This fixes the following
warning that we currently get:
```
.tox/py37-nocover/lib/python3.7/site-packages/_pytest/mark/structures.py:324
/Users/csingh43/buildstream/bst-tmp/.tox/py37-nocover/lib/python3.7/site-packages/_pytest/mark/structures.py:324: PytestUnknownMarkWarning: Unknown pytest.mark.datafiles - is this a typo? You can register custom marks to avoid this warning - for detail
s, see https://docs.pytest.org/en/latest/mark.html
PytestUnknownMarkWarning,
```
Diffstat (limited to 'setup.cfg')
| -rw-r--r-- | setup.cfg | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -18,6 +18,7 @@ env = D:BST_TEST_SUITE=True markers = + datafiles: data files for tests integration: run test only if --integration option is specified remoteexecution: run test only if --remote-execution option is specified in_subprocess: run test in a Python process forked from the main one |