This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch jbilleter/nested-reapi
in repository https://gitbox.apache.org/repos/asf/buildstream.git
omit 06e3efcc3 tests/integration/sandbox.py: Add test for
`remote-apis-socket`
omit 754e2a720 sandbox: Add support for `remote-apis-socket`
omit 9529afa0c Enable local execution in buildbox-casd to support nested
execution
omit ccad294c3 _context.py: Add `effective_build_max_jobs` helper
add 5b9a47388 requirements: Update astroid to 3.3.7 to fix lint on Python
3.13
add 9923ee437 ci: Update images
add 4b62c4eca Merge pull request #2023 from apache/jbilleter/docker-images
add ae3e0cd52 _context.py: Add `effective_build_max_jobs` helper
add 54cfb70ff Enable local execution in buildbox-casd to support nested
execution
add e587aa21b sandbox: Add support for `remote-apis-socket`
add a45279795 tests/integration/sandbox.py: Add test for
`remote-apis-socket`
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (06e3efcc3)
\
N -- N -- N refs/heads/jbilleter/nested-reapi (a45279795)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.github/common.env | 2 +-
.github/compose/ci.docker-compose.yml | 10 +++++-----
.github/run-ci.sh | 2 +-
.github/workflows/ci.yml | 2 +-
requirements/dev-requirements.txt | 2 +-
5 files changed, 9 insertions(+), 9 deletions(-)
