| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| |
| |
| | |
tests/frontend/workspace.py: Remove redundant and pointless tests
See merge request BuildStream/buildstream!1212
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The following tests all test core functionalities for which the
plugin type cannot possibly have any effects on the result, because
none of the tested functionalities in these tests are delegated
to plugins in anyway:
- test_open_track
- test_open_force
- test_open_force_open
- test_open_force_different_workspace
- test_close
- test_inconsitent_pipeline_message
Reduced these tests to only test with the git plugin, instead of
redundantly running these tests against every plugin.
|
| |\
| |
| |
| |
| |
| |
| | |
Improve error reporting when files are not found
Closes #947
See merge request BuildStream/buildstream!1216
|
| | |
| |
| |
| |
| |
| |
| | |
boundaries
These include assertions for the expected provenance in the errors,
protecting against regressions of #947
|
| | |
| |
| |
| |
| | |
These also assert that the provenance of the references to missing
files are reported, guarding for regressions of issue #947
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
appropriate
When a file is missing in a subproject, it is not particularly meaningful
to specify the filesystem path to the elements directory of the subproject,
as this temporary staging directory belongs to BuildStream and not the user.
Instead, when a file is missing in a subproject, specifying the junction name
is more useful.
This fixes an aspect of #947
|
| | |
| |
| |
| | |
This fixes issue #947
|
| |/
|
|
|
|
|
|
|
| |
When printing the provenance, show the fully qualified element name
including the junction prefix in the case that the provenance comes
from a subproject.
This makes much more sensible error reporting when reporting errors
which originate from a subproject.
|
| |\
| |
| |
| |
| | |
Cleanup: Move _yaml.node_get_project_path() to Project._get_path_from_node()
See merge request BuildStream/buildstream!1211
|
| |/
|
|
|
|
| |
_yaml.node_get_project_path() is currently only used by Project
and by Plugin. This function has been moved to Project._get_path_from_node()
and no longers requires a project directory as argument.
|
| |
|
|
|
|
| |
freedesktop-sdk/bootstrap/project.conf doesn't exist anymore
This completes d61e058273f45bd0a2fda1722d579cdc39fbc99a
|
| |\
| |
| |
| |
| |
| |
| | |
.gitlab-ci.yml: Use current stable version of freedeskop-sdk: freedesktop-sdk-18.08.28
Closes #954
See merge request BuildStream/buildstream!1219
|
| |/
|
|
| |
freedesktop-sdk-18.08.28
|
| |\
| |
| |
| |
| |
| |
| | |
Improve remote execution
Closes #935
See merge request BuildStream/buildstream!1192
|
| | |
| |
| |
| | |
Part of #797.
|
| | |
| |
| |
| |
| | |
The sandbox directory should be updated even for commands with non-zero
exit code. This allows caching the failed buildtree for debugging.
|
| | |
| |
| |
| |
| |
| | |
process_job_output() currently expects the whole directory tree as
output. Match this in the request by asking for the whole directory
tree.
|
| | |
| |
| |
| | |
Remote execution should always use CasBasedDirectory.
|
| |/
|
|
| |
This allows bypassing the local filesystem.
|
| |\
| |
| |
| |
| |
| |
| | |
Make it easy to test BuildStream against external plugins
Closes #922
See merge request BuildStream/buildstream!1158
|
| |/ |
|
| |\
| |
| |
| |
| | |
Expose _GitMirror as part of plugin author facing API
See merge request BuildStream/buildstream!1022
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We want it to be possible for plugin authors writing git type plugins
derrived from _GitSourceBase to be able to make use of custom
_GitMirror classes.
Add a MirrorClass class variable to _GitSourceBase which can be
overriden by derriving classes. This allows plugin authors to specify
the use of custom/derrived _GitMirror class.
|
| |/
|
|
|
|
|
|
| |
In !1019, we opened up the `_GitSourceBase()` class but forgot to expose
the `GitMirror()` class that does most of the heavy lifting around
handling the Git repository.
So, add it to `__init__.py` as well, but not as a public API.
|
| |\
| |
| |
| |
| | |
test: Pass proxy and cert env variable to tox environment
See merge request BuildStream/buildstream!1207
|
| |/
|
|
|
|
| |
In order to be able to run integration tests behind a proxy, we need
to let proxy related environment variable cascade to the tox
environment.
|
| |\
| |
| |
| |
| | |
cleanup: Move YAML handling logic in _include.py to _yaml.py
See merge request BuildStream/buildstream!1205
|
| |/ |
|
| |\
| |
| |
| |
| | |
Improve import performance
See merge request BuildStream/buildstream!1190
|
| | |
| |
| |
| | |
Filter elements do not run any commands. This will allow faster staging.
|
| | |
| |
| |
| | |
The filter plugin doesn't use Sandbox.get_directory().
|
| | |
| |
| |
| | |
Import elements do not run any commands. This will allow faster staging.
|
| | |
| |
| |
| | |
This will allow faster staging.
|
| | |
| |
| |
| |
| |
| | |
This flag indicates whether the plugin may run commands using
`Sandbox.run()` and defaults to `True`. This will allow faster staging
for plugins that do not need to run any commands in the sandbox.
|
| | |
| |
| |
| |
| | |
This enables use of CasBasedDirectory for faster staging when command
execution is not required.
|
| | |
| |
| |
| |
| | |
Allow Sandbox implementations to decide whether to use
CasBasedDirectory.
|
| | | |
|
| | |
| |
| |
| |
| | |
We already have relative_pathname in the caller. Reuse that instead of
calling os.path.join().
|
| | |
| |
| |
| |
| | |
This provides an API in line with, e.g., os.path.join(), and eliminates
isinstance checks.
|
| |/
|
|
|
|
| |
If the destination directory does not exist yet and there is no filter,
we can import the whole source directory by digest instead of importing
each directory entry individually.
|
| |\
| |
| |
| |
| | |
Fixes for coverage optionality
See merge request BuildStream/buildstream!1206
|
| | |
| |
| |
| |
| |
| |
| | |
This scaffolding needs to manually tell coverage to cleanup
when sigterm happens in the process in order to collect
the coverage report, but we need to do this conditionally
in case we are running tests without coverage support.
|
| |/
|
|
| |
Chandan, you silly pony.
|
| |\
| |
| |
| |
| | |
requirements/Makefile: Always rebuild requirements files
See merge request BuildStream/buildstream!1204
|
| |/
|
|
|
|
|
| |
We always want to update all the requirements files together such that
the versions of the common dependencies do not drift between them. Do so
by adding a dummy phony target `FORCE` and depend on it from all the
`.txt` targets.
|
| |\
| |
| |
| |
| |
| |
| | |
Make coverage optional
Closes #916
See merge request BuildStream/buildstream!1189
|
| | |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change simply makes it possible to run the tests without
coverage and without any coverage related dependencies present
in the tox venvs.
To run tests without coverage, simply choose the python version
and append "-nocover" to the env name, e.g.:
tox -e py36-nocover
|
