Meghan Denny

https://github.com/oven-sh/bun/actions/runs/9216072907 https://github.com/oven-sh/bun/pull/11306/commits/86743996df6f1a1f41576c437567c7505ba03f50

ci: windows: fix dns.getServers test

1

`dns.resolveNs (empty string)` and `dns.resolveCname (cname.socketify.dev)` are still timing out though and being investigated

windows: fix bunx ci test

1

I have noticed it can sometimes rarely still fail which im looking into. but it used to fail every time consistently so I wanted to get the progress in a...

in `test/js/bun/shell/bunshell.test.ts` ```ts test("stacktrace", async () => { // const folder = TestBuilder.tmpdir(); const code = /* ts */ `import { $ } from 'bun' $.throws(true) async function someFunction() {...

test: bun-install: use runBunInstall helper

1

tests should still pass but be more consistent and easier to write more

``` 4958 | stdout: "ignore", 4959 | stderr: "ignore", 4960 | env: testEnv, 4961 | }); 4962 | 4963 | expect(await proc.exited).toBe(0); ^ error: expect(received).toBe(expected) Expected: 0 Received: 3 at...

``` Loaded page Loaded counter counter a Error: at at at at at at at at at at at at at at at at at at at at at at...

ci: make test/js/bun/shell/commands/rm.test.ts less flaky

2

typical times for the node_modules test range from 2713.78ms to 9518.02ms slightly increasing the timeout length and lowering the parallelism should make this much less flaky to network conditions

`error: TODO: implement @ptrCast between slices changing the length`

1

### Zig Version 0.12.0 ### Steps to Reproduce and Observed Behavior ```zig const std = @import("std"); const builtin = @import("builtin"); test { const a: u32 = 0xCE94C13E; const b: *const...

- `zig build test` holds the output so you can't see the progress as it runs - print nothing on success - by default will cache not only builds but...