| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
profile_start() and profile_end() calls have been added to
Stream.load_selection()
|
| |
|
|
|
| |
profile_start() and profile_end() calls have been incorporated into
Scheduler.run()
|
| |\
| |
| |
| |
| | |
.gitlab-ci.yml: Add overnight tests logs to artifacts.
See merge request BuildStream/buildstream!1084
|
| |/ |
|
| |\
| |
| |
| |
| | |
Make the profiler output binaries (which can be used to visualise the data)
See merge request BuildStream/buildstream!1082
|
| | |
| |
| |
| |
| |
| | |
Private class methods which write the logs and write the binaries
have been added to Profile. The binaries are able to be used
by various visualisation tools.
|
| |/ |
|
| |\
| |
| |
| |
| | |
sandbox/sandbox.py: Display failed commands in the detail string
See merge request BuildStream/buildstream!1081
|
| |/
|
|
|
|
|
|
|
|
|
| |
We should only display commands in detail strings, not in the
message texts.
This also updates tests/integration/sandbox-bwrap.py to expect
the new message string which only contains the command exit status
and not the whole command itself, this does not alter the validity
of the text case which is checking that we can obtain the expected
return value.
|
| |\
| |
| |
| |
| | |
General refactor in tests directory
See merge request BuildStream/buildstream!1062
|
| | |
| |
| |
| | |
This is the directory for all things related to loading.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
The remaining test simply loads a project with one element
and asserts a value on it. This is already sufficiently tested
in tests/format/project.py.
|
| | |
| |
| |
| | |
Remove some redundancy from the test lines.
|
| | |
| |
| |
| |
| |
| | |
This is where other load time related plugin error handling is
checked, and is the last thing to remove in the `tests/pipeline`
directory.
|
| | |
| |
| |
| |
| |
| |
| | |
The tests/format/project.py test already has some tests about how
we error gracefully for bad plugins and bad plugin configurations,
lets put it there rather than tests/pipeline/load.py which we
will remove.
|
| | |
| |
| |
| |
| |
| | |
Created new `tests/format/iteration.py` which tests the order in
which elements are iterated over in various scopes in a loaded
data model.
|
| | |
| |
| |
| | |
This used to be an internal test, converted this to use the `cli` fixture.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Now that the remaining test "filter.py" in the plugins directory
tests a specific element, it makes sense to create a place for
testing elements, just like we do for sources.
|
| | |
| |
| |
| |
| |
| | |
This tests exactly the same thing that is tested in
tests/internals/pluginfactory.py (the new location
of tests/plugins/basics.py).
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Grouping bits of internal testing together here
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
The tests/pipeline directory will be removed, and this test
is the better of the two but also redundant with the one in
tests/frontend/show.
Renamed existing test in show.py to `test_show_except_simple`
and added the better test as `test_show_except` below it.
|
| |/ |
|
| |\
| |
| |
| |
| | |
element.py: Cleanup temporary staging directories on termination
See merge request BuildStream/buildstream!1080
|
| |/
|
|
|
|
|
|
|
|
|
| |
Use utils._tempdir() which in turn uses _signals.terminator() for
this purpose.
This also changes utils._tempdir() to use utils._force_rmtree()
so that it is safe to use for cleaning up the staging directory.
This patch fixes orphaned temporary directories being left behind
in the artifact cache directory at forceful termination time.
|
| |\
| |
| |
| |
| |
| |
| | |
Scheduler refactor, fix processing order
Closes #712
See merge request BuildStream/buildstream!1067
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It was saying "There is not enough space to build the given element.",
this makes me think the error is associated to a specific element, but
this does not make sense to show up in a cleanup task.
Instead say "There is not enough space to complete the build.", which
should be more clear that even after cleaning up there is not enough
space.
|
| | |
| |
| |
| |
| |
| | |
With the scheduler changes, fetch jobs get automatically skipped
so the output is changed, using a separate repo for each element
fixes the test such that every fetch job gets a job launched.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This branch makes the following changes:
* jobs/job.py: No longer stores any interested resource list
Jobs are ephemeral again, they only ever exist while they
are running.
* queues/queue.py: Revert to only handling lists of elements
Elements pass through the queues, Queue.harvest_jobs()
replaces Queue.pop_ready_jobs() and now the Queue stops
creating jobs as soon as there are not enough resources
for the job.
Also removed unused `prepare()` abstract method.
* queues/buildqueue.py: Adapt the part where we launch a job
This part needs to be reworked anyway, just touch it up for
now so that it doesnt break with the surrounding changes.
* jobs/{cachesize,cleanup}job.py: Expose uniform complete callback
Allows the scheduler to manage resource deallocation for these
two job completions as a custom thing, at the same phase
that the Queues take care of their own resource deallocation.
* resources.py: No longer has knowledge of the job
Since jobs are ephemeral, they are not a suitable place
to store the resource identifiers, these must be provided
by the callers wherever needed.
Now the main Resources object is owned by the Scheduler
but shared with Queues, each take care of managing the
resources of the jobs they create through the same
resource API.
* scheduler.py: Reverted to only creating jobs on demand
This changes the flow of the scheduler such that whenever
jobs complete, the queues are interrogated for as many
jobs which can run at the moment but not more; and this
completely removes the waiting list.
For the internal cache management jobs, we handle this
with a little state instead of having a waiting list
and only launch when the resources permit it.
By abolishing the scheduler waiting list and creating jobs
on demand, we fix the order of element processing and consequently
fix issue #712.
|
| |\
| |
| |
| |
| |
| |
| | |
Ensure that we can execute `bst-artifact-server`
Closes #867
See merge request BuildStream/buildstream!1079
|
| |/
|
|
|
|
|
| |
Since the CAS refactor, we have not been able to execute
bst-artifact-server. This commit ensures that we can.
This fix closes #867
|
| |\
| |
| |
| |
| | |
Make integration tests parallelizable
See merge request BuildStream/buildstream!1077
|
| | |
| |
| |
| |
| |
| |
| |
| | |
To ensure we can run integration tests in parallel, use a tempdir
for the artifact cache of each separate integration test run.
This makes it possible to run multiple full test runs including
integration tests in parallel under detox.
|
| |/
|
|
| |
This was just deadcode, it's not really used here.
|
| |\
| |
| |
| |
| | |
bst-docker-import: fix Chandan's name
See merge request BuildStream/buildstream!1076
|
| |/ |
|
| |\
| |
| |
| |
| | |
Cas refactor
See merge request BuildStream/buildstream!1071
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
List of methods moved
* Initialization check: made it a class method that is run in a subprocess, for
when checking in the main buildstream process.
* fetch_blobs
* send_blobs
* verify_digest_on_remote
* push_method
Part of #802
|
| | |
| |
| |
| | |
Part of #802
|
| |/
|
|
|
|
|
|
|
| |
Other components will start to reply on cas modules, and not the artifact cache
modules so it should be organized to reflect this.
All relevant imports have been changed.
Part #802
|
| |\
| |
| |
| |
| | |
Small documentation/comment fixes in context.py
See merge request BuildStream/buildstream!1072
|
| | | |
|
| |/ |
|
