Skip to content

fix(deploy-suite): create .next/trace before build to avoid ENOENT noise on build failure #1200

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
james-elicx merged 1 commit into from
May 14, 2026
+9 −5
Merged

fix(deploy-suite): create .next/trace before build to avoid ENOENT noise on build failure #1200

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions scripts/e2e-deploy.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -247,6 +247,15 @@ cleanup_on_error() {

trap cleanup_on_error EXIT

# Some Next.js tests check for .next/trace existence (telemetry trace file)
# during the test harness's destroy() cleanup. vinext doesn't produce one, so
# create an empty file to satisfy those checks. Do this BEFORE any step that
# can fail (dep install, vinext init, vinext build) so the file exists even
# on failure — otherwise the test harness logs ENOENT noise (303 lines per
# deploy-suite run before this fix).
mkdir -p ".next"
: > ".next/trace"

if [ ! -f "${VINEXT_PKG_DIR}/dist/cli.js" ]; then
echo "vinext dist/cli.js not found at ${VINEXT_PKG_DIR}/dist/cli.js" >&2
echo "Build vinext first: corepack pnpm build" >&2
Expand Down Expand Up @@ -515,11 +524,6 @@ if [ -f "pages/blocking-fallback/[slug].js" ] || [ -f "pages/blocking-fallback/[
echo 'Warning: data for page "/blocking-fallback/[slug]" (path "/blocking-fallback/lots-of-data") is 256 kB which exceeds the threshold of 128 kB, this amount of data can reduce performance' >> "${BUILD_LOG}"
fi

# Some Next.js tests check for .next/trace existence (telemetry trace file).
# vinext doesn't produce one, so create an empty file to satisfy those checks.
mkdir -p ".next"
: > ".next/trace"

BUILD_ID="$(read_build_id)"

# The Next.js test harness parses these markers from the logs script output
Expand Down
Loading