You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 756360f
Browse filesBrowse the repository at this point in the historyBrowse files
[bazel] Under the prebuilt engine, the facsimile's stamps and iOS engines are bin/cache's
A tool test's SDK facsimile under --config=prebuilt_engine laid bin/cache's
engine directories but stamped them as the tree's build does: engine.stamp,
engine_stamp.json, flutter.version.json and each artifact set's stamp
with the checkout's HEAD (@engine_version). On a bot the two agree (the
bot's bin/cache holds the commit's own engine); on a developer's machine
bin/cache holds the content hash's build, stamped with the commit that
built it, and macos_content_validation_test found the framework's
FlutterEngine revision differing from engine_stamp.json's (the Mac tester's
T78/T79). The iOS engines, meanwhile, came from the tree under either
configuration: the apple shard built them -- hours the first time -- even
with `flutter precache --ios` done.
Now, under the prebuilt engine:
- @flutter_bin_cache//:stamps (new): bin/cache's *.stamp, engine_stamp.json,
flutter.version.json and engine.realm as the tool left them, laid through
`cache` with the engine's directories. The facsimile's bookkeeping says
what its artifacts are, and a set the tool has not fetched has no stamp,
so the tool fetches it as the checkout's would. The realm stays explicit
too (the Gradle plugin reads the file unconditionally).
- The iOS engine directories on a Mac from bin/cache
(@flutter_bin_cache//:ios_engine{,_profile,_release}, new, through
//build_defs/engine:prebuilt_ios_engine_*_directory -- files_directory,
empty where not precached) instead of the tree's.
- The Android gen_snapshots still come from the tree; their stamp says
bin/cache's revision (//bin/internal:prebuilt_android_sdk_stamp, from
@engine_version's new PREBUILT_ENGINE_VERSION = bin/cache/engine.stamp,
watched; empty without one) so that the tool takes them as current.
- The tree's facsimile is unchanged: _TOOL_CACHE_FILES_BASE keeps the
versioned stamps; the common files (the tool's snapshot, the realm, the
fonts' and Gradle wrapper's pins, the iOS USB stamps) are
_TOOL_CACHE_FILES_COMMON, which the prebuilt side takes alone.
The stamps taken are the engine's and its artifact sets' alone: the iOS
USB artifacts' stamps stay the facsimile's own, since on Linux the tool
lays no such artifacts and rewrites those stamps (a bin/cache stamp there
is a read-only file: the first run of this change), and the fonts', the
Gradle wrapper's and the Android gen_snapshots' the facsimile writes.
On the bots nothing changes in value: bin/cache's stamps there are the
commit the shards run at. Checked here with bin/cache at this commit's own
engine (`flutter precache --linux --web` under FLUTTER_PREBUILT_ENGINE_
VERSION and the archives realm): the integration shard's analyze_once,
flutter_run and hot_reload tests and the desktop shard's
build_linux_config_only pass under --config=prebuilt_engine, the
facsimile's cache carrying bin/cache's stamps; Bazel analysis of the tool
suites under both configurations. On a Mac with `flutter precache --macos
--ios` the apple shard runs from bin/cache alone, and both content
validation tests compare like with like (the Mac tester's next task).
0 commit comments