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
discard 18f1d2dd3 tests/integration/sandbox.py: Add test for
`action-cache-enable-update`
discard 8e77f4d75 sandbox: Add support for action cache updates via
`remote-apis-socket`
add 6c0651a8b tar.py: Fix hardlink extraction with latest Python
add 6d93bd3d4 tests/sources/tar.py: Add test for symlinks
add 3032c1827 Merge pull request #2039 from apache/jbilleter/tar
add 119a36d6b ci: Update images
add 48b2043f3 sandbox: Add support for action cache updates via
`remote-apis-socket`
add ee04a6ceb 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 (18f1d2dd3)
\
N -- N -- N refs/heads/jbilleter/nested-ac-update (ee04a6ceb)
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 +-
src/buildstream/plugins/sources/tar.py | 12 +++---
tests/sources/tar.py | 45 ++++++++++++++++++++++
.../malicious_target.bst => symlinks/target.bst} | 0
4 files changed, 52 insertions(+), 7 deletions(-)
copy tests/sources/tar/{out-of-basedir-hardlinks/malicious_target.bst =>
symlinks/target.bst} (100%)
