| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
When non-readable files were being added to CAS, `add_object` was
failing. Thus all sourced files must be readable if they are to be cached.
The tar source has been modified to ensure this precondition.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the case we are copying something to a read-only directory,
`_copy_directories` fails. Copying should work regardless.
Now when we are copying something to a read-only directory, we
reset the permissions of the directory to writable, and then revert to
the directory's original permissions after copying is completed.
An example where this is nessesary is when extracting Docker layers.
If one layer adds a read-only directory `/a` and the following layers adds
`/a/foo`, we must be able to copy `foo` into the otherwise read-only directory,
whilst still ensuring `/a` is read-only once the layer is staged.
|
|\
| |
| |
| |
| | |
Update artifact push and pull so that they can handle artifact refs
See merge request BuildStream/buildstream!1568
|
| |
| |
| |
| |
| | |
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.
|
|\
| |
| |
| |
| | |
Display cache usage in status bar
See merge request BuildStream/buildstream!1564
|
| |
| |
| |
| |
| | |
This was removed with the switch to buildbox-casd. Readd it now that
cache usage tracking is supported again.
|
| |
| |
| |
| |
| | |
This spawns a subprocess to periodically retrieve current cache usage
information from buildbox-casd via gRPC.
|
| | |
|
| | |
|
|/
|
|
|
| |
The updated version of buildbox-casd includes support for disk usage
monitoring.
|
|\
| |
| |
| |
| | |
Improve long-running task reporting
See merge request BuildStream/buildstream!1573
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Resolving the initial cached state of Elements could
potentially take a while, especially for large projects
or local caches which are on a latent filesystem. We should
report progress.
|
| | |
|
|/
|
|
|
|
|
| |
Prior to this patch, subtask information was always displayed,
regardless of how long it took. Now, I've implemented a
_DISPLAY_LIMIT of 3 seconds. If a task takes longer than 3 seconds,
the subtask information will be printed.
|
|\
| |
| |
| |
| |
| |
| | |
Fix typo in node attribute
Closes #1118
See merge request BuildStream/buildstream!1582
|
|/
|
|
| |
closes #1118
|
|\
| |
| |
| |
| | |
node.pyx: _SYNTHETIC_FILE_INDEX must not be module-private
See merge request BuildStream/buildstream!1576
|
| | |
|
| |
| |
| |
| |
| | |
This will be used by the test suite to improve isolation between tests
running in the same process.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's declared in node.pxd and used by _yaml.pyx.
This fixes the following error when running individual tests:
src/buildstream/testing/runcli.py:563: in run_project_config
base_config = _yaml.load_data(config)
src/buildstream/_yaml.pyx:293: in buildstream._yaml.load_data
cpdef MappingNode load_data(str data, int file_index=node._SYNTHETIC_FILE_INDEX, str file_name=None, bint copy_tree=False):
src/buildstream/_yaml.pyx:324: in buildstream._yaml.load_data
node._set_root_node_for_file(file_index, contents)
> f_info = <__FileInfo> __FILE_LIST[file_index]
E IndexError: list index out of range
src/buildstream/node.pyx:1550: IndexError
Fixes: 97b8ab7d ("node: Mark module-private functions and classes...")
|
|\
| |
| |
| |
| | |
utils.py: Wait for threads to exit in _is_single_threaded()
See merge request BuildStream/buildstream!1583
|
|/
|
|
| |
gRPC threads are not joined when shut down.
|
|\
| |
| |
| |
| | |
tests/testutils/http_server.py: Drop queue to avoid lingering thread
See merge request BuildStream/buildstream!1581
|
|/
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| | |
README.rst: Point badge to bst-1 branch
See merge request BuildStream/buildstream!1580
|
|/ |
|
|\
| |
| |
| |
| | |
Replace safeguard for fork with multiple threads
See merge request BuildStream/buildstream!1577
|
| | |
|
| |
| |
| |
| |
| | |
This reduces the difference between regular execution and the test
environment.
|
| |
| |
| |
| | |
The fork safeguard is now handled by Context.is_fork_allowed().
|
| |
| |
| |
| | |
The fork safeguard is now handled by Context.is_fork_allowed().
|
| | |
|
| |
| |
| |
| | |
The fork safeguard is now handled by Context.is_fork_allowed().
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This will be used to safeguard against fork issues with multiple
threads.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Also support use as context manager.
|