Skip to content

Workflows for n/n-1 tests - Release 13 branch#8499

Merged
eaydingol merged 8 commits intorelease-13.2from
eaydingol/release-13-pipeline
Mar 12, 2026
Merged

Workflows for n/n-1 tests - Release 13 branch#8499
eaydingol merged 8 commits intorelease-13.2from
eaydingol/release-13-pipeline

Conversation

@eaydingol
Copy link
Copy Markdown
Collaborator

@eaydingol eaydingol commented Mar 9, 2026

Adds workflows to run the following schedules under n/n-1 scenarios:

check-split, check-multi, check-multi-1, check-isolation, check-operations, check-follower-cluster, check-add-backup-node, check-columnar, check-columnar-isolation, check-enterprise, check-enterprise-isolation, check-enterprise-isolation-logicalrep-1, check-enterprise-isolation-logicalrep-2, check-enterprise-isolation-logicalrep-3

The test image is generated from https://github.com/citusdata/the-process/tree/release-13-image
The image has the updated uncrustify, the related test output update is not backported to this branch, so style-check is failing.

The following N/N-1 tests are failing. These failures are expected and are caused by fixes merged after the previous release.

In Test Citus Lib N-1 / PG17 - check-multi - lib-v13.2.0 and Test Citus Coordinator N-1 / PG17 - check-multi - 13.2-1 - lib-v13.2.0

  1. subquery_in_where OK due to ae5c3f6

  2. issue_8243 OK due to ce230b2

  3. merge_repartition2 OK due to 4908841

In Test Citus Lib N-1 / PG17 - check-multi-1 - lib-v13.2.0 and Test Citus Coordinator N-1 / PG17 - check-multi-1 - 13.2-1 - lib-v13.2.0

  1. multi_modifications OK due to 2dddf43

  2. mixed_relkind_tests OK due to 2dddf43

In Test Citus Worker N-1 / PG17 - check-isolation - 13.2-1 - lib-v13.2.0 and Test Citus Coordinator N-1 / PG17 - check-isolation - 13.2-1 - lib-v13.2.0

  1. isolation_metadata_sync_vs_all OK due to 51c223a, in N-1 scenarios (13.2-1 extension with lib-v13.2.0 binary on one side), the two nodes generate textually different but functionally equivalent SQL for colocation metadata commands

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 9, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.88%. Comparing base (2f58ee6) to head (0a4b6d1).
⚠️ Report is 1 commits behind head on release-13.2.

Additional details and impacted files
@@               Coverage Diff                @@
##           release-13.2    #8499      +/-   ##
================================================
- Coverage         88.91%   88.88%   -0.03%     
================================================
  Files               287      287              
  Lines             63229    63239      +10     
  Branches           7958     7962       +4     
================================================
- Hits              56217    56212       -5     
- Misses             4683     4699      +16     
+ Partials           2329     2328       -1     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@eaydingol eaydingol force-pushed the eaydingol/release-13-pipeline branch from 4b687b9 to 988af5b Compare March 9, 2026 10:53
@eaydingol eaydingol force-pushed the eaydingol/release-13-pipeline branch 2 times, most recently from 453d56c to 38c6d45 Compare March 10, 2026 15:39
@eaydingol eaydingol force-pushed the eaydingol/release-13-pipeline branch from 3a6355c to a3baf05 Compare March 10, 2026 19:43
@eaydingol eaydingol force-pushed the eaydingol/release-13-pipeline branch from a3baf05 to 0a4b6d1 Compare March 11, 2026 11:11
Comment thread .github/workflows/build_and_test.yml
Copy link
Copy Markdown
Contributor

@ihalatci ihalatci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

failure explanations in the description, accepted

@eaydingol eaydingol merged commit 58555d3 into release-13.2 Mar 12, 2026
173 of 212 checks passed
@eaydingol eaydingol deleted the eaydingol/release-13-pipeline branch March 12, 2026 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants