| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[heap] Split mark-compact.* files Separate MinorMC, full MC and (a few) shared utilities to separate files. The goal is to make it easier to find relevant code since the original mark-compact.* files became huge. Skipping try bots due to unrelated failures in linux-rel. NOTRY=true Bug: v8:12612 Change-Id: Ib0827b347f46cc06a06f6e5c7d951281ebb03f25 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4650871 Commit-Queue: Omer Katz <omerkatz@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#88699} | 2 年前 | |
[test] Introduce test processors Test processors can be enabled with --infra-staging flag. Rerunning tests, execution and verbose progress indicator already work as test processors. Bug: v8:6917 Change-Id: I40fc42db94dbc8629e8000a3d363030045532fe3 Reviewed-on: https://chromium-review.googlesource.com/850398 Commit-Queue: Michał Majewski <majeski@google.com> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#50399} | 8 年前 | |
[resultdb] Make suffixes more distinguishable Test ids would get an uniform format between different kinds of tests: prefix//test_id//suffix - prefix: - empty for regular tests - or 'special test' token, as in 'numfuzz' - test_id is the full name of the test as generated by test runner: - suite_name/path/to/actual/test_name - suffix is anything a test runner processor might want to add to the name: - numfuzz processor will add 'analysis' of a numeric value - variant processor will add the variant name Bug: v8:13316 Change-Id: Ied8f958173f82d8e26c62e39ccc21167ca2928ab Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4084763 Commit-Queue: Liviu Rau <liviurau@google.com> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#84736} | 3 年前 | |
[test] Refactor testrunner (4) - Removed duplication and unnecessary indirection from all suites testcfgs. - Introduced a more comprehensive context to cover both command context and other platform specific concerns. - Propagated above context to TestLoader to allow for test counting command execution on all platforms. - Wrapped original pool with another class to give it a new interface and allow injecting different implementations in the future. - Consolidated progress indicators under a single processor in the pipeline. - Consolidated result retention requirements calculation outside of pipeline chain. - Refactored LoaderProc and got it under tests. - Added some more tests for the standard runner. - Extracted BuildConfig class. Bug: v8:12785 Change-Id: I87be040e91f792a983662bb5a10d55b36a14ea7f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3701595 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/main@{#81770} | 3 年前 | |
Revert "[test] Output process list after failures on Windows" This reverts commit 743641bb8f925608752d7a1e14edc12439380395. Reason for revert: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux64%20-%20coverage/7415/overview Original change's description: > [test] Output process list after failures on Windows > > This aims to identify background processes running while other > failures occur during testing. > > Bug: v8:14373 > Change-Id: I0fa63bfcddf636bddb94cb6d0784f834b78658f1 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4931688 > Reviewed-by: Liviu Rau <liviurau@google.com> > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/main@{#90357} Bug: v8:14373 Change-Id: I7cbd8f491c98f572c35cbbc4cc81f52a54c54124 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4930894 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#90358} | 2 年前 | |
[resultdb] Add more data about tests Data added: - subtest_id as it is generated by Processors - processor_name to trace back the processors that generate subtests - path of the test - test_id suffixes introduced by processors: - numfuzz will have - an analysis suffix for analysis phase - a number suffix for the variants generated after analysis - variant processor adds a suffix for every variant - subtests will inherit suffixes from the parent tests (origin) V8-Recipe-Flags: resultdb Cq-Include-Trybots: luci.v8.try:v8_numfuzz_dbg,v8_numfuzz_rel,v8_numfuzz_tsan_compile_rel,v8_numfuzz_tsan_rel Bug: v8:13316 Change-Id: I67d8b92b575c31b201238cfbcfc76cd076a2f7af Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4081127 Commit-Queue: Liviu Rau <liviurau@google.com> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#84720} | 3 年前 | |
[test] Enable num-fuzz to skip some slow tests randomly Some tests are susceptible to run really slow with some of the flags passed on num-fuzz. This currently burns a lot of compute time and prevents other, faster tests to execute more often. This change adds a new status file state called "FUZZ_RARE" with which such tests can be marked. On num-fuzz we add a new kind of test filter that skips such tests with a certain probability. The probability can be changed on the command line. As a result, such tests will still be fuzzed, but less often. The non-determinism introduced by this should be ok on num-fuzz, which already tests non-deterministically (e.g. choosing random flags or flag values). Bug: 417413668 Change-Id: Id68ab695a08190c224010241c80a47a8f62989d6 Cq-Include-Trybots: luci.v8.try:v8_numfuzz_dbg,v8_numfuzz_tsan_rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6565342 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/main@{#100403} | 1 年前 | |
[interpreter] Add flag --proto-assign-seq-opt-count This allows testing different thresholds for the optimization as well as stress-testing the new code by also replacing single prototype assignments with the new bytecode. Bug: 429332174 Change-Id: Idcc6a1e99da7e193c4b3d08e4a24b07f18e7ca24 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7178541 Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> Reviewed-by: Raphael Herouart <rherouart@chromium.org> Auto-Submit: Matthias Liedtke <mliedtke@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#103892} | 7 个月前 | |
[numfuzz] Gracefully ignore contradictory flags NumFuzz passes various flags to V8 testing randomly, which can lead to various flag contradictions with existing flags. Up to now the system ignored the check for contradictions and kept running the test cases, leading to false positives. This change adds a new v8 flag --exit-on-contradictory-flags that exists gracefully when a contradiction is detected. On the numfuzz side we now filter simple contradictions beforehand. Measurements showed that ~2% of all numfuzz tests ran into contradictions. Around half of them are simple contradictions (repetitions and inversions), which are now filtered beforehand. The remaining ones (redundant or contradictory implications) are now ignored. Bug: v8:11826 Change-Id: I9942e203ba9668a097fabe1343dd1365c9da94c1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3650746 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Reviewed-by: Almothana Athamneh <almuthanna@chromium.org> Cr-Commit-Position: refs/heads/main@{#80589} | 4 年前 | |
Reland "[testrunner] Use relative paths consistently" This is a reland of commit 0b1d664b6da955b2c089831ab7d45b34fa4cd7a6. The android file upload was fixed in PS1..PS8. Original change's description: > [testrunner] Use relative paths consistently > > Instead of making paths relative when printing (in the progress > indicator / on failures), use relative paths already for constructing > the command line. > This ensures that the command line is consistent between > - what is printed by --verbose, > - what is printed by progress indicators, and > - what is actually being executed. > > R=machenbach@chromium.org > > Change-Id: I5f2fe5c727db8cc2013673e816ce3e18e726559c > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6781191 > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Commit-Queue: Clemens Backes <clemensb@chromium.org> > Cr-Commit-Position: refs/heads/main@{#101685} Change-Id: I5787e23fe5528deaa720a822c149ba54d245d369 Cq-Include-Trybots: luci.v8.try:v8_android_arm64_p7_rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6805698 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#101847} | 10 个月前 | |
[test] Refactor testrunner (4) - Removed duplication and unnecessary indirection from all suites testcfgs. - Introduced a more comprehensive context to cover both command context and other platform specific concerns. - Propagated above context to TestLoader to allow for test counting command execution on all platforms. - Wrapped original pool with another class to give it a new interface and allow injecting different implementations in the future. - Consolidated progress indicators under a single processor in the pipeline. - Consolidated result retention requirements calculation outside of pipeline chain. - Refactored LoaderProc and got it under tests. - Added some more tests for the standard runner. - Extracted BuildConfig class. Bug: v8:12785 Change-Id: I87be040e91f792a983662bb5a10d55b36a14ea7f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3701595 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/main@{#81770} | 3 年前 | |
[test] Refactor testrunner (4) - Removed duplication and unnecessary indirection from all suites testcfgs. - Introduced a more comprehensive context to cover both command context and other platform specific concerns. - Propagated above context to TestLoader to allow for test counting command execution on all platforms. - Wrapped original pool with another class to give it a new interface and allow injecting different implementations in the future. - Consolidated progress indicators under a single processor in the pipeline. - Consolidated result retention requirements calculation outside of pipeline chain. - Refactored LoaderProc and got it under tests. - Added some more tests for the standard runner. - Extracted BuildConfig class. Bug: v8:12785 Change-Id: I87be040e91f792a983662bb5a10d55b36a14ea7f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3701595 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/main@{#81770} | 3 年前 | |
Reland "[test] Stream full test schedule alongside json results" This is a reland of commit 1cfed53b01c63251f915e419deb231e26ae9911c Patchset 2 fixes a bug in the perf runner on Android, which previously set the duration directly - now it sets start and end time. Original change's description: > [test] Stream full test schedule alongside json results > > This writes a file in a default location alongside the json test > results, containing all start and end timestamps of all executed > tests. > > Bug: v8:14373 > Change-Id: Idb55b6cafc022814a4a6aec9590bf0cae2f111c8 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4931699 > Reviewed-by: Liviu Rau <liviurau@google.com> > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/main@{#90377} Bug: v8:14373 Change-Id: I21c042a22a52351bc084bb2ec0bd83059f04740b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4933861 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@google.com> Auto-Submit: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#90380} | 2 年前 | |
[resultdb] Add more data about tests Data added: - subtest_id as it is generated by Processors - processor_name to trace back the processors that generate subtests - path of the test - test_id suffixes introduced by processors: - numfuzz will have - an analysis suffix for analysis phase - a number suffix for the variants generated after analysis - variant processor adds a suffix for every variant - subtests will inherit suffixes from the parent tests (origin) V8-Recipe-Flags: resultdb Cq-Include-Trybots: luci.v8.try:v8_numfuzz_dbg,v8_numfuzz_rel,v8_numfuzz_tsan_compile_rel,v8_numfuzz_tsan_rel Bug: v8:13316 Change-Id: I67d8b92b575c31b201238cfbcfc76cd076a2f7af Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4081127 Commit-Queue: Liviu Rau <liviurau@google.com> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#84720} | 3 年前 | |
Reland "[resultdb] Add ResultDB indicator" This is a reland of commit 237de893e1c0a0628a57d0f5797483d3add7f005 We now guard against requests Python module not being available when running the testrunner. If preconditions (modules & luci context) are not met we no longer add ResultDBIndicator to the chain. Original change's description: > [resultdb] Add ResultDB indicator > > Adds a new indicator that will send every result to ResultDB (and ultimately in a bq table; to be configured later). > > If we are not running in a ResultDB context we introduce only a minimal overhead by exiting early from indicator. > > To test these changes in a luci context with ResultDB we activated resultdb feature flag via V8-Recipe-Flags. This feature got implemented in https://crrev.com/c/3925576 . > > > V8-Recipe-Flags: resultdb > Bug: v8:13316 > Change-Id: I5d98e8f27531b536686a8d63b993313b9d6f62c5 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3905385 > Commit-Queue: Liviu Rau <liviurau@google.com> > Reviewed-by: Alexander Schulze <alexschulze@chromium.org> > Cr-Commit-Position: refs/heads/main@{#83672} V8-Recipe-Flags: resultdb Bug: v8:13316 Change-Id: I0bdfae13cc7f250c41a18f2d3a513a3bfc580f6d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3955263 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#83711} | 3 年前 | |
Reland "[testrunner] Use relative paths consistently" This is a reland of commit 0b1d664b6da955b2c089831ab7d45b34fa4cd7a6. The android file upload was fixed in PS1..PS8. Original change's description: > [testrunner] Use relative paths consistently > > Instead of making paths relative when printing (in the progress > indicator / on failures), use relative paths already for constructing > the command line. > This ensures that the command line is consistent between > - what is printed by --verbose, > - what is printed by progress indicators, and > - what is actually being executed. > > R=machenbach@chromium.org > > Change-Id: I5f2fe5c727db8cc2013673e816ce3e18e726559c > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6781191 > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Commit-Queue: Clemens Backes <clemensb@chromium.org> > Cr-Commit-Position: refs/heads/main@{#101685} Change-Id: I5787e23fe5528deaa720a822c149ba54d245d369 Cq-Include-Trybots: luci.v8.try:v8_android_arm64_p7_rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6805698 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#101847} | 10 个月前 | |
Use fake rdb sink in tests Bug: chromium:1445854 Change-Id: I2a66717fe8a7db7dc6f736c24ef809f4f3b761a5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4813259 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#89844} | 2 年前 | |
[test] Fix encoding of resultdb artifacts By default on windows, the cp1252 encoding is used for temporary files. This doesn't map some utf-8 characters that might appear in V8's output. Ensuring utf-8 encoding should fix this. Bug: chromium:1497956 Change-Id: I6c05b5a62bec1835262fe5a29c852e555aa807fa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4994334 Reviewed-by: Liviu Rau <liviurau@google.com> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#90726} | 2 年前 | |
[resultdb] Add more data about tests Data added: - subtest_id as it is generated by Processors - processor_name to trace back the processors that generate subtests - path of the test - test_id suffixes introduced by processors: - numfuzz will have - an analysis suffix for analysis phase - a number suffix for the variants generated after analysis - variant processor adds a suffix for every variant - subtests will inherit suffixes from the parent tests (origin) V8-Recipe-Flags: resultdb Cq-Include-Trybots: luci.v8.try:v8_numfuzz_dbg,v8_numfuzz_rel,v8_numfuzz_tsan_compile_rel,v8_numfuzz_tsan_rel Bug: v8:13316 Change-Id: I67d8b92b575c31b201238cfbcfc76cd076a2f7af Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4081127 Commit-Queue: Liviu Rau <liviurau@google.com> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#84720} | 3 年前 | |
[test] Run heavy tests sequentially This adds a new status file indicator "HEAVY" to mark tests with high resource demands. There will be other tests running in parallel, but only a limited number of other heavy tests. The limit is controlled with a new parameter --max-heavy-tests and defaults to 1. The change also marks a variety of tests as heavy that recently had flaky timeouts. Heavy also implies slow, hence heavy tests are executed at the beginning with a higher timeout like other slow tests. The implementation is encapsulated in the test-processor chain. A new processor buffers heavy tests in a queue and adds buffered tests only if other heavy tests have ended their computation. Bug: v8:5861 Change-Id: I89648ad0030271a3a5af588ecc9c43285b728d6d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2905767 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/master@{#74712} | 5 年前 | |
[test] Refactor testrunner (3) - removed some 'feature envy' instances: - created a AugmentedOptions class to take care of non trivial option look-ups - moved some calculation closer the the actual data - promoted parameter that was passed around a lot (options) to filed in the offending class - similar object creation looks a bit more similar - CommandContext provides a wrapper that ensures resource de-allocation - separate tests from standard and num_fuzz runners - added a couple of more tests to improve coverage This is still in flux. But further changes risk creating a disconnect between the original implementation and further refactorings. Bug: v8:12785 Change-Id: I0ec2e9c6a81604a5cd1d4a80982dd3329c1b48db Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3686411 Commit-Queue: Liviu Rau <liviurau@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#81148} | 4 年前 | |
[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} | 3 年前 | |
[test] Cleanup Unused imports and some deprecation related updates. Bug: v8:12785 Change-Id: Ia3998a75f0c3b83eef4134741c1bda5f3d49c6f4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3678840 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/main@{#80883} | 4 年前 | |
[test] Dump traceback on test-runner interrupts Bug: v8:13113 Change-Id: I7cd37446d9ecbe271e0e5df96a4dcfd43b307c27 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3879489 Reviewed-by: Alexander Schulze <alexschulze@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#83056} | 3 年前 | |
[test] Dump traceback on test-runner interrupts Bug: v8:13113 Change-Id: I7cd37446d9ecbe271e0e5df96a4dcfd43b307c27 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3879489 Reviewed-by: Alexander Schulze <alexschulze@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#83056} | 3 年前 | |
[test] Add process-memory probe and track consumption This adds a probing mechanism for tests executed on desktop platforms. The probe tracks memory statistics with psutil. The results are added to the resultsdb entry and the json test results. For the json test results, only the top 20 tests are tracked, similar to duration. When running locally or when psutil is not available, the probe will just stay inactive. There is no significant overhead when probing every 0.2 seconds. Very fast tests will show 0 results. Similar to test duration, we can use the information from the json to list the top memory-hungry tests, which are not yet marked as HEAVY in the status file. Such a listing will be implemented as a follow up on the infra side. Bug: v8:14373 Change-Id: Ief162d5ef88bdd7792a953505feeb5a8f1e4fe94 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4946490 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@google.com> Cr-Commit-Position: refs/heads/main@{#90492} | 2 年前 | |
Allow V8 to run all unittests presubmit Search for all files with testing naming convention and run that on v8_presubmit. Also modify all PRESUBMIT files in the tools directory to include any test file with the appropriate naming convention. Bug: chromium:1306474 Change-Id: I61c1b7c71badbbc3b99705289588aa8280824d66 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3532266 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Almothana Athamneh <almuthanna@chromium.org> Cr-Commit-Position: refs/heads/main@{#79651} | 4 年前 | |
[resultdb] Make suffixes more distinguishable Test ids would get an uniform format between different kinds of tests: prefix//test_id//suffix - prefix: - empty for regular tests - or 'special test' token, as in 'numfuzz' - test_id is the full name of the test as generated by test runner: - suite_name/path/to/actual/test_name - suffix is anything a test runner processor might want to add to the name: - numfuzz processor will add 'analysis' of a numeric value - variant processor will add the variant name Bug: v8:13316 Change-Id: Ied8f958173f82d8e26c62e39ccc21167ca2928ab Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4084763 Commit-Queue: Liviu Rau <liviurau@google.com> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#84736} | 3 年前 | |
[test] Refactor testrunner (4) - Removed duplication and unnecessary indirection from all suites testcfgs. - Introduced a more comprehensive context to cover both command context and other platform specific concerns. - Propagated above context to TestLoader to allow for test counting command execution on all platforms. - Wrapped original pool with another class to give it a new interface and allow injecting different implementations in the future. - Consolidated progress indicators under a single processor in the pipeline. - Consolidated result retention requirements calculation outside of pipeline chain. - Refactored LoaderProc and got it under tests. - Added some more tests for the standard runner. - Extracted BuildConfig class. Bug: v8:12785 Change-Id: I87be040e91f792a983662bb5a10d55b36a14ea7f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3701595 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/main@{#81770} | 3 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 年前 | ||
| 8 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 2 年前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 7 个月前 | ||
| 4 年前 | ||
| 10 个月前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 2 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 10 个月前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 3 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 3 年前 | ||
| 4 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 2 年前 | ||
| 4 年前 | ||
| 3 年前 | ||
| 3 年前 |