| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| |
| |
| | |
Fix some warnings happening during the tests
See merge request BuildStream/buildstream!1880
|
| | |
| |
| |
| |
| |
| |
| | |
This ensures we do not leak resources during our tests and that we close
everything nicely.
This removes multiple warnings that is thrown by our code.
|
| |/
|
|
| |
This removes a warning around resources leaks
|
| |\
| |
| |
| |
| |
| |
| | |
tests: Stop using tmpdir_factory.mkdtemp("")
Closes #1290
See merge request BuildStream/buildstream!1879
|
| |/
|
|
|
| |
Using "" as a directory is invalid starting from pytest 5.4.0, let's
use the __file__ name instead
|
| |\
| |
| |
| |
| | |
.gitlab-ci.yml: Update to CentOS 7.7
See merge request BuildStream/buildstream!1876
|
| |/ |
|
| |\
| |
| |
| |
| | |
_exceptions.py: Propagate `temporary` to the base class
See merge request BuildStream/buildstream!1873
|
| |/
|
|
| |
The parameter value should not be ignored.
|
| |\ |
|
| |/ |
|
| |\
| |
| |
| |
| | |
Remove old version annotations
See merge request BuildStream/buildstream!1869
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The guidelines are already correct, however they use 1.x as the reference
for this API.
This commit simply changes the guidelines to indicate 2.x to contributors
as the latest major point release to care about.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This does not make sense to keep in the public API surface
documentation. As we are heading towards a release of 2.0, this
represents a "reset" in public API, and older annotations only
serve to clutter the documentation with information that is not
relevant to the reader.
Everything which is public at the time of the 2.0 release can
be considered available "Since: 2.0" implicitly (as this is
going to be the starting point of this new stable API).
It will make sense to start adding these annotations again for any
added API in 2.2 and forward.
|
| |\
| |
| |
| |
| | |
Documentation build fixes
See merge request BuildStream/buildstream!1871
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The way we were using $(foreach ...) here from GNU Make was causing
errors to be ignored, this should really only be used for collecting
target names and such.
In this commit, we instead:
* Collect the SESSION_FILES using $(wildcard ...)
* Use a "%.run:" Rule to run bst2html.py for each session file
separately, ensuring that we bail out the build if the session
generation fails.
* Having the SESSION_FILES depend on the phony target sessions-prep,
ensures that this rule will be called unconditionally, regardless
of the existance of the .run files.
|
| |/
|
|
|
|
|
| |
This was broken by Chandan's commit b4d472e9c2, when we changed
the pip namespace such that element and source plugins are loaded
from a different group (although he would not have noticed because
the build was not failing for this).
|
| |\
| |
| |
| |
| | |
pip source plugin: Add support for python 3.8
See merge request BuildStream/buildstream!1847
|
| |/
|
|
|
|
|
|
|
|
| |
For some reason, the pip source plugin appears to pass tests in master
when testing python 3.8 without this change, however it does not pass
tests without this change on the bst-1 branch.
Adding this change to master for consistency across branches for now,
and in the off chance that this fixes the pip source plugin in some
python 3.8 environments.
|
| |\
| |
| |
| |
| |
| |
| | |
Fix handling of missing blobs in `ArtifactCache.pull()`
Closes #1276
See merge request BuildStream/buildstream!1843
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
We need to make sure that we read the new proto after a fresh build. And
there is no need to keep the proto around for an incomplete artifact.
This fixes `FileNotFoundError` of CAS blob on push after rebuild.
|
| | |
| |
| |
| | |
This is required when buildbox-casd is running as separate user.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Artifact push and pull operations currently fail if logs are missing.
We don't currently have a config option to control how long artifact
logs should be kept in the cache. Until this changes, we should be
conservative and consider logs to be an essential part of artifacts,
keeping them from getting expired before the rest of the artifact.
|
| | |
| |
| |
| | |
Like `contains_file()` but checks multiple files in a single request.
|
| | |
| |
| |
| |
| | |
This is identical to `test_pull_missing_blob` except that it uses
separate servers for artifact proto index and CAS.
|
| | |
| |
| |
| | |
This fixes handling of missing blobs in `ArtifactCache.pull()`.
|
| | | |
|
| |/
|
|
|
| |
Do not print message "Pulled artifact" when pulling the artifact proto
without data. This matches the log messages in `SourceCache`.
|
| |\
| |
| |
| |
| | |
tests/sources/tar.py: Fix flaky test_out_of_basedir_hardlinks
See merge request BuildStream/buildstream!1870
|
| | |
| |
| |
| |
| | |
Increase sleep duration in test_casd_redirects_stderr_to_file_and_rotate
from 0.05s to 0.5s to reduce risk of test failure.
|
| |/
|
|
|
|
| |
Don't recursively add `contents` to the tar file as the order is not
guaranteed. We need to add `elsewhere` before `to_extract` as the latter
references the former in `linkname`.
|
| |\
| |
| |
| |
| | |
User guide enhancements
See merge request BuildStream/buildstream!1864
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This refreshes the stored sessions and adds the new ones generated
by recent additions to the user guide.
The stored sessions exist to allow contributors to build the
docs without having to build the sessions, which requires an
internet connection and takes longer to build.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
elements
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Renamed the "Advanced topics" section to "Combining projects", and splitting
up the junctions section into two separate documents, one which describes
the simplest junction example and another which explains how to use
workspaces in conjunction with junctions.
This commit also makes some minor changes the examples, correcting
some grammatical errors, improving links and formatting, also rewording
a `note::` in order to clarify that it would be unusual to junction
a project that is in a subdirectory.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Calling this "Developing using BuildStream" is just redundant,
seeing that this is a part of a BuildStream user guide already.
Also, rephrased the introduction text (which appears on a page
which is rarely frequented anyway).
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This section of the user manual describes the basics of creating
your first BuildStream project, while we've discussed this in
terms of a "Getting started" guide while developing it, we ended
up naming this a "Tutorial" because of it's walkthrough nature.
Due to it's name as a Tutorial, developers (our target audience)
have a tendency to avoid it and look for more terse and advanced
material, while this material could be more suitable for getting
started.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Clarification of (@) include documentation
The "important" annotation here was very confusing to read, rewrote
this section to clarify that files included across a junction cannot
be used to inform the declaration of a junction, as this can present
a circular dependency.
Clarification around conditionals and includes
Clarify that conditional statements are always resolved in the context
of the project where the conditional statement was declared.
|
| |/
|
|
| |
Fix an error in documentation build.
|
| |\
| |
| |
| |
| | |
element.py: Fix strong cache key calculation in non-strict mode
See merge request BuildStream/buildstream!1865
|
| | |
| |
| |
| |
| | |
Test that a clean build in non-strict mode produces an artifact matching
the strict cache key.
|
