| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
This also involves a number of changes to tests and other parts of the
codebase since they were hacking about wit API that shouldn't have
existed.
|
| |
|
|
|
|
|
| |
As discussed over the mailing list, reformat code using Black. This is a
one-off change to reformat all our codebase. Moving forward, we
shouldn't expect such blanket reformats. Rather, we expect each change
to already comply with the Black formatting style.
|
| |
|
|
| |
tests: remove strict kwargs from xfail marks
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Spotted by Darius.
|
| | |
|
| |
|
|
|
| |
Now that both are equivalent, we can skip the sanitization part before
the yaml call.
|
| |
|
|
|
|
|
|
|
| |
This changes the location of source refs from `cache/cas/refs` to
`cache/sources_protos` and fixes tests that looked in the old reference
place. Source cache now uses the new protocol buffer and grpc methods
defined, for storing locally, and pushing and pulling to remotes.
Part of #1038
|
| |
|
|
|
|
| |
Instead of having methods in Context forward calls on to the Messenger,
have folks call the Messenger directly. Remove the forwarding methods in
Context.
|
| |
|
|
|
|
|
|
| |
Remove the need to pass the Context object to message handlers, by
passing what is usually requested from the context instead.
This paves the way to sharing less information with some child jobs -
they won't need the whole context object, just the messenger.
|
| |
|
|
|
|
| |
Calling '_yaml.dump' will itself call '_yaml.node_sanitize', therefore
we can remove all calls to it in places where we directly after call
dump.
|
| |
|
|
|
|
|
|
| |
When we are testing push failures, we are being too strict
when we try to verify that the remote has failed to be initialized.
The assertion was failing because of slightly different gRPC error
messages. Now the assertion is less strict but still appropriate.
|
| |
|
|
|
|
|
|
|
| |
- Rename plugintestutils to testing.
- Don't run the tests from bst-plugins-template. This imports
buildstream.plugintestutils so will have to be disabled to get
through CI. This can be re nabled once bst-plugins-template has been
patched.
|
| |
|
|
|
|
|
|
| |
This needs to be exposed as part of the plugin author facing API so
that plugin authors can define custom repo types which will can be
passed to the set of tests which iterate over multiple source types.
Part of the work towards #944
|
| |
|
|
|
|
|
| |
Adds a plugin build element that always fails. The test tries to build
an element of this kind.
Part of #440
|
| |
|
|
| |
Part of #440
|
| |
|
|
| |
Part of #440
|
|
|
Part of #440
|