Status Update
Comments
cc...@google.com <cc...@google.com>
du...@google.com <du...@google.com> #2
Stack overflow posting -
gv...@gmail.com <gv...@gmail.com> #3
du...@google.com <du...@google.com> #4
du...@google.com <du...@google.com> #5
gv...@gmail.com <gv...@gmail.com> #6
gv...@gmail.com <gv...@gmail.com> #7
du...@google.com <du...@google.com> #8
gv...@gmail.com <gv...@gmail.com> #9
du...@google.com <du...@google.com> #10
gv...@gmail.com <gv...@gmail.com> #11
du...@google.com <du...@google.com> #12
gv...@gmail.com <gv...@gmail.com> #13
du...@google.com <du...@google.com> #14
du...@google.com <du...@google.com> #15
co...@gmail.com <co...@gmail.com> #16
du...@google.com <du...@google.com> #17
du...@google.com <du...@google.com> #18
du...@google.com <du...@google.com> #19
co...@gmail.com <co...@gmail.com> #20
du...@google.com <du...@google.com> #21
du...@google.com <du...@google.com> #22
gv...@gmail.com <gv...@gmail.com> #23
du...@google.com <du...@google.com> #24
gv...@gmail.com <gv...@gmail.com> #25
du...@google.com <du...@google.com> #26
gv...@gmail.com <gv...@gmail.com> #27
+1 for this feature.
du...@google.com <du...@google.com> #28
du...@google.com <du...@google.com> #29
du...@google.com <du...@google.com> #30
gv...@gmail.com <gv...@gmail.com> #31
ąøą¹ąø§ąø¢ą¹ąøą¹ą¹ąø browser ą¹ąø«ą¹ąøąø”ąø«ąøą¹ąøąø¢ąøąø£ąø±ąø
du...@google.com <du...@google.com> #32
I meant that the leak canary result should have been filtered out by the --where clause in the query.
du...@google.com <du...@google.com> #33
Oh! I understand what you're saying now, the leak canary result you posted earlier was modified so that's why it wasn't caught by the where clause.
Either way, I've submitted the fix now to AGP and we just have to wait for it to land!
Unfortunately I don't have a good way to work around the issue for you as the data copying is completely reliant on the logic in AGP which can't be overridden.. something else to address separately I suppose...
du...@google.com <du...@google.com> #34
You'll probably need to do something horrible like extend the test runner to print out the resulting json on device before it's deleted after test run :/
gv...@gmail.com <gv...@gmail.com> #35
du...@google.com <du...@google.com> #36
Should be fixed in the next canary release - let me know if it's not!
gv...@gmail.com <gv...@gmail.com> #37
Attached the screenshots for the proof
du...@google.com <du...@google.com>
ki...@gmail.com <ki...@gmail.com> #38
Hi, I have the same problem which the benchmark report file. I have tried from the latest stable benchmark version 1.0.0 in ./gradew benchmark:cC --trace --info
the tests are passed but I can't find the report file on my Linux machine.
Here is AS version I'm using:
Android Studio 4.1.1
Build #AI-201.8743.12.41.6953283, built on November 5, 2020
Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 5.4.0-59-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 2014M
Cores: 4
Registry: ide.new.welcome.screen.force=true, external.system.auto.import.disabled=true
Non-Bundled Plugins: GLSL, Key Promoter X, carbon-now-sh, com.thoughtworks.gauge, org.intellij.plugins.markdown, com.intellij.marketplace, org.jetbrains.kotlin, com.vermouthx.idea, com.google.mad-scorecard
Current Desktop: ubuntu:GNOME
The screenshots that I attached are from version 1.1.0 alpha01
P/s: In the alpha version, don't know why I can't override the additionalTestOutputDir arg. The arg is always /storage/emulated/0/Android/data/com.example.benchmark.test/files/test_data.
du...@google.com <du...@google.com> #39
The additionalTestOutputDir
arg is meant to be provided to you as a writable directory from your test-apk within scoped storage. Overriding it to change what directory AGP copies from isn't supported yet afaik.
What device / api level are you using?
Description
verified: all test cases passed, having android.enableAdditionalTestOutput=true in properties, tried to run with terminal too