Fix web e2e (npm/vite) and Python DML CI pipelines (#29609)
### Summary
Two small, independent CI fixes that unblock currently-failing required
pipelines. The NPM packaging pipeline's web e2e consuming test broke
when a floating `vite` range pulled the just-released 7.3.x line, and
the Python DML pipeline started failing on a MeanVarianceNormalization
precision mismatch. Neither change affects runtime code.
### Key Changes
| Pipeline | File | Change | Why |
|---|---|---|---|
| NPM packaging (`web-ci` → e2e) | `js/web/test/e2e/package.json` | Cap
`vite` from `^7.1.12` to `>=7.1.12 <7.3.0` | The e2e runner uses a
non-deterministic `npm install`, so `^7.1.12` floated onto vite 7.3.6
(the tarball the install aborted on). vite 7.3.0 also bumped esbuild
`^0.25.0 → ^0.27.0`, pulling platform binaries not reliably mirrored in
the internal feed. Capping below 7.3.0 keeps the bundler smoke test on
the known-good line. |
| Python DML |
`onnxruntime/test/testdata/onnx_backend_test_series_filters.jsonc` |
Exclude `^test_mvn_cpu` from the DML EP backend test list | `test_mvn`
(MeanVarianceNormalization) fails on DML with 27/27 mismatched elements
(max rel diff ~25) — a precision issue, not a functional regression.
Filtering it matches how other DML precision/known-issue cases are
already handled in this list. |
### Testing Notes
- **NPM packaging**: re-run the web CI e2e step (`npm run test:e2e --
--browser=Chrome_default`); `npm install` in `build/js/e2e` now resolves
vite to a 7.1/7.2 release instead of 7.3.6, so the install no longer
aborts (and the Windows `npm warn cleanup ... EPERM` rollback noise
disappears).
- **Python DML**: re-run the DML python backend test job; `test_mvn_*`
is now skipped for the DML EP alongside the existing excluded cases.
