Add coverage for PGXNTOOL_ENABLE_FS_INSTALL / PGXNTOOL_ENABLE_PGXN_INSTALL - #70
Draft
jnasbyupgrade wants to merge 1 commit into
Draft
Add coverage for PGXNTOOL_ENABLE_FS_INSTALL / PGXNTOOL_ENABLE_PGXN_INSTALL#70jnasbyupgrade wants to merge 1 commit into
jnasbyupgrade wants to merge 1 commit into
Conversation
…STALL Add tests/updates for pgxntool commit 6966d3c (adds PGXNTOOL_ENABLE_FS_INSTALL / PGXNTOOL_ENABLE_PGXN_INSTALL): - `install` is now conditionally gated out of `test`/`verify-results`/ `installcheck`/`test-build` via `PGXNTOOL_ENABLE_FS_INSTALL`, for existing-mode/pg_tle-style testing (issues Postgres-Extensions#55, #90) - pgtap's own `pgxn install --sudo` auto-install is independently gated via `PGXNTOOL_ENABLE_PGXN_INSTALL`, defaulting to follow `PGXNTOOL_ENABLE_FS_INSTALL` Extends `test/standard/make-test.bats` with: default/override/independent- override behavior (via `print-%`); structural proof via `make -p -n` that `install`/`pgtap` prerequisites are genuinely removed from `installcheck`'s parsed rule, not just skipped at runtime; a dry-run proof (via a fake `DESTDIR`) that the `pgxn install pgtap --sudo` recipe disappears when disabled; and end-to-end proof that `make test PGXNTOOL_ENABLE_FS_INSTALL=no` succeeds against an already-installed tree but fails against a genuinely uninstalled one. Also tightens two `installcheck` prerequisite-list assertions (the pre-existing issue #79 one and the new one) to match the exact `install` token instead of a `grep -w` substring, which false-matched inside the unrelated `test/install/schedule` path. Co-Authored-By: Claude <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Draft
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PGXNTOOL_ENABLE_FS_INSTALL(gatesinstallout oftest/verify-results/installcheck/test-build, for existing-mode/pg_tle-style testing -- issues util.sh: micro-optimize array_not_empty comparison #55, #90) andPGXNTOOL_ENABLE_PGXN_INSTALL(independently gates pgtap's ownpgxn install --sudoauto-install, defaulting to followPGXNTOOL_ENABLE_FS_INSTALL).test/standard/make-test.bats: default/override/independent-override behavior, structural proof viamake -p -nthatinstall/pgtapprerequisites are genuinely removed, a dry-run proof (fakeDESTDIR) that thepgxn install pgtap --sudorecipe disappears when disabled, and end-to-end proof thatmake test PGXNTOOL_ENABLE_FS_INSTALL=nosucceeds against an already-installed tree but fails against a genuinely uninstalled one.installcheckprerequisite-list assertions (the pre-existing issue #79 one and the new one) to match the exactinstalltoken instead of agrep -wsubstring, which false-matched inside the unrelatedtest/install/schedulepath.Test plan
test/standard/make-test.bats(35/35 passed)test-allsuite (257/257 passed, 0 skipped)