android / android/nowinandroid
[Bug]: `.run/Generate Demo Baseline Profile.run.xml` is no longer valid
- Dominant language
- Kotlin
- Stars
- 21.8k
- Forks
- 4.6k
- Avg merge
- 19h 20m
- Merged PRs (30d)
- 2
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Is there a StackOverflow question about this issue?
- [X] I have searched StackOverflow
### What happened?
There is a [`Generate Demo Baseline Profile`](https://github.com/android/nowinandroid/blob/main/.run/Generate%20Demo%20Baseline%20Profile.run.xml) run configuration in this project that is currently trying to execute this task:
`:benchmark:pixel6Api31atdDemoBenchmarkAndroidTest --rerun --enable-display -Pandroid.testInstrumentationRunnerArguments.androidx.benchmark.enabledRules=BaselineProfile`
Unfortunately, this configuration no longer exists (the module name changed, the device name changed, etc.).
We should either modify it, or remove it.
I would suggest to "update" it to target any "connected" device with `:benchmark:connectedDemoBenchmarkAndroidTest` to allow anyone to try and test the baseline profile generation (unless you want to use predefined adt devices).
Can anyone confirm what is the actual task executed to regenerate [baseline-prof.txt](app/src/main/baseline-prof.txt)?
Ping @mlykotom, @zsmb13, @keyboardsurfer.
🙏 sorry for the ping, you are the one updating this file according to the [history](https://github.com/android/nowinandroid/commits/main/app/src/main/baseline-prof.txt)
### Relevant logcat output
```shell
Cannot locate tasks that match ':benchmark:pixel6Api31atdDemoBenchmarkAndroidTest' as task 'pixel6Api31atdDemoBenchmarkAndroidTest' not found in project ':benchmarks'. Some candidates are: 'pixel6api31aospDemoBenchmarkAndroidTest'.
```
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Start with .run/Generate Demo Baseline Profile.run.xml and app/src/main/baseline-prof.txt. Compare the configured task with the valid candidate shown in the log, determine the task used to regenerate the baseline profile, and update or remove the run configuration so the workflow is valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100