Yicong-Huang opened a new issue, #6023: URL: https://github.com/apache/texera/issues/6023
### Task Summary `PveResourceSpec` runs in the `amber` unit CI job (`AMBER_TEST_FILTER=skip-integration`) but is **not** tagged `@IntegrationTest`, so every run shells out to real `pip` over the network: - Each `createNewPve` runs `pip install -r requirements.txt` (the full amber dependency set). - The lazy `resolveSystemPackages()` also installs `requirements.txt` into a throwaway venv, then `pip freeze`. That is ~6 full installs per spec run — network-dependent (flaky) and slow, on the PR-blocking unit path. **Fix:** funnel every child process in `PveManager` (venv creation, pip install/uninstall/freeze) through a single injectable `runProcess` seam (`PveManager` is an `object`). The spec swaps in a fake that fabricates the venv layout, emits canned output, and returns a configurable exit code — fully hermetic (no venv, no pip, no network). The metadata-file and queue-message logic stays under test, and failure paths (venv-create / install failures, system-package rejection) become cheap to cover. ### Task Type - [x] Refactor / Cleanup - [ ] DevOps / Deployment / CI - [x] Testing / QA - [ ] Documentation - [ ] Performance - [ ] Other -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
