Reland Android systrace#29080
Conversation
…, and enable systracing in release mode on Android (flutter-team-archive#28903)" (flutter-team-archive#29071)" This reverts commit a2773d5.
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat. If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
|
@zanderso - I had a successful run here: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/dnfield_google.com/a5e0ef9eeb08d87f7a542b482f782c281ce20eada7392a93c5a05697870b3c12/+/build.proto I've added some more logging so that if this fails again we'll know why. I also added a 10 minute timeout on the part where we wait for the observatory to be available to avoid tying up the bot for longer than that. |
| break | ||
| # If it takes longer than 10 minutes to find the observatory, avoid tying up | ||
| # the bot. | ||
| logcat.wait(timeout=(10 * 60)) |
There was a problem hiding this comment.
I don't follow how this works. Isn't this line only reached if the logcat process dies or the loop on 62 finds the Observatory line?
There was a problem hiding this comment.
Either way, if this code doesn't work, we'll have to fix it as a P0 whether the bot is taking 60 minutes or 10 minutes to fail, so I'd recommend skipping the timeout here.
There was a problem hiding this comment.
Hm. I think yo'ure right. I had this in here at one point when I wasn't setting up the popen correctly and it seemed to help, but now I think I was wrong.
I'll just remove the line entirely.
There was a problem hiding this comment.
Rerunning led to be sure: https://ci.chromium.org/swarming/task/5679c2230fabac10?server=chromium-swarm.appspot.com
|
The logs for the test run show a Java exception. Is that expected: |
|
Yes - scenario app does not have plugins. We should probably fix that. |
|
This one looks like it's hanging. Will try to figure out what's going on here. |
I'm surprised that a scary looking exception in the logs is part of normal operation here. It makes it seem like the app might be broken or misconfigured. @blasten @stuartmorgan |
|
Normally the Flutter tool would generate an empty GeneratedPluginRegistrant and the exception wouldn't happen. The Scenario app doesn't have it because it's not created by the tool. |
|
I think I've figured out the problem - sometimes LeakCanary's starting an activity instead of the one we actually want. I'm trying to use a different method that will not allow that to happen. Latest run is at https://ci.chromium.org/swarming/task/567a8666de29d410?server=chromium-swarm.appspot.com |
|
|
||
| print('Trace did not contain ShellSetupUISubsystem, failing.') | ||
| return 1 | ||
|
|
Adding more logging to see if I can figure out what's going on on the bot.