History

auto-submit[bot] c1a301e8e8

Reverts "Manual pub roll (#156549 )" (#156607 )

Reverts: flutter/flutter#156549
Initiated by: christopherfujino
Reason for reverting: https://github.com/flutter/flutter/issues/156606
Original PR Author: christopherfujino

Reviewed By: {matanlurey}

This change reverts the following previous change:
I manually ran:

```
flutter update-packages --force-upgrade
cd dev/tools && dart bin/generate_gradle_lockfiles.dart --no-gradle-generation --no-exclusion
```

Note this bumps the `google_mobile_ads` plugin, which caused https://github.com/flutter/flutter/issues/156474. I expect it to work this time after https://flutter-review.googlesource.com/c/recipes/+/60340

2024-10-11 18:52:18 +00:00

android

Reland "Update template/test compileSdk, targetSdk, ndk versions" (#153795 )

2024-08-21 18:27:00 +00:00

ios

Migrate Xcode projects last version checks to Xcode 15.1 (#140256 )

2024-01-03 23:05:46 +00:00

lib

Add back main() methods to benchmark benches. (#156083 )

2024-10-02 16:23:47 -07:00

money_asset_manifest.json

Add asset manifest parsing benchmark (#112836 )

2022-10-07 13:39:35 +00:00

pubspec.yaml

Reverts "Manual pub roll (#156549 )" (#156607 )

2024-10-11 18:52:18 +00:00

README.md

Improve microbenchmarks a smidge (#154461 )

2024-09-03 09:10:13 -07:00

README.md

microbenchmarks

To run these benchmarks on a device, first run flutter logs in one window to see the device logs, then, in a different window, run:

flutter run -d $DEVICE_ID --profile lib/benchmark_collection.dart

To run a subset of tests:

flutter run -d $DEVICE_ID --profile lib/benchmark_collection.dart --dart-define=tests=foundation/change_notifier_bench.dart,language/sync_star_bench.dart

To specify a seed value for shuffling tests:

flutter run -d $DEVICE_ID --profile lib/benchmark_collection.dart --dart-define=seed=12345

The results should be in the device logs.

Avoid changing names of the benchmarks

Each microbenchmark is identified by a name, for example, "catmullrom_transform_iteration". Changing the name passed to BenchmarkResultPrinter.addResult will effectively remove the old benchmark and create a new one, losing the historical data associated with the old benchmark in the process.