| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
Cache failed builds caused by missing-command
Closes #1101
See merge request BuildStream/buildstream!1543
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
|
| |
| |
| |
| |
| |
| |
| |
| | |
So that, should a sandbox be missing a command such as `sh`, we cache
failures to build, ensure that each sandbox which checks for the command
raises SandboxCommandError instead of SandboxError.
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
|
|/
|
|
|
|
|
|
|
| |
In order to properly support caching failures to build when a sandbox
is missing a command, we need to permit SandboxCommandError to take a
reason parameter. We default that to that which it previously forced
in order to reduce the need to add a reason code to every raise.
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
|
|\
| |
| |
| |
| |
| |
| | |
Don't reset a failed (but cached) workspaced Element
Closes #1096
See merge request BuildStream/buildstream!1536
|
|/
|
|
|
|
|
|
|
|
|
| |
A workspaced element can fail to build, if this happens, we
cache the result as a failure. This patch ensures that we
do not reset the cache data if a workspace has failed to build.
An integration test has also been added which ensures that we
are able to get the log of a failed workspace build.
Closes #1096
|
|\
| |
| |
| |
| |
| |
| | |
Report error when job process unexpectedly dies
Closes #1089
See merge request BuildStream/buildstream!1531
|
|/ |
|
|\
| |
| |
| |
| | |
Move makemaker plugin to bst-plugins-experimental
See merge request BuildStream/buildstream!1538
|
|/
|
|
| |
Continuing moving plugins to bst-plugins-experimental.
|
|\
| |
| |
| |
| | |
Move make plugin to bst-plugins-experimental
See merge request BuildStream/buildstream!1535
|
|/ |
|
|\
| |
| |
| |
| | |
Fix artifact log
See merge request BuildStream/buildstream!1533
|
| |
| |
| |
| |
| |
| |
| |
| | |
This command now fetches the absolute paths of the log files in
the local CAS cache and opens a pager for each path.
The test has also been updated to ensure that a log file is
actually obtained.
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
_frontend/app.py: Fixup node._assert_symbol_name() positional args
Closes #1100
See merge request BuildStream/buildstream!1534
|
|/
|
|
|
| |
bst init was failing due to project_name_proc() incorrectly
passing args to the method, remove erroneous None.
|
|\
| |
| |
| |
| | |
Move meson element to bst-plugins-experimental
See merge request BuildStream/buildstream!1532
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Reject elements which have duplicated dependencies
Closes #1077
See merge request BuildStream/buildstream!1528
|
| |
| |
| |
| | |
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When loading an element, if it has duplicated dependencies of any kind
then we reject the element with a LoadError(DUPLICATE_DEPENDENCY). This
means that an element `foo.bst` can only appear once in any given dependency
kind, allowing it to be both `runtime` and `build`, but not either of those
twice, nor either plus `all`, nor `all` twice.
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
|
|/
|
|
| |
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
|
|\
| |
| |
| |
| | |
Message rework
See merge request BuildStream/buildstream!1500
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adding the element full name and display key into all element related
messages removes the need to look up the plugintable via a plugin
unique_id just to retrieve the same values for logging and widget
frontend display. Relying on plugintable state is also incompatible
if the frontend will be running in a different process, as it will
exist in multiple states.
The element full name is now displayed instead of the unique_id,
such as in the debugging widget. It is also displayed in place of
'name' (i.e including any junction prepend) to be more informative.
|
| |
| |
| |
| |
| |
| | |
Once project & type are resolved, the full_name can be computed
and cached for efficiency. The accessor for getting the private
member should also be moved to the correct section.
|
|/ |
|
|\
| |
| |
| |
| | |
Artifact blob handling
See merge request BuildStream/buildstream!1527
|
| |
| |
| |
| |
| | |
With blob-based expiry in buildbox-casd, the presence of the artifact
proto will no longer be sufficient.
|
| |
| |
| |
| | |
This is in preparation for blob-based expiry as used by buildbox-casd.
|
| | |
|
| |
| |
| |
| |
| | |
If `check_exists` is set, missing directories should raise a
FileNotFoundError.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We need to ensure artifact files are available locally also for elements
that don't run any commands (e.g., compose elements). It's also not
necessary to fetch file blobs after every command. This moves file blob
fetching from SandboxRemote.process_job_output() (part of Sandbox.run())
to a separate fetch_missing_blobs() method, which is invoked by
Element._cache_artifact().
|
|/ |
|
| |
|
|\
| |
| |
| |
| | |
Move cmake plugin to bst-plugins-experimental
See merge request BuildStream/buildstream!1520
|
|/
|
|
|
|
|
|
|
|
|
|
| |
It was agreed on the mailing list to move all plugins to a single
repository, before moving them into domain-specific repositories. As
a result it seems reasonable to move everything to the
bst-plugins-experimental repo as this stepping stone, rather than
creating a whole new repo.
This commit starts the process of moving things over by moving only the
cmake plugin to bst-plugins-experimental, and altering the tests to
reflect the new location.
|
|\
| |
| |
| |
| | |
Enable integration tests for buildbox sandboxing backend
See merge request BuildStream/buildstream!1525
|
| | |
|
| | |
|
| |
| |
| |
| | |
This reverts commit b54c8cb07ca257be79940ffa70853bf75d2c287c.
|
|/
|
|
| |
buildbox-fuse uses bubblewrap for sandboxing.
|
|\
| |
| |
| |
| | |
Revert default junction behaviour and add new junction config options
See merge request BuildStream/buildstream!1403
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This option allows us to completely ignore remotes defined in the
subproject. As a user, we may not wish to interact with subproject
remotes as we may not be able to trust them, for example.
An appropriate test and some documentation has also been added.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The 'cache-junction-elements' configuration option for junction's
is a boolean which enables elements from within the junction to
interact with the parent project's remote(s).
A test has been added to enforce this behaviour and the
BST_FORMAT_VERSION has been bumped.
|