| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
That was removed anyway, now use utils.sha256sum() to calculate
the expected tar ref.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This little bit of code was being repeated a bunch of times
already throughout buildstream, looks sane enough to offer a utility.
|
| |
|
|
|
|
|
|
|
| |
Currently, if BuildStream is unable to push to the artifact cache for
whatever reason, the build will just error out. Fix it so that if we are
unable to push to the shared cache, we give a warning to the user and
continue building.
Fixes https://gitlab.com/BuildStream/buildstream/issues/90
|
| |
|
|
|
| |
Including changes for newly added bst push & pull
commands and also some changes to the shell command.
|
| |
|
|
| |
So that interactive sandbox mode can be used in a test or automated scenario.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bst shell command is now an optional argument, which
defaults to ['sh', '-i']. This allows one to override
the command including the shell, so one need not invoke
the shell, thus it fixes issue #86.
Instead of an option. This means we can pick up a complete command
line after the '--' token directly from the remaining argument vector,
which makes escaping of things a bit less complicated.
E.g.:
bst shell --scope run <target.bst> -- sh -c "echo Hello World"
Further, the --scope argument is removed in favor of defaulting
to the --scope=run behavior, and adding a --build option
(use `bst shell --build <target>` for build shells, otherwise
juse use `bst shell <target>` for run shells).
Finally, the --builddir has been renamed to --sysroot; which
a bit more accurately describes what it is.
|
| |
|
|
|
|
| |
o The command argument is a list, not a string
o The default value for the command list is ['sh', '-i']
o The sandbox is always run interactively
|
| | |
|
| | |
|
| |
|
|
| |
Fixes #63
|
| |
|
|
|
| |
This composite policy is on the way out the door anyway, first
lets reduce some unused code though.
|
| |
|
|
| |
This saves over 100MB from the resulting image size.
|
| | |
|
| |
|
|
|
|
| |
This report combines the coverage from the integration tests
and the pytest suite together into one report so we can see just
what parts of the code base we're covering collectively.
|
| |
|
|
| |
combined
|
| |
|
|
|
|
|
|
| |
The remove() API is not used anywhere, it was previously used
by ArtifactCache.remove() which itself was unused.
If we need it in the future, it will be right here in
the history.
|
| |
|
|
|
| |
The remove() API is not used anywhere, except for previously
being tested.
|
| |
|
|
|
|
|
|
|
|
| |
Except for the ArtifactCache.remove() test, all of these assertions are
covered by the frontend `push` and `pull` tests. The remove() API itself
is unused except for being tested, lets leave this functionality out
until it's used.
The highlevel tests are easier to write and exercise more of the
codebase to assert the right behaviors, so lets only maintain that.
|
| |
|
|
|
|
|
| |
The coverage reports do not include codepaths reached by
forked processes with multiprocessing unless we configure
this, now we have a more accurate report (and up from 69%
to 73% !)
|
| |
|
|
|
|
|
| |
We require a newer version of OSTree now so the old note
in the install.rst doesnt make sense anymore.
This fixes issue #88
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Use {build_root} itself and not a subdirectory of {build_root} for the
build area used in the source-bundle generated build scripts.
This is consistent with what %{build-root} is expanded to when
generating the build scripts.
Fixes issue #67
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
subdirs
When completing .bst files in subdirectories of an 'element-path',
we need to take the element path into consideration when testing the
results of os.listdir() for os.path.isdir().
This makes directories behave like directories when completing
subdirs of project element paths.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Instead of trying to fire a MessageType.FAIL without an elapsed
parameter, and then not returning from the push()/pull() methods.
|
| | |
|
| | |
|
| |
|
|
| |
We want to see them in failed test logs even if they succeeded.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
It's interesting to keep the local directory push & pull
codepaths alive for the sake of testing everything that
calls into the artifact cache.
For this reason, even when the artifact cache is "offline",
it should be possible to pull and push to it if it is
a local artifact share.
|
| |
|
|
|
| |
So we can create artifact shares and use them easily
in test cases for pushing and pulling artifacts from a share.
|
| |
|
|
|
|
|
| |
If we are executing completions in the context of running
tests, dont use the fast exit path.
Also some docstring fixups for push/pull commands
|
| |
|
|
|
|
|
|
|
|
| |
exiting
Leave that choice to the calling code.
Also some additional cleanup. Removed some bits of code borrowed
from click but unused in this context, just because it's futzing
up the coverage reports.
|
| |
|
|
| |
Turns out we do need this in some corner cases
|
| |
|
|
|
|
| |
Make all the test batteries which run on all the
source backends we have repo scaffoldings for discover
the list of Repo implementations automatically.
|
| | |
|
