fix flaky test

@paperdave we must always use `bunEnv` in the `env` to ensure that the color settings and other stuff doesn't cause bun to produce extraneous stdout input when using console.log

Additionally, the console.log was left in (which is okay)

1 files changed, 2 insertions, 3 deletions

diff --git a/test/regression/issue/03216.test.ts b/test/regression/issue/03216.test.ts
index fd4f391d0..5eced0bf9 100644
--- a/test/regression/issue/03216.test.ts
+++ b/test/regression/issue/03216.test.ts
@@ -3,7 +3,7 @@ import { test, expect } from "bun:test";
 import { tmpdir } from "os";
 import { mkdtempSync, writeFileSync } from "fs";
 import { join } from "path";
-import { bunExe } from "harness";
+import { bunEnv, bunExe } from "harness";
 
 test("runtime directory caching gets invalidated", () => {
   const tmp = mkdtempSync(join(tmpdir(), "bun-test-"));
@@ -33,10 +33,9 @@ try {
   const result = Bun.spawnSync({
     cmd: [bunExe(), "run", join(tmp, "index.ts")],
     cwd: tmp,
+    env: bunEnv,
   });
 
-  console.log(bunExe(), join(tmp, "index.ts"), result.stdout.toString("utf-8"));
-
   expect(result.exitCode).toBe(0);
   expect(result.stdout.toString("utf-8")).toBe("1\n");
 });