ci: add –extended when using –usecli #34998

1. 
   polespinasa commented at 8:37 pm on April 3, 2026: member

   The current CI doesn’t cover the case of running all tests with --extended if using --usecli. This led to a test failing (feature_index_prune.py) if run with --usecli and the CI not catching it. See #34991 for context.

   The CI obviously will fail in this PR until #34991 is merged into master.

   I don’t know if this is the best approach; I just looked for a ci using --usecli and added the --extended flag to cover these scenarios. I’m open to changing the approach.

2. ci: add --extended when using --usecli 69e15e3768
3. DrahtBot added the label Tests on Apr 3, 2026
4. 
   DrahtBot commented at 8:38 pm on April 3, 2026: contributor

   The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

   Reviews

   See the guideline for information on the review process. A summary of reviews will appear here.

5. 
   polespinasa commented at 8:38 pm on April 3, 2026: member

   Friendly pinging you here @fanquake
6. DrahtBot added the label CI failed on Apr 3, 2026
7. 
   fanquake commented at 8:11 am on April 4, 2026: member

   I think it would be better to pick one of the jobs already using --extended, and add --usecli.

Contributors
polespinasa DrahtBot fanquake

Labels
Tests CI failed