| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
First commit of new tools/run-tests.py Review URL: https://codereview.chromium.org/10919265 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@12583 ce2b1a6d-e550-0410-aec6-3dcde31c8c00 | 13 年前 | |
[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 年前 | |
[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] Make test runner work in chromium checkout Fix a relative path issue (expectation that the out directory is relative to the cwd) to make the test runner work in a chromium checkout. Change-Id: I98420f84dd357e8aa3d41f4e2d0cca415ea62012 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6913107 Reviewed-by: Matthias Liedtke <mliedtke@chromium.org> Commit-Queue: Matthias Liedtke <mliedtke@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#102251} | 10 个月前 | |
[test] Use pathlib in test framework This turns all paths in the test frameworks and all its suite implementations from strings into pathlib paths. This makes the framework more future-proof, simplifies a lot of code and enhances readability. It comes with the risk of introducing new bugs. This is lowered using an experimental test comparison script: https://crrev.com/c/4648372. Some detailed changes: - The "path" of a test case is now a pathlib path (also in cases where the path doesn't correspond to a location on the file system). This path is always relative to the test root. - The "name" of a test case is the posix string of that path used in status files and at the command line. - All other paths are absolute. - We use some more wrapping with Path() than absolutely necessary. Reducing such a wrapping where it's not needed is a micro-optimization and the potential by introducing a bug by forgetting one is worse. - Some modules are not happy with pathlib objects, hence a few explicit str() conversions are added. Thoughts on risk: - The highest risk is that due to the newly introduced logic, some test cases are silently filtered and not run now. We'll manually compare runs before and after this change. - Each test attempted to run will either pass or fail, failures won't be silent. E.g. a wrong path passed to the cctest executable is flagged as a failure. - Wrongly constructed paths to JS test cases lead to failures (tested several manually). Other failure types: - Some string path not turned into pathlib: Will typically fail when calling any pathlib function. - Some pathlib object treated as a string: Will typically raise an exception, e.g. using in-operator. - Logic bugs in pathlib functions behaving differently than anticipated, e.g. with_suffix(): Will typically result in wrong paths, resulting in errors reading a test case. Though worst case could be silent ignoring. Cq-Include-Trybots: luci.v8.try:v8_numfuzz_dbg Cq-Include-Trybots: luci.v8.try:v8_numfuzz_rel Cq-Include-Trybots: luci.v8.try:v8_numfuzz_tsan_rel Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel Cq-Include-Trybots: luci.v8.try:v8_android_arm64_n5x_rel Cq-Include-Trybots: luci.v8.try:v8_linux64_msan_rel Cq-Include-Trybots: luci.v8.try:v8_linux64_ubsan_rel Cq-Include-Trybots: luci.v8.try:v8_android_arm64_n5x_rel Bug: chromium:1132088 Change-Id: Ifc94feb292174935db969dcf5d174d2eedcf3dfd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4538761 Reviewed-by: Liviu Rau <liviurau@google.com> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/main@{#88502} | 2 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 13 年前 | ||
| 2 年前 | ||
| 4 年前 | ||
| 10 个月前 | ||
| 2 年前 |