| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/
|
|
|
|
|
|
|
| |
Previously, debug messages from `Plugin.__del__()` went to stdout
which was a problem for the test suite in extremely rare and hard to
predict circumstances. This corrects that by sending the message to
stderr where all the rest of the messages tend to go.
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
|
|\
| |
| |
| |
| |
| |
| | |
Add local cache expiry documentation and fix misleading error message when specifying a percentage cache quota
Closes #700
See merge request BuildStream/buildstream!939
|
| |
| |
| |
| |
| | |
Due to the changed Exception message, this patch also changes
the test_parse_size_over_1024T test in misc.py
|
|/
|
|
|
|
| |
local cache
This patch partially resolves #700
|
|\
| |
| |
| |
| | |
Add more to GitLab-relevant parts of contributing
See merge request BuildStream/buildstream!935
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Explain why it's useful to mention the decisions made for a change and
provide links for background, e.g. issue numbers.
My general experience of git histories is that folks don't do enough
explaining, so it's great we have a contributing section for it.
I've found it's easier for folks to stick to rules when they know the
practical reasons for them, so provide some.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I was recently surprised that we don't prefer addressing review comments
in 'fixup!' commits.
Coming from GitHub, I've found that fixup commits make it easier for
reviewers to see what has changed since their last review. The idea is
to use '--autosquash' before landing to clean up the history again.
It's a pleasant surprise that it's easy to keep track of what changed in
merge-requests between pushes, so we can always keep the history clean.
Document this, so folks like me can see the light sooner.
|
|/
|
|
|
|
|
|
| |
As someone coming from GitHub to GitLab, I was pleasantly surprised by
the 'filter by WIP status' option.
To make sure we get the most out of it, add a guideline to keep the
filter clean, to reduce reviewer burden.
|
|\
| |
| |
| |
| |
| |
| | |
Fix bug with root mounted as non-artifact in script plugin.
Closes #756 and #749
See merge request BuildStream/buildstream!941
|
|/
|
|
| |
The issue was introduced by 6ccfab0b1b25990e406446d5cbe5aee83a5e158a.
|
|\
| |
| |
| |
| |
| |
| | |
test behavior when there is no sandbox on Linux
Closes #696 and #736
See merge request BuildStream/buildstream!921
|
| |
| |
| |
| |
| | |
This adds a `reason` to the SandboxEror thrown in sandboxdummy
to be able to understand where the error comes from
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes the `_instance` on the platform object that we use
for caching and not recreating the object everytime at the start
of every test.
This is to ensure our tests share the least amount of state.
The performance penalty is from 5 to 10% accross the whole test suite.
The readings were done 5 times for each before and after the change
and on the same computer.
|
|/
|
|
|
|
|
|
| |
Remove the bwraps checks from _site.py and put them in platform.linux
which is the only place where they are run.
This allows the removal of a double level of caching, making
reasoning about tests easier
|
|\
| |
| |
| |
| |
| |
| | |
Fix infinite recursion in default strip debug command
Closes #645
See merge request BuildStream/buildstream!918
|
|/
|
|
| |
Fixes #645.
|
|\
| |
| |
| |
| |
| |
| | |
Fix cache corruption by scripts when layout and integration commands are used
Closes #749
See merge request BuildStream/buildstream!934
|
|/
|
|
|
|
|
|
| |
Root directory was marked as a non-artifact mount, so not using
SafeHardLink. However integration commands executed with write access
to the root directory.
Fixes #749
|
|\
| |
| |
| |
| |
| |
| | |
Use _force_rmtree instead of custom code.
Closes #735
See merge request BuildStream/buildstream!927
|
|/
|
|
|
| |
There are arguments for and against using onerror - see issue #735
for details.
|
|\
| |
| |
| |
| | |
Update our instructions/examples regarding how we declare remote caches
See merge request BuildStream/buildstream!932
|
| |
| |
| |
| | |
config/project config
|
| |
| |
| |
| | |
caches in project.conf
|
|/
|
|
| |
config
|
|\
| |
| |
| |
| |
| |
| | |
_sandboxremote.py: Use the standard SandboxError
Closes #746
See merge request BuildStream/buildstream!931
|
|/
|
|
|
| |
Replaces the custom one which was erroneously added during development.
Fixes #746.
|
|\
| |
| |
| |
| | |
Fix issue with _pretty_size with large numbers of bytes
See merge request BuildStream/buildstream!799
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Split up artifact cache and CAS cache
Closes #659
See merge request BuildStream/buildstream!922
|
| |
| |
| |
| |
| |
| |
| |
| | |
This changes CASCache from a subclass to a delegate object of
ArtifactCache. As the lower layer, CASCache no longer deals with
elements or projects.
Fixes #659.
|
| |
| |
| |
| |
| |
| |
| | |
The artifact cache backend does not affect build outputs and we anyway
no longer have pluggable artifact cache backends. This hardcodes
CASCache instead of removing the entry completely to avoid cache key
changes.
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
| |
Get the artifact cache from the context instead.
|
|\
| |
| |
| |
| | |
dev-requirements: Update pytest dependency to 3.8
See merge request BuildStream/buildstream!930
|
|/
|
|
|
| |
"_frontend/app.py: Set correct element-path in interactive bst-init"
added a dependency on the tmp_path test fixture, which was added by 3.8.
|
|\
| |
| |
| |
| |
| |
| | |
Use less fetchers in overnight build to work-around limitations from servers.
Closes #742
See merge request BuildStream/buildstream!929
|
|/
|
|
|
|
| |
Issue happens with sourceware.org server.
Fixes #742
|
|\
| |
| |
| |
| | |
element.py: Pass bare_directory also to SandboxRemote()
See merge request BuildStream/buildstream!928
|
|/
|
|
| |
Fixes: 825963b5 ("element: Make "--sysroot" take a bare directory")
|
|\
| |
| |
| |
| | |
plugins/sources/pip.py: Accomodate characters '-','.','_' for packages
See merge request BuildStream/buildstream!914
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
_yaml.py: Implement `get()` for `ChainMap`
See merge request BuildStream/buildstream!919
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Since the core Python `ChainMap.get()` implements with:
self[key] if key in self else default
The double-chain-lookup is expensive. This simple change solves that
for our ChainMap derived structure. As such it improves matters
for #466 somewhat.
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
|
|\
| |
| |
| |
| |
| |
| | |
BREAK: manual.yaml: don't set any default env vars
Closes #718
See merge request BuildStream/buildstream!916
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the 'MAKEFLAGS' and 'V' defaults.
Now that there is a specialised 'make' element, these make-specific
defaults don't make sense here. This element is meant to be a blank
slate for folks to build on.
Note that this is a breaking change, that will require some users to
make changes to their .bst files if they are expecting these environment
variable to be set.
_versions.py: BST_FORMAT_VERSION bumped to 18.
This fixes issue #718
|