CI: Fix extended test failure

[2010YOUY01]

Which issue does this PR close?

• Closes #.

Rationale for this change

The extended test (job linux-test-extended) in CI is failing because of changes introduced in #16081. This PR added several failing snapshot tests for CLI integration. The CLI integration tests in CI run with backtrace disabled, while the extended tests run with backtrace enabled, which is causing the discrepancies.

Since the purpose of the failing CI job is only for tests guarded by the extended_test feature, and we don't have any for CLI tests, we can exclude CLI tests from the extended test suite.

Failed CI run: https://github.com/apache/datafusion/actions/runs/15179660797/job/42686605128
Failed CI job script:

datafusion/.github/workflows/extended.yml

Line 77 in cb45f1f

linux-test-extended:

What changes are included in this PR?

Exclude datafusion-cli test from CI extended test, job linux-test-extended

Are these changes tested?

Are there any user-facing changes?

[2010YOUY01]

I'm testing it in my local clone: https://github.com/2010YOUY01/arrow-datafusion/actions/runs/15182434324
Update: passed

[zhuqi-lucas]

LGTM Thanks @2010YOUY01 !

[blaginin]

Another potential solution: use something like

datafusion/datafusion-cli/tests/cli_integration.rs

Line 33 in cb45f1f

settings.add_filter(r"Elapsed .* seconds\.", "[ELAPSED]");

to filter out stacktrace

[blaginin]

I think other actions fail with the same error here? 🤔
https://github.com/apache/datafusion/actions/runs/15183361207/job/42699605764?pr=16145

[ding-young]

I think other actions fail with the same error here? 🤔 https://github.com/apache/datafusion/actions/runs/15183361207/job/42699605764?pr=16145

For that one, I think the author replaced B with bytes in the tests , so we need to check it again after fixing that

[2010YOUY01]

Another potential solution: use something like

datafusion/datafusion-cli/tests/cli_integration.rs

Line 33 in cb45f1f

settings.add_filter(r"Elapsed .* seconds\.", "[ELAPSED]");

to filter out stacktrace

Yes, I think this is also required for other similar usages. I think showing backtrace is common for error tests, it would be great to have a utility function for that.

[blaginin]

Created a separate issue #16146

Let's merge this PR for now to make the CI green 💚