| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Moving fetch and track to the source command group accidentally dropped
the support for guessing targets for these commands when invoked from a
workspace directory. This brings it back.
|
| |\
| |
| |
| |
| |
| |
| | |
Use collections.abc for Mapping, Iterable
Closes #831
See merge request BuildStream/buildstream!1020
|
| |/
|
|
|
|
|
| |
In _yaml.py and _frontend/complete.py we were getting pylint warnings
for using collections.Mapping and collections.Iterable, which are
abstract classes now provided from collections.abc. This patch just
uses the classes from the right place.
|
| |\
| |
| |
| |
| | |
Run the linter separately from the tests
See merge request BuildStream/buildstream!1033
|
| | |
| |
| |
| |
| |
| |
| | |
pytest plugins
We no longer run the linters through pytest, so we don't need these
plugins anymore.
|
| | |
| |
| |
| |
| | |
Apparently you need to spell Jinja2 with a capital J, otherwise
we find it listed twice in the resulting requirements.txt files.
|
| | | |
|
| | |
| |
| |
| |
| | |
This should save us some cycles in CI, and also allow the
developer to more conveniently lint separately from testing.
|
| | | |
|
| | | |
|
| |/
|
|
| |
configuration
|
| |\
| |
| |
| |
| |
| |
| | |
tests/frontend/buildcheckout.py: Fix bad filename issue for Windows
Closes #842
See merge request BuildStream/buildstream!1032
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In BuildStream/buildstream!1028, we added a test specifically to test
that BuildStream correctly raises an warning when the name of an element
contains characters that are invalid on Windows. Unfortunately, we
didn't see it coming that it would make it impossible to checkout this
branch on Windows.
Fix it by generating this file, only if we are not running on Windows.
* tests/testutils/site.py: Add `IS_WINDOWS` check
* tests/frontend/buildcheckout.py: Generate file with invalid filename
on the fly
* Remove tests/frontend/project/elements/invalid-chars.
Fixes #842.
Note that this may still cause issues on WSL when running tests on a
shared filesystem, but that seems to be a generic issue on WSL with
`os.rename`.
|
| |\
| |
| |
| |
| | |
Use tox as a frontend for running tests
See merge request BuildStream/buildstream!1027
|
| | |
| |
| |
| |
| |
| |
| | |
When we update our dependencies, developers will eventually need to
recreate their `tox` environments to get correct results. This happens
because `tox` isn't particularly good at recognizing changes in the
requirements files.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently the CI and the docs both have to duplicate the same inforation
about how to gather dependencies etc, and have to use hacky ways to run
them.
Add a new `docs` environment to our tox setup so that building docs is
as simple as running `tox -e docs`.
|
| | |
| |
| |
| |
| |
| | |
These new `.in` and `.txt` are making the repository look very
cluttered. Move them to a separate `tools` directory to make it look a
bit cleaner.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since we don't allow use of site packages by default in our `tox`
configuration, people will need to install non-python build dependencies
of some of our dependencies that do not provide pre-built wheels. We
have two such packages at the moment:
* psuitl: requires python C headers, compiler
* pygobject: requires python C headers, pkg-config, compiler, cairo
headers, and gobject libraries
|
| | | |
|
| | |
| |
| |
| |
| | |
Instead of invoking tests throung `setup.py`, use `tox` as a frontend in
the CI pipelines.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Add `tox.ini` file that will enable us to use
[tox](https://tox.readthedocs.io/) as a frontend for running tests.
Since we share the config via `setup.cfg` and requirements via
requirements files, commands like `python3 setup.py test` will continue
to work.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add `.in` and `.txt` requirements files for BuildStream's pure python
dependencies. For each pair, the `.in` file is supposed to capture the
loose version requirements, and the corresponding `.txt` file is
supposed to have frozen requirements. We have 3 such sets:
* `requirements`: BuildStream's runtime dependencies
* `dev-requirements`: Dependencies for running tests
* `plugin-requirements`: Dependencies for core plugins
Note that the frozen requirements files will only be used for testing
purposes, and `setup.py` will continue to read loose requirements.
|
| |\
| |
| |
| |
| | |
Use pycodestyle instead pep8 python module
See merge request BuildStream/buildstream!638
|
| | |
| |
| |
| |
| |
| |
| |
| | |
pep8 package was renamed to pycodestyle to reduce confusion.
Disabled warnings:
W504 - Line break after binary operator (seems people like this)
W605 - Invalid escape sequence (some of our regexes use these)
|
| |/
|
|
|
|
| |
We need to bump the testsuite image versions to use the new
pycodestyle update that allows excluding file paths, so that we can
exclude generated python code.
|
| |\
| |
| |
| |
| | |
doc/Makefile: Update comment about sphinx entrypoint
See merge request BuildStream/buildstream!1026
|
| |/
|
|
|
|
| |
https://github.com/sphinx-doc/sphinx/issues/4375 has been closed as
`wontfix`. Update the comment in doc/Makefile that mentions it, based on
the discussion on the issue.
|
| |\
| |
| |
| |
| | |
Add warnings about invalid characters in filename
See merge request BuildStream/buildstream!1028
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
See https://mail.gnome.org/archives/buildstream-list/2018-December/msg00061.html
for some related discussion.
|
| |/
|
|
|
|
|
| |
Currently we some duplication in the way we check for invalid filenames.
To make it more robust and allow room for adding more warnings, refactor
it into a separate method `_warn_invalid_elements()` that handles just
this.
|
| |\
| |
| |
| |
| | |
Junction test addition
See merge request BuildStream/buildstream!1029
|
| | |
| |
| |
| | |
element is not found
|
| |/
|
|
| |
Better to use the same API everywhere for thecking CLI results.
|
| |\
| |
| |
| |
| | |
Fix netrc crasher
See merge request BuildStream/buildstream!1025
|
| | |
| |
| |
| |
| | |
This happens when the netrc module is searching for a ~/.netrc
file and it doesnt find any HOME set.
|
| | |
| |
| |
| |
| | |
Treat None values in the passed dictionary as keys to be removed
from the environment, this was already happening at restoration time.
|
| |/
|
|
|
|
| |
The python netrc module will raise OSError in the case
that HOME is not set, this was discovered while running
tests under tox.
|
| |\
| |
| |
| |
| |
| |
| | |
Misc fixes to the tests and newer linter errors
Closes #636
See merge request BuildStream/buildstream!1011
|
| | |
| |
| |
| |
| |
| | |
After having fixed the more recent linting errors, the
tests should pass with recent versions of pylint. Tested
with pylint 2.2.2.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Since Thomas Nixon fixed the datafiles plugin to be compatible
with pytest >= 3.8.0, we can now depend on it and avoid the
warnings and errors which the older datafiles plugin causes.
This fixes issue #636
|
| | |
| |
| |
| | |
linter errors
|
| | |
| |
| |
| | |
(duplicate-string-formatting-argument) linter error
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
linter errors
|
