Skip to content

Conversation

@reshke
Copy link
Contributor

@reshke reshke commented Dec 23, 2025

Currently initdb TAP tests fails due to
number-of-checks assertions. Trivially fix specifying correct number of tests

Currently initdb TAP tests fails due to
number-of-checks assertions. Trivially fix specifying correct number
of tests
@reshke reshke added the TAP label Dec 23, 2025
@reshke
Copy link
Contributor Author

reshke commented Dec 23, 2025

As I can see in #1506
TAP tests run in CI also expects 24 tests

# Looks like you planned 22 tests but ran 24.
t/001_initdb.pl .. 
Dubious, test returned 255 (wstat 65280, 0xff00)
All 22 subtests passed 

Test Summary Report
-------------------
t/001_initdb.pl (Wstat: 65280 Tests: 24 Failed: 2)
  Failed tests:  23-24
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 22 tests but ran 24.
Files=1, Tests=24,  3 wallclock secs ( 0.02 usr  0.00 sys +  1.21 cusr  1.24 csys =  2.47 CPU)
Result: FAIL
make[1]: *** [Makefile:69: installcheck] Error 1
make[1]: Leaving directory '/__w/cloudberry/cloudberry/s

@reshke
Copy link
Contributor Author

reshke commented Dec 24, 2025

This is required for #1506 to work

@reshke reshke requested review from my-ship-it and tuhaihe December 24, 2025 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants