TEST PR

[alamb]

I am using this to refine a github API scrapting

Which issue does this PR close?

• Closes #.

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

[alamb]

This is a test comment

[alamb]

run benchmark

[alamb]

🤖 Hi @alamb, thanks for the request (#19000 (comment)). scrape_comments.py only supports whitelisted benchmarks: clickbench_extended, clickbench_partitioned, tpch. Please choose one of these with run benchmark <name>.

[alamb]

🤖 Hi @alamb, thanks for the request (#19000 (comment)). scrape_comments.py only supports whitelisted benchmarks: clickbench_1, clickbench_extended, clickbench_partitioned, clickbench_pushdown, tpch, tpch10, tpch_mem, tpch_mem10. Please choose one of these with run benchmark <name>.

[alamb]

run benchmarks

[alamb]

run benchmark clickbench_pushdown

[alamb]

🤖 ./gh_compare_branch.shBenchmark Script Running
Linux aal-dev 6.14.0-1018-gcp #19~24.04.1-Ubuntu SMP Wed Sep 24 23:23:09 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Comparing alamb/release_instructions (591341a) to 7b12666diff using: tpch_mem clickbench_partitioned clickbench_extended
Results will be posted here when complete

[alamb]

🤖 Hi @alamb, thanks for the request (#19000 (comment)). scrape_comments.py only supports whitelisted benchmarks: clickbench_1, clickbench_extended, clickbench_partitioned, clickbench_pushdown, tpch, tpch10, tpch_mem, tpch_mem10. Please choose one of these with run benchmark <name>.

[alamb]

run benchmarks foo clickbench_1 bar

[alamb]

🤖 Hi @alamb, thanks for the request (#19000 (comment)).

scrape_comments.py only supports whitelisted benchmarks: clickbench_1, clickbench_extended, clickbench_partitioned, clickbench_pushdown, tpch, tpch10, tpch_mem, tpch_mem10.

Please choose one or more of these with run benchmark <name> or run benchmarks <name1> <name2>...

Unsupported benchmarks: foo, bar.

[alamb]

show benchmark queue

[alamb]

🤖 Hi @alamb, you asked to view the benchmark queue (#19000 (comment)).

Job	User	Benchmarks	Comment
19000_3596642041.sh	alamb	sql_planner	#19000 (comment)
19002_3596511414.sh	alamb	clickbench_partitioned	#19002 (comment)
19018_3596651489.sh	rluvaton	default	#19018 (comment)

[alamb]

show benchmark queue

[alamb]

🤖 Hi @alamb, you asked to view the benchmark queue (#19000 (comment)).

Job	User	Benchmarks	Comment
18572_3596717224.sh	Dandandan	tpch_mem clickbench_partitioned	#18572 (comment)
18572_3596718568.sh	Dandandan	tpch	#18572 (comment)
19018_3596651489.sh	rluvaton	default	#19018 (comment)

[alamb]

show benchmark queue

[alamb]

🤖 Hi @alamb, you asked to view the benchmark queue (#19000 (comment)).

Job	User	Benchmarks	Comment
18415_3596731381.sh	alamb	sql_planner	#18415 (comment)
18572_3596717224.sh	Dandandan	tpch_mem clickbench_partitioned	#18572 (comment)
18572_3596718568.sh	Dandandan	tpch	#18572 (comment)
19018_3596651489.sh	rluvaton	default	#19018 (comment)

[alamb]

🤖 Hi @alamb, you asked to view the benchmark queue (#19000 (comment)).

Job	User	Benchmarks	Comment
19002_3596511414.sh	alamb	clickbench_partitioned	#19002 (comment)
19000_3596642041.sh	alamb	sql_planner	#19000 (comment)
19018_3596651489.sh	rluvaton	default	#19018 (comment)
18415_3596731381.sh	alamb	sql_planner	#18415 (comment)
18572_3596718568.sh	Dandandan	tpch	#18572 (comment)
18572_3596717224.sh	Dandandan	tpch_mem clickbench_partitioned	#18572 (comment)