| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This is now split into storage/index remotes, where the former is
expected to be a CASRemote and the latter a BuildStream-specific
remote with the extensions required to store BuildStream artifact
protos.
|
|
|
|
| |
This was almost entirely just historical code duplication.
|
|
|
|
|
|
| |
These tests ensure that we can checkout the build dependencies of
an artifact and that if we try to checkout the runtime dependencies
the command will fail.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
ArtifactElement inherits Element, both have an Artifact
object as a member, thus we should not need to handle these
separately.
This change has resulted in introducing a configure_sandbox()
method in ArtifactElement. The method is similar to
BuildElement.configure_sandbox() but does not configure the
sandbox to actually be used for building.
|
|
|
|
|
|
|
| |
When we open a workspace, we are linking the sources to the directory
specified. As such testing that we are able to open a workspace on a
read-only directory should show that we are able to link files to a RO
directory when we are staging complex sources (eg. Docker source).
|
|
|
|
|
| |
This test was added to consider the edge case when a unreadable file is being
added to CAS.
|
|
|
|
|
| |
This patch adds support for the handling of artifact refs in
bst artifact pull. A test for this has also been added.
|
|
|
|
|
|
|
|
| |
Previously, before loading artifact refs (ArtifactElements) we were
checking that they were cached before loading them. This obviously becomes
a problem when we want to try and pull an artifact. This patch removes
the check for cached artifacts as we should still be able to contruct
an ArtifactElement regardless of whether it is cached or not.
|
|
|
|
|
|
|
|
| |
This patch extends support for bst artifact push so that is now
able to handle artifact refs.
If --deps all is selected and a ref is given, BuildStream will
error.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Some CI jobs still sporadically encounter a thread that wasn't cleaned
up in tests that use the HTTP server, despite calling Queue.close() and
Queue.join_thread().
As a simple SIGTERM signal should suffice to properly terminate the HTTP
server child process, this simply removes the queue and also the extra
thread for serving requests.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
--long or -l will provide the user with extra information about the
contents of the artifacts, including permission mode, file type, size
and name. In order for this to work, the way in which list-contents
works has been modified.
A test and NEWS entry have also been added within this commit
|
|
|
|
|
|
|
| |
Artifact.py consists of multiple tests for the different artifact
subcommands all grouped together. This MR splits the tests relevant to
each subcommand up into separate test files, making it easier to find
the relevant test.
|
| |
|
|
|
|
|
|
|
|
|
| |
This tests that the target which depends on a common dependency
strictly in non strict mode needs to be rebuilt after this common
dependency changes, while it is not the case when depending on the
same common target non strictly.
This is a regression test for #254
|
| |
|
|
|
|
|
|
|
|
| |
In changing the tests to use in_subprocess, they were modified to do
parametrization over both variables instead of looping over one in the
test itself. The purpose of the original code was to reduce the number
of test cases printed in the output. I have hence attempted to remove
superfluous test cases.
|
|
|
|
|
|
|
| |
Additionally, test code that was previous executed by a subfunction (in
the forked process) has been folded into the test function itself, as
separating it is now redundant. This removes some duplicate code for
setting up the context and project, etc.
|
| |
|
|
|
|
|
|
| |
test_invalid_cache_quota was marked as xfail as part of the migration to
buildbox-casd. This reactivates the test but removes the checks for too
large quotas as that aspect is better handled by buildbox-casd.
|
|
|
|
|
| |
This works around a TOCTTOU race condition in bzr's creation of
~/.bazaar in ensure_config_dir_exists() when running tests in parallel.
|
|
|
|
|
| |
Merge `os.environ` and `GIT_ENV` instead of replacing the existing
(tox) environment variables such as HOME and XDG_CONFIG_HOME.
|
|
|
|
|
| |
Merge `os.environ` and `BZR_ENV` instead of replacing the existing
(tox) environment variables such as HOME and XDG_CONFIG_HOME.
|
|
|
|
|
|
|
|
| |
A --out option has been added, allowing an artifact log to be
written to a logfile. This is particularly useful when more
than one artifact's log is wanting to be read; It will write
a file for each log.
A test and NEWS entry have also been added.
|
| |
|
| |
|
|
|
|
|
|
| |
bst artifact show can be used to determine which element names,
artifact refs (also by glob expression) are present within the
artifact cache.
|
| |
|
| |
|
|
|
|
|
| |
This fixes a bug where third party plugins cannot get tested
automatically because they are not part of BuildStream.
|
| |
|
|
|
|
|
|
|
| |
Remove check for order of events as cache cleanup is now handled by
buildbox-casd, not BuildStream scheduler jobs. The test still verifies
that build succeeds when the cache disk usage is larger than the
configured quota.
|
|
|
|
|
|
| |
buildbox-casd checks disk usage against the quota before actually
committing a new blob to the local cache and thus, the disk usage will
never outgrow the quota.
|
|
|
|
|
| |
Parallel fetching leads to sporadic test failures due to scheduling
differences.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Install a signal handler to execute cleanup also on SIGTERM. This will
be used to terminate the buildbox-casd child process.
|