David Rubin
David Rubin
ah lol. just look at your initial trace: ``` /home/andy/Downloads/zig/lib/compiler/test.zig:2:5: 0x1039430 in test.example (test) /home/andy/Downloads/zig/lib/compiler/test_runner.zig:158:25: 0x104479c in mainTerminal (test) ``` I have a feeling you weren't actually in `lib/compiler`
Problem lies in the encoding of the DWARF. - when we parse it back, it provides a duplicate `dir_index` for two different dirs - when running `objdump` on the compiled...
Zig Version: `0.13.0-dev.49+7053eb06c` Stack Trace ``` thread 233764 panic: reached unreachable code /home/david/Code/zig/src/type.zig:2228:33: 0x1abe402 in intInfo (zig) .simple_type => unreachable, // handled via Index enum tag above ^ /home/david/Code/zig/src/codegen/llvm.zig:4225:70: 0x1b3d68b...
I think this would require us to have async for something like `cancelawait` or spawn a manager thread. With status quo, how do you plan to time out the function...
> a spawned test process could communicate the timeout requirement back to the parent build (/ test server) process, This is what I was referring to. This `test` process runs...
The issue that I see is that we would not know which test was the one hanging (timing out).
That's an interesting idea, we could have the "latest" test being ran and we'll know if it times out. In the future I would like have this ability in the...
How's this?
Ah my apologies, I did not phrase that correctly. One moment.
Duplicate of #246 I believe.