This is an automated email from the ASF dual-hosted git repository.
hubcio pushed a change to branch storage-compat-test
in repository https://gitbox.apache.org/repos/asf/iggy.git
omit 779a4ee0c Merge branch 'master' into storage-compat-test
omit ddfb9203e test(integration): catch on-disk storage format breaks
pre-merge
add 1dbd9029f test(integration): catch on-disk storage format breaks
pre-merge
add 873b27e47 test(integration): close false greens in the storage compat
check
add 52185f1c1 fix(ci): stop storage-compat.sh from shallowing a full clone
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 (779a4ee0c)
\
N -- N -- N refs/heads/storage-compat-test (52185f1c1)
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/actions/rust/pre-merge/action.yml | 18 +-
.github/config/components.yml | 27 ++-
.../tests/data_integrity/storage_compat.rs | 242 ++++++++++++++++++---
scripts/ci/storage-compat.sh | 76 +++++--
4 files changed, 297 insertions(+), 66 deletions(-)
