| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
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.
|
| |\
| |
| |
| |
| | |
Coverage optional in 1.2.x
See merge request BuildStream/buildstream!1203
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| |
| |
| | |
This disables any attempt to use coverage when running tests
directly against installed dependencies with setup.py.
This fixes #916
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
| |
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.
|
| |\
| |
| |
| |
| | |
Observe fail-on-overlap policy on building element's project
See merge request BuildStream/buildstream!1172
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This test ensures the overlap failure vs warning policy in one
project only ever affects the artifacts created for the project
which declares it and does not force it's policy onto another
consuming project.
A regression test against issue #926
|
| |/
|
|
|
|
|
|
| |
Instead of observing the policy on the element which introduces
overlapping files, which is still the correct element to observe
for whitelists.
This fixes #926
|
| | |
|
| |\
| |
| |
| |
| | |
buildstream/_artifactcache/cascache.py: Set 0644 rights to pulled files
See merge request BuildStream/buildstream!1132
|
| |/
|
|
| |
This was broken by 9252a18180ce79d70c193768293baa0f0eff9981.
|
| |\
| |
| |
| |
| | |
filter.py: don't recurse when staging dependencies
See merge request BuildStream/buildstream!1127
|
| |/
|
|
|
|
|
|
|
| |
Also bump the element's version so cached artifacts would be
invalidated.
Fixes #883
(cherry picked from commit 03111d39e093b11ffc6589071f2f5040d5f61ab4)
|
| |\
| |
| |
| |
| | |
Run tests using tox
See merge request BuildStream/buildstream!1111
|
| | |
| |
| |
| |
| | |
This is relevant bit of change from the MR !1051, to fix the coverage
stats.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
* Omit versioneer's _version.py
* Omit our __main__.py which is used only internally for generating
documentation
(cherry picked from commit 116c1070c893c4b5bd2505ea39157f1b37946092)
|
| | |
| |
| |
| |
| |
| | |
(cherry picked from commit 1fd38fb74c81d39ca7500d9b7f77c67430ed7852)
Backport of !874.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit a backport of a handful of merge requests to master. As
these two branches have diverged a bit and the master branch has seen a
fair bit of churn lately, it was not trivial to simply cherry-pick the
changes.
Some related merge reqtests are: !1027, !1037 and !1051.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`tox.ini` has seen heavy churn lately, and backporting individual
commits is turning out to be a more involved process as the two branches
have diverged a bit. So, this is more or less copy-pasted from the
master branch, without a separate lint job.
Since switching to `pycodestyle` will require some code formatting
changes, that does not seem reasonable to apply to this branch. So,
let's stick with running the linters via `pytest`.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
This commit comes with a Makefile to update the requirements files as
well.
---
!1027 is related MR for the master branch.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Starting from `pytest` version 4.1.0, `Node.get_marker()` has been
removed, and hence our tests break when running with newer versions of
`pytest`. It was deprecated since a while back but it has recently been
removed completely. Use `get_closest_marker()` as a replacement that is
suggested in the changelog, and seems to work fine for our use case.
See https://github.com/pytest-dev/pytest/pull/4564 for more context on
the upstream issue.
One way of verifying this change is that this should fix the recently
added `tests-fedora-update-deps` job, that was failing before due to
this issue.
(cherry picked from commit c91784abcdfebef2e1e70612193b67efe7fa016a)
|
| |\
| |
| |
| |
| | |
[backport 1.2] Force updating tags when fetching git repository
See merge request BuildStream/buildstream!1005
|
| |/
|
|
|
|
|
|
|
| |
When using aliases there are multiple remotes used in the cache
repository. When fetching, tags are not updated if the were previously
fetched from a different remote. Commits that not in a branch and only
tagged do not get fetched if the tag is not fetched.
Fixes #812
|
| |\
| |
| |
| |
| | |
[backport 1.2] Avoid downloading unused git submodules
See merge request BuildStream/buildstream!1001
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently we have configuration in place to disable use of
submodules, with the `checkout-submodules` git plugin option
and the individual `checkout` options for each submodule, but
these unused submodules are still downloaded at fetch time.
This patch fixes the plugin to just completely ignore the
submodules which are configured to be unused.
This was previously fixed in the master branch by !996, and
this patch backports the relevant fix to the 1.2 branch,
fixing issue #804.
|
| |\
| |
| |
| |
| | |
[backport 1.2] Fix cleanup of cache in server when disk is full
See merge request BuildStream/buildstream!979
|
| | |
| |
| |
| | |
Cleaning up in parallel might slow down the cleaning process
|
| | |
| |
| |
| |
| | |
When there is less than 2GB left, it cleans up have 10GB available.
These values are configurable.
|
| | | |
|
| | |
| |
| |
| |
| | |
This also remove references when some objects are missing. This is in
preparation for the move from reference to object garbage collection.
|
| | |
| |
| |
| |
| | |
This locks the temporary object file so that cleanup does not need to
be done for every write.
|
| | |
| |
| |
| |
| |
| |
| | |
The file is already a temporary file and does not need copy. ENOSPC
is thrown during that copy in issue #609.
Fixes #678.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
We plan to make cache incomplete. That is some blobs are missing. For
most of cases we will delete references when requested if they are
incomplete. But there will be corner cases where objects are removed
after the reference is requested.
|
| |/
|
|
|
|
| |
f_bfree space might not be usable. In practice we see failures in big
disks because f_bfree is over 2GB and f_bavail is 0. We get ENOSPC if
writing on disk then.
|
| |\
| |
| |
| |
| | |
[backport] Fix cache corruption by scripts when layout and integration commands are used
See merge request BuildStream/buildstream!940
|
| |/
|
|
|
|
|
|
| |
Root directory was marked as a non-artifact mount, so not using
SafeHardLink. However integration commands executed with write access
to the root directory.
Fixes #749
|
| |\
| |
| |
| |
| | |
Ensure `--deps=none` option works for `bst checkout`
See merge request BuildStream/buildstream!828
|
| |/
|
|
|
|
|
|
|
|
|
| |
This is a backport of !819.
---
Currently, `bst checkout --deps none` command always produces empty
output. Fix this issue and add regression test for the same.
Fixes #670.
|
| |\
| |
| |
| |
| | |
Change URL to the Alpine tarball
See merge request BuildStream/buildstream!881
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
Catch correct exception from shutil.rmtree [bst-1.2]
See merge request BuildStream/buildstream!861
|
