| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
See https://gitlab.com/freedesktop-sdk/freedesktop-sdk/merge_requests/1560
|
| |
|
| |
|
|
|
|
| |
Fixes #1046
|
|
|
|
|
|
|
| |
BuildStream now requires setuptools and cython when building the wheel
and thus can't be installed directly with pip install --no-index.
Building a wheel beforehand allows us to install without dependencies.
|
|
|
|
| |
[ci skip]
|
|
|
|
| |
Use bst-plugins-experimental with ostree plugin included
|
|
|
|
|
| |
Since the `buildstream` module now lives inside `src` directory, also
update the paths that we give to `radon`.
|
| |
|
|
|
|
|
|
|
|
|
| |
Now that BuildStream 2 APIs have diverged, we maintain a branch of
freedesktop-sdk which supports BuildStream 2 and uses bst-plugins-experimental
instead of bst-external.
This commit updates our overnight tests to check that we're not breaking
our builds against a ported freedesktop-sdk project.
|
|
|
|
| |
instead bst-external
|
| |
|
|
|
|
| |
https://gitlab.com/BuildStream/buildstream/issues/629
|
|
|
|
| |
https://gitlab.com/BuildStream/buildstream/issues/629
|
|
|
|
|
|
|
| |
WSL tests may be run on non-master branches manually.
WSL tests on master do not have "allow-failure" so we will be notified
if it's failing.
|
|
|
|
|
|
|
|
|
| |
Having the external plugins in the same tox env as the internal tests
is inconvenient for developers. Move the external tests into their own
environment.
In order to run the external tests locally, append `-external` to an
environment name. For example tox -e py35-external.
|
|
|
|
|
|
| |
freedesktop-sdk/bootstrap/project.conf doesn't exist anymore
This completes d61e058273f45bd0a2fda1722d579cdc39fbc99a
|
|
|
|
| |
freedesktop-sdk-18.08.28
|
|
|
|
|
|
|
| |
There appears to be multiple versions of tox in the WSL test
environment, prepending /root/.local/bin to the PATH while
running tests ensures that we are using a recent enough tox
to execute the tests.
|
|
|
|
|
| |
This is generally useful to know, since the tox version is not
enforced by BuildStream.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
coverage.
The test jobs which create coverage reports need to be listed
in the dependencies of the coverage job, as highlighted in
issue #356.
|
|
|
|
| |
Fedora 29 includes python 3.7 so this is not needed anymore
|
| |
|
| |
|
|
|
|
| |
are sorted out
|
|
|
|
|
|
| |
Fedora 27 is EOL since 2018-11-30
See https://fedoraproject.org/wiki/End_of_life
|
| |
|
| |
|
|
|
|
| |
Centos is apparently different enough from fedora when running tests.
|
| |
|
|
|
|
|
|
| |
We already have tests for python 3.5 and 3.6 but not 3.7.
Fixes https://gitlab.com/BuildStream/buildstream/issues/838.
|
|
|
|
|
|
|
| |
This will help us check if BuildStream is working with the latest
version of dependencies, as per our constraints. This job is allowed to
fail but its failure should signal that we need to add stricter
constraints in some of our `.in` requirements files.
|
|
|
|
| |
which include flatpak_repo plugin needed to build fdsdk
|
|
|
|
|
|
|
|
|
|
|
|
| |
During recent reorganizing of `.gitlab-ci.yml` to work with `tox`, seems
like we missed to update the image used by the overnight aarch tests,
meaning that they currently fail due to `tox` being missing from them.
While these tests will be skipped on MRs usually, here is an example of
what the tests look like if they are actually run with this change:
https://gitlab.com/BuildStream/buildstream/-/jobs/145449561.
Fixes #859.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch namespaces the test temp directory and the output
coverage report file with the name of the environment under test,
such that separately run tests do not access the same files.
When running tests without tox, directly through setup.py,
then the tmp directory will still be `./tmp`.
* .gitignore: Added new .coverage-reports/ directory
* .gitlab-ci.yml: Rely on tox to combine and report coverage, only
tell tox about the COVERAGE_PREFIX so that results can be namespaced
by CI job name.
This change also publishes the sources and final combined `.coverage`
file in an output gitlab artifact for inspection, and lists some missing
dependencies to the `coverage` job.
* tox.ini: Add comments and refactor main [testenv] section so that
other environments dont inherit too much unrelated cruft.
Generate the coverate reports in the respective {envtmpdir} so that
all per-process coverage files are prefixed with a full path, ensuring
that concurrent runs don't mix reports and addressing concerns
raised in #844.
Also implemented new `tox -e coverage` environment to combine
any found coverage and print a report.
* .coveragerc: Omit .tox/ directory from coverage stats
Fixes issue #844
|
|
|
|
|
|
|
|
|
|
| |
As we now run tests using `tox`, we don't need to worry about manually
packing and unpacking BuildStream. So, we can remove the preapre stage
entirely.
Update `coverage` and nightly jobs to appropriately cope with this
change. Both these jobs now install all runtime dependencies from
requirements files.
|
|
|
|
|
| |
This seems like a better name for the directory, as it more closely
describes the purpose of its contents.
|
|
|
|
|
| |
This should save us some cycles in CI, and also allow the
developer to more conveniently lint separately from testing.
|
|
|
|
|
|
|
|
|
| |
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`.
|
|
|
|
|
| |
Instead of invoking tests throung `setup.py`, use `tox` as a frontend in
the CI pipelines.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
This removes the need of having it synchronized in multiple places
|
|
|
|
|
| |
This allows us to make sure that tests behave nicely while missing brwap
and ostree.
|
|
|
|
|
| |
This makes all tests use the same template, which makes reasoning
about them simpler
|
|
|
|
|
| |
The unix-logs is always empty, there is therefore no reasons of keeping
it there
|