Michael Achenbach 29b3bd3826 [test] Include shard info in test records ... This will allow on the infra side to easier link to the respective shard on a test failure. Without that it's a hassle to find out on which shard the failing test ran. This also simplifies how the global test_config stores information. Some information was duplicated, but is now rather shared through properties if the owning object is already present. Bug: v8:13681 Change-Id: I52f01a4fac74627575d80f25923faba99eb6a1fb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4181030 Reviewed-by: Liviu Rau <liviurau@google.com> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#85429}		2023-01-23 09:50:01 +00:00
..
bugs	Allow name collision when materializing scope object	2021-11-02 13:06:43 +00:00
debug	Reland: "[wasm] Compile debug code lazily"	2022-12-15 14:59:13 +00:00
protocol	[debugger] basic test infrastructure for new debugger test api.	2016-10-21 06:38:05 +00:00
regress	[debug] Fix source position around class literals	2022-08-16 07:16:47 +00:00
wrapper	[debugger] Various break-related functionality in test wrapper	2016-10-28 08:18:34 +00:00
BUILD.gn	[build] Add data deps for d8 test suites	2018-03-26 13:44:58 +00:00
debugger.status	[mips32] Delete mips32 from v8	2022-09-13 07:54:54 +00:00
OWNERS	Use relative paths to OWNERS files	2019-08-12 13:52:52 +00:00
test-api.js	[debug][cleanup] Use consistent StepInto and StepOver naming.	2021-06-01 11:26:57 +00:00
testcfg.py	[test] Include shard info in test records	2023-01-23 09:50:01 +00:00