davidot 3b020c6fb4 test262-runner: Use alarm instead of setitimer ... Since setitimer is not implemented in Serenity we use alarm which triggers SIGALRM after the timeout. We also don't use a signal handler as we are doing things that serenity doesn't like/doesn't allow. Linux dealt with allocating and writing in a signal handler but it is undefined, so instead we just let the process die by SIGALRM. This means we instead of reading the output can detect timeouts by checking how the process died.		2022-09-11 20:25:51 +01:00
..
CMakeLists.txt	LibJS: Allow negative pointers in Value	2022-09-10 00:05:32 +01:00
test-bytecode-js.cpp	LibJS: Remove {Bytecode::,}Interpreter::global_object()	2022-08-23 13:58:30 +01:00
test-invalid-unicode-js.cpp	Everywhere: Add sv suffix to strings relying on StringView(char const*)	2022-07-12 23:11:35 +02:00
test-js.cpp	LibJS: Replace GlobalObject with VM in ArrayBuffer AOs [Part 11/19]	2022-08-23 13:58:30 +01:00
test-value-js.cpp	LibJS: Allow negative pointers in Value	2022-09-10 00:05:32 +01:00
test262-runner.cpp	test262-runner: Use alarm instead of setitimer	2022-09-11 20:25:51 +01:00