| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
https://gitlab.com/BuildStream/buildstream/issues/629
|
| |
|
|
| |
https://gitlab.com/BuildStream/buildstream/issues/629
|
| |
|
|
| |
https://gitlab.com/BuildStream/buildstream/issues/629
|
| |
|
|
| |
https://gitlab.com/BuildStream/buildstream/issues/629
|
| |
|
|
|
|
|
|
| |
Unlike the --integration option that activates additional tests marked
with 'integration', this new --remote-execution option deactivates all the
tests except those marked with 'remoteexecution'.
https://gitlab.com/BuildStream/buildstream/issues/629
|
| |\
| |
| |
| |
| | |
Source key fix
See merge request BuildStream/buildstream!1238
|
| | |
| |
| |
| |
| |
| |
| | |
In element we have access to self.__sources directly so we should use
that.
Part of fixes for !1214
|
| | |
| |
| |
| | |
Part of a fix for !1124
|
| |/
|
|
|
|
| |
This means that keys are only generated after tracking.
Part of a fix for !1124
|
| |\
| |
| |
| |
| | |
tests: when comparing lists/dicts, compare all at once
See merge request BuildStream/buildstream!1247
|
| |/
|
|
|
| |
This allows pytest to show a better report of the difference between
the two lists and not just tell that one entry is wrong.
|
| |\
| |
| |
| |
| | |
cleanupjob, cascache: don't write cache size twice
See merge request BuildStream/buildstream!1227
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In CleanupJob, don't write the same size update to the cache size file
twice. The update received in the 'update-cache-size' message has
already been written during ArtifactCache.clean().
This means that we now only do one (write temp file + move into place)
for every artifact that we remove, and from one process at a time. In
later work we might reconsider the number of temp files we create.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
It seems that `CASQuota.calculate_cache_size` had historical significance,
but is now not necessary. Inline it into `CASQuota.compute_cache_size`
to make things simpler. Also remove a redundant compare and assign.
|
| | |
| |
| |
| |
| | |
This comment is unclear and seems to explain something that's better
understood from reading the code alone.
|
| |/
|
|
|
|
|
|
| |
No need to define CACHE_SIZE_FILE in _artifactcache, it is not used here
by the main application, and it is already defined and used in
_cas.cascache.
Fixup the reference in tests to refer to _cas.cascache instead.
|
| |\
| |
| |
| |
| | |
tests: str(datafiles) instead of a longer thing
See merge request BuildStream/buildstream!1245
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Replace some popular copypasta.
This important-looking invocation:
os.path.join(datafiles.dirname, datafiles.basename)
is equivalent to this shorter invocation:
project = str(datafiles)
It seems like it's very popular copypasta, replace it with the shorter
one thus:
# Use 'gsed' or 'sed' etc. as appropriate for your system.
git config --global alias.sub '!f() { git grep --name-only --null "$1" | gxargs --null gsed --in-place --expression "s/$1/$2/g" ; }; f'
git sub 'os.path.join(datafiles.dirname, datafiles.basename)' 'str(datafiles)'
|
| |\
| |
| |
| |
| |
| |
| | |
Refactor _update_state() to be called only when needed
Closes #703
See merge request BuildStream/buildstream!1070
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Tests that the target is still built even when a workspace is open
on a runtime dependency of a build-only dependency.
- Tests that the target is still built even when a workspace is open
on a runtime dependency of a runtime dependency of a build-only
dependency
This adds the regression test provided by Matthew Yates for issue #919
|
| | |
| |
| |
| | |
This is to be consistent will all other queues that follow this setup.
|
| | |
| |
| |
| |
| | |
Since we know when an object's state can change, we don't need
to update the state of all objects for consistency.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Statuses of an element can be changed when:
1) It is pulled
2) It is fetched
3) It is workspaced and it finished building
4) One of its dependencies is tracked
5) One of its dependencies is workspaced and finished building
We can therefore update the statuses at those moments and we don't
need to check all the time.
This reduces considerably the calls to update_states that are done
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
_unique_id is set at instantiation and never modified afterwards.
Since the guildelines for the project is to never modify directly
an object's state, accessing _unique_id as an attribute is safe.
Moreover this will save us some cost of calling functions.
|
| |/
|
|
|
| |
This encapsulates the logic of how we handle ids and the table in the
plugin class itself, making it easier to refactor afterwards
|
| |\
| |
| |
| |
| | |
Added doc's for workspace reset --soft
See merge request BuildStream/buildstream!1246
|
| |/ |
|
| |\
| |
| |
| |
| | |
casserver.py: fix logging-format-interpolation error and enable
See merge request BuildStream/buildstream!1248
|
| |/
|
|
| |
This enables the "logging-format-interpolation" pylint error check
|
| |\
| |
| |
| |
| | |
MANIFEST.in: Remove conftest.py include
See merge request BuildStream/buildstream!1249
|
| |/
|
|
|
|
| |
In !1243, `conftest.py` was moved inside the `tests` directory. Since we
already recursively include everything from there, we can get rid of the
outdated top-level include directive.
|
| |\
| |
| |
| |
| | |
element: keep original 'detail' when re-raising
See merge request BuildStream/buildstream!1240
|
| |/
|
|
|
|
|
| |
Also don't redundantly convert exceptions to strings when format()-ing
them.
In later work there may be other modules that need fixups.
|
| |\
| |
| |
| |
| | |
gitlab-ci: Make WSL tests only run automatically on master
See merge request BuildStream/buildstream!1241
|
| |/
|
|
|
|
|
| |
WSL tests may be run on non-master branches manually.
WSL tests on master do not have "allow-failure" so we will be notified
if it's failing.
|
| |\
| |
| |
| |
| |
| |
| | |
Enable pylint on the tests
Closes #941
See merge request BuildStream/buildstream!1222
|
| | | |
|
| | |
| |
| |
| |
| | |
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.
|
| | | |
|
| | |
| |
| |
| |
| | |
Removes all the ones thare were not needed
Whitelist the ones that are actually needed for side effects
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This fixes a inconsistent-return-statements from pylint and makes it
easier to understand what is happening
|
| | | |
|
