Skip to content

Actions: duckdblabs/db-benchmark

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
138 workflow runs
138 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Run benchmark
Run benchmark #52: Manually run by Tmonster
March 7, 2025 09:29 52m 58s main
March 7, 2025 09:29 52m 58s
Run benchmark
Run benchmark #51: Manually run by Tmonster
March 7, 2025 07:36 33s main
March 7, 2025 07:36 33s
Run benchmark
Run benchmark #50: Manually run by Tmonster
March 7, 2025 07:21 40s main
March 7, 2025 07:21 40s
Run benchmark
Run benchmark #49: Manually run by Tmonster
March 7, 2025 07:17 1m 28s main
March 7, 2025 07:17 1m 28s
Run benchmark
Run benchmark #48: Manually run by Tmonster
March 7, 2025 07:02 44s main
March 7, 2025 07:02 44s
Run benchmark
Run benchmark #47: Manually run by Tmonster
March 7, 2025 06:59 1s main
March 7, 2025 06:59 1s
Run benchmark
Run benchmark #46: Manually run by Tmonster
March 7, 2025 06:45 Startup failure main
March 7, 2025 06:45 Startup failure
Add trigger to run the benchmark
Regression #192: Pull request #112 synchronize by Tmonster
March 6, 2025 21:03 4h 14m 25s add_trigger_to_run_the_benchmark
March 6, 2025 21:03 4h 14m 25s
Add trigger to run the benchmark
Regression #191: Pull request #112 synchronize by Tmonster
March 6, 2025 20:22 33m 22s add_trigger_to_run_the_benchmark
March 6, 2025 20:22 33m 22s
Add trigger to run the benchmark
Regression #190: Pull request #112 opened by Tmonster
March 6, 2025 20:02 20m 10s add_trigger_to_run_the_benchmark
March 6, 2025 20:02 20m 10s
new results
Run benchmark #45: Commit 24e46b8 pushed by Tmonster
March 4, 2025 20:22 2h 5m 49s results-2025-03-04-20h22m
March 4, 2025 20:22 2h 5m 49s
new results
Run benchmark #44: Commit a114ac2 pushed by Tmonster
March 4, 2025 17:48 2h 33m 58s results-2025-03-04-17h48m
March 4, 2025 17:48 2h 33m 58s
new results
Run benchmark #43: Commit a96acc7 pushed by Tmonster
March 4, 2025 15:13 2h 34m 23s results-2025-03-04-15h13m
March 4, 2025 15:13 2h 34m 23s
add code to actually run the benchmark again
Run benchmark #42: Commit 9bfe1c6 pushed by Tmonster
March 4, 2025 12:34 2h 39m 18s add_trigger_to_run_the_benchmark
March 4, 2025 12:34 2h 39m 18s
new results
Run benchmark #41: Commit d2d2cc5 pushed by Tmonster
March 4, 2025 12:32 11s results-2025-03-04-12h32m
March 4, 2025 12:32 11s
add a fetch
Run benchmark #40: Commit 0803bd0 pushed by Tmonster
March 4, 2025 12:32 12s add_trigger_to_run_the_benchmark
March 4, 2025 12:32 12s
new results
Run benchmark #39: Commit 85f7fe5 pushed by Tmonster
March 4, 2025 12:30 11s results-2025-03-04-12h30m
March 4, 2025 12:30 11s
now use git keys
Run benchmark #38: Commit 0fc2a8a pushed by Tmonster
March 4, 2025 12:30 11s add_trigger_to_run_the_benchmark
March 4, 2025 12:30 11s
attempt to push new results
Run benchmark #37: Commit 45e5b7c pushed by Tmonster
March 4, 2025 12:28 11s test_new_branch
March 4, 2025 12:28 11s
attempt to push new results
Run benchmark #36: Commit 558294f pushed by Tmonster
March 4, 2025 12:17 11s add_trigger_to_run_the_benchmark
March 4, 2025 12:17 11s
try this one more time
Run benchmark #35: Commit 7ae09d9 pushed by Tmonster
March 4, 2025 12:14 11s add_trigger_to_run_the_benchmark
March 4, 2025 12:14 11s
try this?
Run benchmark #34: Commit 870c853 pushed by Tmonster
March 4, 2025 12:02 12s add_trigger_to_run_the_benchmark
March 4, 2025 12:02 12s
trying the push thing again
Run benchmark #33: Commit 721d885 pushed by Tmonster
March 4, 2025 11:55 14s add_trigger_to_run_the_benchmark
March 4, 2025 11:55 14s
set upstream as well
Run benchmark #32: Commit 410b762 pushed by Tmonster
March 4, 2025 11:43 3m 54s add_trigger_to_run_the_benchmark
March 4, 2025 11:43 3m 54s