| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This is a regression test for issue #990
|
|
|
|
|
|
|
|
| |
This causes multiple source instances to interact with the same
backing data store at the same time, increasing the likelyhood
of triggering issues around concurrent access.
This more reliably triggers issue #868
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Tests that the target is still built even when a workspace is open
on a runtime dependency of a build-only dependency.
- Tests that the target is still built even when a workspace is open
on a runtime dependency of a runtime dependency of a build-only
dependency
This adds the regression test provided by Matthew Yates for issue #919
This test differs from the one committed in master as:
- We have an orthogonal bug in 1.2.x where buildable elements show up
in a waiting state instead of a buildable state
- Some new APIs were used in the test case added in master, adjusted
to use only 1.2 APIs for the test case.
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
This was broken by 9252a18180ce79d70c193768293baa0f0eff9981.
|
|
|
|
|
| |
When there is less than 2GB left, it cleans up have 10GB available.
These values are configurable.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Adds a test to ensure that BuildStream alerts the user of a skipped push
when the remote already has the artifact cached.
|
|
|
|
|
|
|
|
|
|
| |
The SKIPPED message type is now used to indicate the end of a task which
was successful without having to perform the given task.
This overhauls the use of `Queue.done()` and therefore queues do not
need to provide a processed/skipped return value from `done()`. Instead
this is replaced with the action of raising a `SkipJob` exception from
within `Queue.process()`.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Source must now mention whether the marked or translated
URL is "primary" or not. Even when a Source may have multiple
URLs, the auxilliary URLs are derived from the primary one, not
only is this true for git, but it is mandated by our tracking
API which assumes there is a primary URL.
This adjusts the `git` source and the test `fetch_source.py` source
to behave properly and advertize it's primary URL properly.
This is a part of #620
|
|
|
|
|
|
| |
Failures to write files when tracking were not reported.
Fixes #533.
|
|
|
|
|
| |
This test was skipped because of issue #538, but #538 was fixed
and the test was still not reenabled.
|
| |
|
|
|
|
|
| |
Removed redundant tests from recently merged !740, this new
test does not need to run for every different source kind.
|
|
|
|
| |
This adds a regression test for #461.
|
|
|
|
| |
Fixes #576.
|
|
|
|
|
|
|
|
|
|
|
| |
Ostree mirrors were not sharing the same local repository, so it was
impossible the request refs from the right local repository when data
was fetched from a mirror rather than upstream.
Instead of having several repository with one remote each, we now
have one repository with several remotes.
This fixes #538.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Trying to checkout an element that has no cached artifacts should be and
handled failure. See BuildStream/buildstream#447.
|
|
|
|
|
|
|
| |
Add test to ensure gracefull handling of exception thrown while loading
a pipeline due the python's max recursion depth being exceeded.
This is part of the work for issue #203
|
|
|
|
| |
tests/frontend/workspace.py: Added tests
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Stream._load() now returns early without resolving build pipeline when
only tracking. Resolving track pipelines does not require to fully
load project configurations when when elements to track are only
junctions.
However build pipelines require to fully load project
configurations. This might not be possible in the case a project
configuration includes a file from a junction that yet needs to be
tracked.
Fixes #565.
|
|
|
|
| |
Fixes #331.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
One of the tests added is configured to be skipped for now, as dumping
binary data is causing a bad descriptor exception when using the pytest
capture module.
Closes #263.
|
|
|
|
| |
`bst checkout`"
|
| |
|
|
|
|
| |
The CAS server now supports LRU.
|
| |
|
|
|
|
|
| |
This makes it unnecessary to update the free space in the mock object in
the middle of tests.
|
| |
|
| |
|
|
|
|
| |
The OSTree summary file is no longer used.
|
|
|
|
|
|
|
| |
--track-cross-junctions now concerns crossing junctions rather than
forbidding elements in sub-project to be tracked.
Part of #359.
|
|
|
|
|
|
|
|
|
|
|
| |
Workspaces are now index by colon separated junction path. This
now allows to create workspaces for elements in external projects.
Workspaces are owned by context instead of root project. However
it is initialized once top-level project is registered as we need
to resolve paths relatively to this top-level project.
Part of #359.
|
|
|
|
|
|
| |
'a.bst:b.bst' gets interpreted as 'b.bst' from junction 'a.bst'.
Part of #359.
|
| |
|
|
|
|
|
|
|
|
| |
The tests include a new environment variable: BST_CACHE_QUOTA.
This variable is used in receive_main() in pushreceive.py.
Test names: test_artifact_expires, test_large_artifact_is_not_cached_remotely
test_recently_pulled_artifact_does_not_expire: marked as xfail until
we implement LRU expiry in remote share
|
|
|
|
| |
Fixes #393.
|
|
|
|
|
|
|
|
|
|
|
| |
Previously "elements" was hard-coded as the path for the elements
directory whereas it was supposed to be configurable via the
`element_path` option to `init_project()`. This led to incorrect
behavior when `bst init` was run `--element-path` option.
Also, extend tests to test the creation of elements directory.
Fixes #398.
|
|
|
|
|
|
| |
With the dynamic plan using `_set_required()` we can avoid
pulling/fetching/building unneeded elements even if elements are being
tracked.
|
|
|
|
| |
This is in preparation for moving away from summary files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here the pipeline becomes essentially stateless, some dangling
state remains to be factored out because of frontend accesses
which will be changed in a later commit.
Essentially, the Pipeline.load() method no longer has any knowledge
of the specific purposes of the loaded targets, and now takes
a list of target groups and returns a corresponding list of element
groups.
The Stream() business logic methods now use other pipeline helper
methods to create and filter lists from the loaded target elements.
The Stream() also finally absorbs the Scheduler frontend facing
APIs. However Queues are still exposed on the Stream object for
logging purposes and through callbacks such that the frontend can
retry elements.
|
|
|
|
| |
Use Stream error for Stream errors.
|