This is an automated email from the ASF dual-hosted git repository.
juergbi pushed a change to branch jbilleter/nested-ac-update
in repository https://gitbox.apache.org/repos/asf/buildstream.git
omit ee04a6ceb tests/integration/sandbox.py: Add test for
`action-cache-enable-update`
omit 48b2043f3 sandbox: Add support for action cache updates via
`remote-apis-socket`
add b44bda4ae sandbox: Add support for action cache updates via
`remote-apis-socket`
add 07a2aacf0 tests/integration/sandbox.py: Add test for
`action-cache-enable-update`
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 (ee04a6ceb)
\
N -- N -- N refs/heads/jbilleter/nested-ac-update (07a2aacf0)
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:
src/buildstream/sandbox/_config.py | 11 +----------
1 file changed, 1 insertion(+), 10 deletions(-)
