Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 0a2f5df

Browse files
committed
ci: freebsd: Specify debug_parallel_query=regress
A lot of buildfarm animals run with debug_parallel_query=regress, while CI didn't test that. That lead to the annoying situation of only noticing related test instabilities after merging changes upstream. FreeBSD was chosen because it's a relatively fast task. It also tests debug_write_read_parse_plan_trees etc, which probably is exercised a bit more heavily with debug_parallel_query=regress. Discussion: https://postgr.es/m/zbuk4mlov22yfoktf5ub3lwjw2b7ezwphwolbplthepda42int@h6wpvq7orc44
1 parent ad40644 commit 0a2f5df

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

.cirrus.tasks.yml

+8-1
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,14 @@ task:
139139
CPPFLAGS: -DRELCACHE_FORCE_RELEASE -DENFORCE_REGRESSION_TEST_NAME_RESTRICTIONS
140140
CFLAGS: -Og -ggdb
141141

142-
PG_TEST_INITDB_EXTRA_OPTS: -c debug_copy_parse_plan_trees=on -c debug_write_read_parse_plan_trees=on -c debug_raw_expression_coverage_test=on
142+
# Several buildfarm animals enable these options. Without testing them
143+
# during CI, it would be easy to cause breakage on the buildfarm with CI
144+
# passing.
145+
PG_TEST_INITDB_EXTRA_OPTS: >-
146+
-c debug_copy_parse_plan_trees=on
147+
-c debug_write_read_parse_plan_trees=on
148+
-c debug_raw_expression_coverage_test=on
149+
-c debug_parallel_query=regress
143150
PG_TEST_PG_UPGRADE_MODE: --link
144151

145152
<<: *freebsd_task_template

0 commit comments

Comments
 (0)