This is an automated email from the ASF dual-hosted git repository.
jiayu pushed a change to branch update/duckdb-150-benchmark-defaults
in repository https://gitbox.apache.org/repos/asf/sedona-spatialbench.git
discard a51f242 Show OOM-killed engines in summary report
discard fe56a02 Default SedonaDB to stable, show OOM queries in summary
discard c2d4488 Run both SF1 and SF10 by default, add crash resilience
discard cae1c51 Add crash resilience: pre-populate results and handle SIGTERM
discard c154ecd Default DuckDB to stable release, revert non-fatal spatial
install
discard 48c8c19 Make DuckDB spatial extension install step non-fatal
discard 6315b93 Restore INSTALL spatial for DuckDB nightly compatibility
discard 245c625 Remove unnecessary INSTALL spatial for DuckDB 1.5+
discard 2da7250 Update DuckDB to 1.5.0+, default to SF10 with 300s timeout,
and add crash resilience
add 888a607 Improve benchmark defaults, crash resilience, and OOM handling
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 (a51f242)
\
N -- N -- N refs/heads/update/duckdb-150-benchmark-defaults
(888a607)
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/workflows/benchmark.yml | 6 ++++++
1 file changed, 6 insertions(+)
