Disable Ntex scenarios in CI (Plaintext, Json, Fortunes)

[LoopedBard3]

All three Ntex scenarios (Plaintext, Json, Fortunes) have been failing in benchmarks-ci-01 and benchmarks-ci-02 every run since the Mar 26 build. The docker builds for both ntex-plt.dockerfile and ntex-db.dockerfile fail to compile:

error[E0308]: mismatched types
   --> /usr/local/cargo/git/checkouts/postgres-.../tokio-postgres/src/query.rs:77:52
   |
77 |             encode_bind(statement, params, "", buf)?;
   |             -----------                        ^^^ expected `&mut BytesMut`, found `&mut BytePages`
error: could not compile `tokio-postgres` (lib) due to 9 previous errors

Root cause

In TechEmpower/FrameworkBenchmarks/frameworks/Rust/ntex/Cargo.toml, tokio-postgres is a top-level dependency (not feature-gated) pointing at the fafhrd91/postgres ntex-3 fork (frozen at commit fbc7a17). Every ntex binary in the workspace builds it — including ntex-plt, not just ntex-db.

The caret-versioned ntex-bytes = { version = "1.5", features=["simd"] } resolves to ntex-bytes 1.6.0 (released 2026-05-02), which introduced the BytePages type. The fafhrd91 fork still uses BytesMut, so the workspace fails to compile end-to-end.

TechEmpower/FrameworkBenchmarks is now archived (last push 2026‑03‑24), so a real upstream fix is not coming.

Change

Comment out all three Ntex scenarios in the three places they run:

File	Scenarios disabled
build/frameworks-scenarios.yml	Ntex Plaintext, Ntex Json
build/frameworks-database-scenarios.yml	Ntex Fortunes
build/containers-scenarios.yml	Json NTex, Fortunes NTex

Each disable carries an explanatory comment that cross-references the other sites, so it's easy to re-enable as a set if someone forks/pins the ntex source back into a working state.

Context

Failing crank invocations from the latest CI runs:

• Ntex Plaintext (build 2974984): docker build --pull -t benchmarks_ntex-plt -f frameworks/Rust/ntex/ntex-plt.dockerfile .../frameworks/Rust/ntex/
• Ntex Json (same build): same dockerfile, exits 101
• Ntex Fortunes (build 2974764): docker build --pull -t benchmarks_ntex-db -f frameworks/Rust/ntex/ntex-db.dockerfile .../frameworks/Rust/ntex/

Drafting for visibility — the Blazor Wasm half of the CI red is being addressed separately (dotnet/aspnetcore#66686 upstream, with a short-term local workaround in LoopedBard3/Benchmarks#4).

[Copilot]

Pull request overview

This PR disables the failing Ntex Fortunes benchmark runs in CI while leaving other Ntex scenarios active.

Changes:

• Comments out the Ntex Fortunes database scenario entry.
• Comments out the Ntex Fortunes container matrix scenario entry.
• Adds explanatory comments documenting the dependency breakage and re-enable guidance.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
build/frameworks-database-scenarios.yml	Disables the fortunes_ntex database benchmark and documents the reason.
build/containers-scenarios.yml	Disables the fortunes_ntex container matrix benchmark and links to the matching database scenario disable.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[LoopedBard3]

Converting back to draft as there may be more NTex tests to disable.