Fix linux-presto-fuzzer-run CI build failure

[majetideepak]

No description provided.

[netlify]

✅ Deploy Preview for meta-velox canceled.

Name	Link
🔨 Latest commit	3e1a31d
🔍 Latest deploy log	https://app.netlify.com/sites/meta-velox/deploys/655e0e5f5eb73600082165cc

[assignUser]

That should do it :)

[pedroerp]

Can you comment on why we need to explicitly specify we want DuckDB bundled? Is it because sometimes there is DuckDB already installed in the system?

[facebook-github-bot]

@pedroerp has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[assignUser]

@pedroerp on that job we force the use of system dependencies and ddb is not installed in that image (something we can fix in a follow up)

[facebook-github-bot]

@pedroerp merged this pull request in ba1b6a2.

[conbench-facebook]

Conbench analyzed the 1 benchmark run on commit ba1b6a22.

There were 2 benchmark results indicating a performance regression:

• Commit Run on GitHub-runner-8-core at 2023-11-22 18:45:54Z
  • multiplyOutputAlwaysNullMedium (C++) with source=cpp-micro, suite=velox_benchmark_basic_simple_arithmetic
  • multiplyOutputAlwaysNullLarge (C++) with source=cpp-micro, suite=velox_benchmark_basic_simple_arithmetic

The full Conbench report has more details.

[mbasmanova]

Why are we using BUNDLED and not SYSTEM here.

I believe this change (inadvertently) broken join fuzzer CI runs: #7943

CC: @kgpai

[majetideepak]

@mbasmanova, as @assignUser mentioned, there is no DuckDB installed in the system.
But it turned out to be costly because of the Debug mode build.

[mbasmanova]

Can you comment on why we need to explicitly specify we want DuckDB bundled? Is it because sometimes there is DuckDB already installed in the system?

I wish we fixed that. It would have save me long hours debugging #7943 which happens only if DuckDB is build in debug mode.