IssueTracker

Project: platform/frameworks/support
Branch: androidx-main
Author: Radha Nakade <radhanakade@google.com>
Link:      https://android-review.googlesource.com/3510337

Migrate traffic from pixel2 to mediumphone on FTL emulators.

Migrate traffic from pixel2 to mediumphone on FTL emulators. 
 
Bug: 396715333 
 
Test: ./gradlew emoji2:emoji2-emojipicker:ftlmediumphoneapi33 
Change-Id: If5555443ca1a91479128e1bd6f4f909154c40ba2

The api-versions.json files could be generated directly from the checked in signature files without going through generateApi

I'm not sure how this could work while still using the latest API surface. We either need to provide the current API from sources like we currently do or from the current signature file. If we're relying on the current signature file, we need to depend on generateApi. If this task ran in parallel with generateApi when generateApi was out of date and needed to be rerun, it would be using an out of date signature file. In the case that generateApi was up to date, I think the API versions file task will almost always also be up to date (and cached), unless there's a change in the other versioned signature files it depends on.

The assumption that I am making is the current signature file should always be up to date at the point you are publishing (which is the only time you need to use the apiLevels.json file). If true than if generateApi did not create apiLevels.json then it would effectively be a no-op that, depending on cache state, could take a while to do nothing.

If that assumption is not correct could you explain under what conditions the current signature file would be out of date when publishing. I am sure that could happen if you are testing publishing locally but I am talking about automated publishing done as part of continuous build.

I probably confused you by saying to run generateApi in parallel. I meant you could run the check that the current checked in signature file is up to date in parallel just to double check that you are publishing the latest API.