fa88e0c91f
This CL: * Adds a benchmark of running `dart analyze` on a single small file. * Adds a benchmark of running `dart analyze` on a single project. * Adds a benchmark of running `dart analyze` on several projects. * Adds a hidden flag to `dart analyze` so it reports ram usage: run via `dart analyze --format=json --memory` and the memory usage will be reported in the json output. All the bencmarks run without and with cache for speed testing, and without and with cache when measuring memory usage. The idea of running this via `dart analyze` instead of running either the script or the snapshot is to measure the "real world" speed which could be different (although in practise it _does_ just run the snapshot). Future CL(s) should also add benchmarks for queries using the language server. Change-Id: Iad6d6d72c1a2ed18ab51d056b4914f8b6eb963e4 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/276100 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Jens Johansen <jensj@google.com> |
||
---|---|---|
.. | ||
_fe_analyzer_shared | ||
_js_interop_checks | ||
analysis_server | ||
analysis_server_client | ||
analyzer | ||
analyzer_cli | ||
analyzer_plugin | ||
analyzer_utilities | ||
async_helper | ||
build_integration | ||
compiler | ||
dart2js_info | ||
dart2js_runtime_metrics | ||
dart2js_tools | ||
dart2native | ||
dart2wasm | ||
dart_internal | ||
dartdev | ||
dds | ||
dds_service_extensions | ||
dev_compiler | ||
expect | ||
front_end | ||
frontend_server | ||
js | ||
js_ast | ||
js_runtime | ||
js_shared | ||
kernel | ||
language_versioning_2_7_test | ||
meta | ||
modular_test | ||
native_stack_traces | ||
nnbd_migration | ||
scrape | ||
smith | ||
sourcemap_testing | ||
status_file | ||
telemetry | ||
test_runner | ||
testing | ||
vm | ||
vm_service | ||
vm_snapshot_analysis | ||
wasm_builder | ||
.gitignore | ||
BUILD.gn | ||
OWNERS | ||
pkg.status | ||
README.md |
Package validation
The packages in pkg/
are automatically validated on the LUCI CI bots. The
validation is largely done by the tools/package_deps
package; it can be tested
locally via:
dart tools/package_deps/bin/package_deps.dart
Packages which are published
There are several packages developed in pkg/
which are published to pub.
Validation of these packages is particularly important because the pub tools are
not used for these packages during development; we get our dependency versions
from the DEPS file. Its very easy for the dependencies specified in a package's
pubspec file to get out of date wrt the packages and versions actually used.
In order to better ensure we're publishing correct packages, we validate some properties of the pubspec files on our CI system. These validations include:
- that the dependencies listed in the pubspec are used in the package
- that all the packages used by the source are listed in the pubspec
- that we don't use relative path deps to pkg/ or third_party/ packages
Packages which are not published
For packages in pkg/ which we do not intend to be published, we put the following comment in the pubspec.yaml file:
# This package is not intended for consumption on pub.dev. DO NOT publish.
publish_to: none
These pubspecs are still validated by the package validation tool. The contents are more informational as the pubspecs for these packages are not consumed by the pub tool or ecosystem.
We validate:
- that the dependencies listed in the pubspec are used in the package
- that all the packages used by the source are listed in the pubspec
- that a reference to a pkg/ package is done via a relative path dependency