执行增量编译时,可正常编译到手机,但控制台一直在运行gradle_check_mobile_change_task任务
- Dominant language
- Java
- Stars
- 5.4k
- Forks
- 620
- PR merge metrics
- No merged PRs in 30d
Description
$ **python freeline.py**
[INFO] preparing for tasks...
[-][connect_device_task] finished. in 13.0s
[-][gradle_aapt_task] finished. in 0.0s
[-][app] finished. in 2.3s
[-]**[gradle_check_mobile_change_task] finished. in 144.8s**
[-][merge_dex_task] finished. in 0.0s
[-][gradle_push_history_inc_task] failed. in 0.0s
[-][gradle_sync_task] failed. in 0s
[-][gradle_backup_inc_product_task] failed. in 0s
[-][clean_cache_task] failed. in 0s
[-][update_stat_task] failed. in 0s
[ERROR] --------------------------------------------------------
[ERROR] Freeline ERROR
[ERROR] --------------------------------------------------------
[ERROR] --------------------------------------------------------
[ERROR] get sync ticket failed
[ERROR] --------------------------------------------------------
[DEBUG] Prepare tasks time: 0.2s
[DEBUG] Task engine running time: 157.8s
[DEBUG] Total time: 158.0s
[DEBUG] --------------------------------------------------------
直到自动退出任务,估计是超时了
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by running python freeline.py and trace the gradle_check_mobile_change_task entry point shown in the report. Reproduce the long-running task and inspect why the following sync and cache tasks fail; done means incremental compilation completes without the apparent timeout and the subsequent tasks succeed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, python
- Domain
- build-system, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100