Due to new UI, Accessibility Trace and IM Trace views were broken. This
CL passes values in for presentTags and presentErrors to ensure the
views display as expected.
Bug: b/197628035
Test: run a trace with all checkboxes ticked and ensure the views
display as expected.
Change-Id: Iad98ab88b0250447ead72c5bcf467f8873d25182
Fixed all failing spec tests so that object transformations, diff tree
generation and proto file decoding can all be tested via yarn.
Bug: b/196210353
Test: `yarn run test`
Change-Id: Iefd41dd93d6a591756d1a60ae6e42c3b08f9d5e0
At the start or end timestamp of a transition, or at an error timestamp, colour coded tags show up
next to the relevant layer/task in the WM and SF trace hierarchy views.
Tick the transition checkbox to only show entries that have tags/errors.
Compatible with flat checkbox.
Bug: b/196544612
Test: upload the zip onto the x20 (see bug) and test above.
Change-Id: Ied84adbedc38324629c8b50178b44041f8e8b66e
Extend the tag timeline display from global to specific WM/SF trace
timelines. During focused or targeted navigation, the tags/errors should display for their associated trace
only. On global navigation, the minimum start and maximum end timestamp
for each transition is displayed. In the search bar, under transitions
and errors, note that the timestamps displayed as the global start and
end.
Bug: b/197066003
Test: upload SampleWinscope.zip from bug and test the different
navigation types.
Change-Id: Id273bf77425c504d943f1ee9716ce2f3ad0ec9c5
Add a searchbar to bottom of Winscope that can be used to navigate through
all the tags/transitions/errors present in a trace (integrating existing timestamp search).
Choose the desired tab to set the type of search. Typing input into the relevant search will filter the elements.
Click on the start or end timestamp in the scrollable search table to navigate to that
timestamp in the timeline. Click on a transition in the search table to navigate to the start timestamp for that transition. Click on a transition in the timeline to toggle between start and end timestamps for that transition.
Bug: b/196197875
Test: upload the traces on the bug and test the above implementations on
the x20.
Change-Id: Ib3a0fff770cc65a38e50a8d99f130752b2f98eeb
Use vuex to store the otaConfig, now the history configurations can be
reused in the job detail page. Also the targetBuilds, incrementalSources
are not stored in vuex as well. Once the targetBuilds are chosen, it
will not lose the states when switching the tab between singleOTA,
batchOTA and chainOTA.
Test: npm run test:unit
Change-Id: I563ac0c79fd0cedd5e71e8722b956545f6624551
The extra space in args['extra'] may cause the ota generation fail.
Test: python test_ota_interface.py -v
Change-Id: Iac6d06a89c52ab7554e54c08e5e04496b3da730a
Now ticking the flat checkbox displays all entries without indentation,
and only visible entries are shown upon ticking only visible.
Bug: b/196951608
Test: upload a WM or SF trace and tick flat - all entries should be
aligned to left of Hierarchy box.
Change-Id: Iedb755d94895afcdca334871e980064c79430206
Add test to two classes: BuildInfo and TargetLib. BuildInfo is a
dataclass which can store and parse Android Build informations from an
OTA package. TargetLib is a database interface which can be used to
store and extract BuildInfo.
Please refer to this CL for more details of these two classes:
https://android-review.googlesource.com/c/platform/development/+/1735315
Test: python test_target_lib.py -v
Change-Id: I3b2143af7f3708207b6c53744d903d3dcee92d55
Python map function returns an iterator that cannot be reused. Convert
it into a list instead to support multiple usages.
Also, add an error message to the ocnsole if no files are returned
Test: run proxy, start/stop trace 2+ times in a row
Change-Id: I09e4a4a28315b28f8d6eabdbfe60890cdfb8510c
Problem was that we were relying on getProperties to iterate through all
the properties to format them, but getProperties would filter out any
falsy value so all properties that had fasly values were pre-filtered out regardless of if show defaults was toggled or not.
We also make sure that null and undefined fields are shown when show
defaults is enabled
Test: Check proto section of entries in winscope to see all missing entries
Fixes: 187463843
Change-Id: Iaf6ef1b855edafb0dfbd324e73bbd5c3ce1b2f59
If a single read request contains the entire manifest, we will return
right after prefixLength is computed, and the UI just hangs there.
Test: load a small OTA pkg
Change-Id: Idb93fdba103f9c6e7b14974b45d1aecdb2ae9168
Store transition types in enum so easier to type check in Typescript if necessary later on.
Bug: b/196203538
Test: check that the tag trace attached to the bug still uploads
correctly
Change-Id: I2994f58ceb1d49bd82af54fb075369bd70dc1394
The ProcessManagement helps initiate OTA generation processes and
monitor those processes. Add some test and comments to this class.
Please refer to:
https://android-review.googlesource.com/c/platform/development/+/1736940
for more details.
Test: python test_ota_interface.py -v
Change-Id: Ib22fca4c5a670f8b55db8a4175fef16d92eaceaf
Add testcases for ota_interface.JobInfo, which is used as object to
store task information and serve/read data to/from database.
Refer to:
https://android-review.googlesource.com/c/platform/development/+/1736940
for more details.
Test: python test_ota_interface.py -v
Change-Id: I74dcb16390078bd9258da490e21cb2b73dd78e81
