Following part has been modified:
1. Add tabs for selection between single generation and batch
generation. (src/components/JobConfigure.vue)
2. Change the data structure of OTAConfiguration, now it only records
the flags. The source/target build will be provided when submit jobs.
(src/services/JobSubmission.js)
3. Seperate the OTAOptions as a single component, which only takes in
the flags for backend. The selection of source/target build will be in a
seperate component. (src/components/OTAOptions.vue,
src/components/SingleOTAOptions.vue).
4. Now the partition selection can takes in more than one build, but
only show the partition list of first one. Later on, this will be able
to show the intersection of the partition lists from all given builds.
(src/components/PartialCheckbox.vue)
Point 1 enables the possibility of the dynamical loading of single/batch
ota generation pages. Point 2,3,4 allow the OTAOptions components to
be reused for batch generation.
Test: Mannual tested.
Change-Id: I1a29fa7c605596d717d19da25d31b81ce5b8fcba
1. converted the Make file to a Soong one;
2. handled the .rscript files by genrule (to include the same commands used when build
with the former .mk file);
3. the differences observed in the apks before and after the conversion
are the same as in http://b/186244109, which should not affect the
conversion here;
4. the same result was observed when run the two apks on a physical
phone(Pixel 3a XL (bonito));
5. test commands:
mma -j RsHelloCompute
adb install -r ~/aosp/out/target/product/bonito/system/app/RsHelloCompute/RsHelloCompute.apk
adb shell am start -S -n com.example.android.rs.hellocompute/.HelloCompute
Bug: 124261647
Test: compared the two apk files built by Make and Soong
Test: run two apks on a Pixel 3a XL (bonito) phone
Test: TreeHugger
Change-Id: I93a536ccedd9abe5ceb99d73d96668f0a861fb51
When traversing tree of the transformObject, _transform function with
some fields did not have a key and instead had a terminal class. This
has been updated to display the key string.
Bug: 190176285
Test: Using a pb file giving a object object previously and clicking
show diff on all, see that no object object appears now.
Change-Id: I7fa3db3a631209e1d5e1f771a93d7b3e57694309
The transform flicker object doesn't have a "isNotEmpty" property
(return undefined) and was being ignored. Instead check if
object.isEmpty === true to allow objects without a isNotEmpty
property to be displayed
Bug: 176906864
Test: compile winscope, take a SF trace, check if the layers have a
trasnform property
Change-Id: Ia466dd6b5e9f5e08fad515d31122206b6bd9898a
A variable name was mispelled and it could lead to jobs unable to be
started.
Test: Mannual tested.
Change-Id: I4067e2ae243428cb190463f55122b88d471f45f7
A complete set of flags for the CLI tool can be found in this script:
https://source.corp.google.com/android/build/make/tools/releasetools/ota_from_target_files.py
Now most of the flags are being added to the front end. However, there
are several TODOs:
1. flags that require extra arguements or file operations are not
supported yet.
2. the flags can depend or exclude on other flags. Dependency is
included in file 'JobSubmissions.js'-'OTAExtraFlags'. But the function
is not implemented yet.
Test: Mannual tested.
Change-Id: I3b6b76d48861cff81bfad86b549ff53f6536933b
timeline.
Test: Run one trace. Check that there is no navigation drop down list to
the left of the timeline. Run multiple traces. Check that the navigation
drop down list now appears.
Bug: 162716882
Change-Id: Ic466dd6b5e9f5e08fad515d31122206b6bd9898f
If an element is selected in the hierarchy view, its properties are
displayed in the property view. If the element is subsequently collapsed
in the hierarchy, the properties remain expanded.
Test: Run a WM trace. Select an element in the hierarchy view. Check
its properties are visible. Collapse the element. The properties should
not collapse.
Bug: 187320866
Change-Id: I7b8fab7d5fa5e502ff1668381be42259a421431c
Now when uploading and opening trace and dump files at the same time, the timeline should be fully interactive in Global, Focused and Targeted modes. Timestamps should appear and change as you click along the timeline.
Test: Start a trace. Run a dump on another Winscope instance. End the first trace. Download the files from both instances, upload and open them on a separate instance. Check that the timestamp changes when selecting different parts of the timeline in different modes.
bottom of Winscope.
Bug: b/163105631
Change-Id: I979dfe5eea9937b64f17ab62b2c068fac507ec87
