(NFC) Skip CliRunnerTest on php80+drush+Backdrop #23184
Merged
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.
Overview
The
CliRunnerTest
goes through various permutations of CLI commands (cv
,drush
,wp-cli
) in different environments (php7
/min,php8
/max, D7, D9, BD, WP, etc). The permutation forphp8
+backdrop
+drush
has been failing persistently (https://test.civicrm.org/job/CiviCRM-E2E-Matrix/).Skip this test permutation. It is blocked by upstream issues in drush-backdrop, and (AFAIK) this permutation has never worked.
CC @seamuslee001 @herbdool
Before
These tests fail in php8+backdrop+drush:
After
The tests are skipped in php8+backdrop+drush.
Technical Details
The problem does not seem to be specific to the functionality
civicrm-core.git
-- it appears to affect anything going throughdrush-backdrop
on php8, and it's been blocked on upstream fixes. You can see this by running justdrush ev
:I'm not too worried about losing coverage here -
CliRunnerTest
still provides coverage for several adjacent configurations, ieComments
It's hard to see this when skimming the matrix (https://test.civicrm.org/job/CiviCRM-E2E-Matrix/), but there is an additional error for
backdrop,max
regardingSoapTest
. I haven't been able to reproduce this yet. I mention it only to show why these extra red-flags matter -- when we get multiple+persistent red-flags for something outside our control, we're less likely to see other red-flags.When/if there's an upstream fix, we can re-enable the test...