| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
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.
|
| |
|
|
|
| |
This removes the --fetch option of bst source checkout, always enabling
fetch support. This is in line with fetching subprojects as needed.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
This will replace the previous use of a directory structure.
Quite a lot is changed here, predominantly _artifact and _artifactcache
modules.
Part of #974
|
| |
|
|
|
|
| |
Tests that sources are cached seperately where appropriate.
Part of #982
|
| |
|
|
|
|
|
|
|
| |
- 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
|
| |
|
|
|
|
|
| |
Workspaced elements should not push their sources as consistency is
marked as cached even if the sources are not necessarily available.
Part of #440
|
| |
|
|
|
|
|
| |
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
|
| |
|
|
| |
Part of #440
|
| |
|
|
|
|
|
| |
Checks buildstream calls fetch method when remote source cache does not
have a source.
Part of #440
|
| |
|
|
| |
Part of #440
|
| |
|
|
|
|
| |
This means that keys are only generated after tracking.
Part of a fix for !1124
|
| |
|
|
|
| |
Pylint can't know that pytest's fixtures are used in a file and
therefore reports false positives. Silencing all those errors
|
| |
|
|
|
| |
Pylint doesn't play well with pytest fixtures, we therefore need to
silence this error.
|
| |
|
|
| |
Fix all pylint unused-variable issues
|
| |
|
|
|
| |
- Remove all wrong-import-order from pylint
- Order some subgroups of imports
|
|
|
Few different source cache tests have been to check that sources are
staged into the local CAS and fetched where appropriate
Part of #440
|