linaro-android

linaro-android@lists.linaro.org

1071 discussions

lcr-reference-android: TC2: HMP scheduler test summary 15.07

by Naresh Kamboju

Hi Team, LCR reference android TC2: HMP Scheduler test summary 15.07 Here is test result summary for LCR reference android HMP Scheduler test on vexpress TC2 platform with Android image. High lights : ----------------- - No new bug found sched_tests.git No of Test Cases Tests Run Tests Pass Tests Fail Absolute pass rate (%) Failure Analysis/Comments Regression 20 19 19 0 100% basic_suite 14 10 10 0 100% core_suite 10 6 5 1 83% [1] extended_suite 20 8 8 0 100% loadbalance_suite 2 2 2 0 100% scaleinvariance_suite 5 5 5 0 100% pmu_suite 11 11 11 0 100% [4] hwbreakpoint_suite 1 1 1 0 100% taskpacking_suite 1 1 1 0 100% thresholds_suite 1 1 1 0 100% irqs_suite 2 2 1 1 50% [2] usecase 3 3 2 1 67% [3] non-functional_suite 6 6 6 0 100 % Bug list : ----------- [1] HMP Scheduler test suite: core_test_scn03.2a test case failed https://bugs.linaro.org/show_bug.cgi?id=396 [2]HMP Scheduler test suite: 01_irqs_on_big test case failed https://bugs.linaro.org/bugzilla/show_bug.cgi?id=1591 [3] HMP Scheduler test suite: 01_rttasks test case failed https://bugs.linaro.org/bugzilla/show_bug.cgi?id=1590 [4] HMP scheduler testsuite: pmu_test_scn07 test case failed This test failed intermittently so waived from the failed list https://bugs.linaro.org/bugzilla/show_bug.cgi?id=374 Linux kernel: ------------------ Linux version 3.10.80 (buildslave@x86-64-07-android) (gcc version 4.9.4 20150629 (prerelease) (Linaro GCC 4.9-2015.06) ) #1 SMP PREEMPT Wed Jul 22 17:21:47 CEST 2015 Android build: ------------------ http://snapshots.linaro.org/android/~linaro-android/lcr-reference-vexpress/… Test definitions: ----------------------- https://git.linaro.org/qa/test-definitions.git/blob/refs/heads/master:/comm… Test results log --------------------- https://validation.linaro.org/dashboard/streams/private/team/linaro/android… Results spread sheet: ---------------------------- https://docs.google.com/spreadsheets/d/1xbHTVSl7c7WOc-9rATQf_oSLUIhmXXgz1RX… For more information please refer results spread sheet. Best regards Naresh Kamboju

8 years, 9 months

About the memcpy optimization patch

by yfw

Hi, About the patch http://review.android.git.linaro.org/#/c/15529/, we got an issue report from member. It could improve the micro benchmark but hurt general benchmark actually. Here is their test result: bionic-benchmarks32 BM_string_memcpy: Size AOSP Linaro Perf Improvement 8 450.7 329.5 -37% 64 1715.7 2225.3 23% 512 3100.7 4253.0 27% 1K 3271.8 4652.3 30% 8K 2460.9 3174.7 22% 16K 2267.4 2953.2 23% 32K 2222.9 2800.7 21% 64K 2204.3 2640.1 17% without patch with patch perf delta Quadrant mem 3400 2100 -38% GeekBench3 single-core 436 260 -40% multi-core 434 358 -18% I am wondering whether this is an known issue or not for this list. Thanks in advance. Regards Yin, Fengwei

8 years, 9 months

RFC: Gerrit version upgrade on Linaro hosts

by Paul Sokolovsky

Hello, All Linaro Gerrit services (4 of them) currently run Gerrit 2.8.6.1, the latest of 2.8 branch, which is now 1 year old, and 3 major releases behind the latest, 2.11. We (Systems) regularly get requests regarding features available in newer Gerrit versions, and regularly face issues, which are not even reportable upstream, as we run a pretty old version. With all the improvements we did to Gerrit management across different installs lately, we're now ready to raise the question of the version upgrade. Here're basic facts about recent Gerrit versions: 1. Major change in 2.9 is introduction of new change summary screen. It's pretty different by both looks and feel and it's fair to say taht one needs to relearn Gerrit a bit with its introduction. It's still possible to use old screen, until it's removed in further versions. 2. 2.11 does remove support for old change summary screen. 3. 2.10 and 2.11 are actively supported and maintained (e.g. 2.10.6 released Jun 29, 2.11.2 - Jul, 14). Based on this, we would like to propose upgrade to 2.10, to let people some leeway to learn the new change screen, and be able to switch back to the old screen in the meantime. As usual, we'd like to select single server for pilot upgrade first, and among 4 we have, Linaro Android Gerrit, https://android-review.linaro.org seems like a good candidate, as it's used just by subset of Linaro teams, and at the same time, used regularly to call it "tested" after the pilot period. Things you can do/help with in the meantime: 1. Provide feedback on the general idea of the upgrade. 2. Let us know if you'd like a server you regularly use to be upgraded sooner rather than later. We in particular would like to know whether Android Team (and other stakeholders) agree to pilot new version on https://android-review.linaro.org 3. Get feedback from any stakeholders which may be affected, first of all, from Builds&Baselines, who run CI with Gerrit integration. 4. Get acquainted with new change screen "extramurally", by reviewing documentation with extensive screenshots: https://gerrit-documentation.storage.googleapis.com/Documentation/2.9/user-… Thanks, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

8 years, 9 months

Renaming review.android.git.linaro.org & android.git.linaro.org

by Paul Sokolovsky

Hello Android Team, For this past weekend, there was scheduled an LDAP authentication upgrade for review.android.git.linaro.org - sorry, it wasn't announced to the list, because it should be pretty transparent change, so I just got an ack from Vishal on IRC. However, the migration was postponed last-minute because new auth setup requires having SSL on review.android.git.linaro.org, and we lack it there. It's not enabled because it has pretty deep 5-level domain name, we never had such a wildcard certificate, and apparently never ordered a dedicated certificate for it. During last year or so we actually gave up many 4-level domain names, by switching to use dashes as separators instead of dots. That's more cost-effective and much easier to maintain and avoid situation with expired certificates, etc. So, what we'd like to do is migrate Android services to contemporary Linaro naming convention either. It would be: review.android.git.linaro.org -> android-review.linaro.org android.git.linaro.org -> android-git.linaro.org Note that older names will remain active and will be supported indefinitely. How it will look like, is that if you access review.android.git.linaro.org via web browser, you will be automatically redirected to android-review.linaro.org. Access via gerrit, git, ssh will work as before. Overall, the upgrade should be seamless, but as there will be several moving parts, there may be risk of something breaking for short periods of time. So, we would like to make sure that there're no concerns and that e.g. end of next week is good time to proceed. Thanks, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

8 years, 9 months

Re: RT Tests for Android

by $rik＠nth

Adding subject. On Mon, Jul 13, 2015 at 11:42 PM, $rik@nth <srikanth007m(a)gmail.com> wrote: > Hi All, > > AFAIK the current RT tests [1] doesn't have an Android.mk by default to > compile with android tool chain. > > Seems somebody would have already been tried to cross compile the current > version of rt tests to arm android. > > It would be great if someone can share the exact steps to be followed for > cross compiling. > > [1] *git*://*git*.kernel.org/pub/scm/*linux*/kernel/*git*/clrkwllms/*rt* > -tests.*git* > > -- > Thanks & Regards, > M.Srikanth Kumar. > -- Thanks & Regards, M.Srikanth Kumar.

8 years, 10 months

(no subject)

by $rik＠nth

Hi All, AFAIK the current RT tests [1] doesn't have an Android.mk by default to compile with android tool chain. Seems somebody would have already been tried to cross compile the current version of rt tests to arm android. It would be great if someone can share the exact steps to be followed for cross compiling. [1] *git*://*git*.kernel.org/pub/scm/*linux*/kernel/*git*/clrkwllms/*rt* -tests.*git* -- Thanks & Regards, M.Srikanth Kumar.

8 years, 10 months

About the local manfiest for LCR release

by yfw

Hi Vishal, I saw the local manifest git tree (ssh://git@dev-private-git.linaro.org/linaro-art/platform/manifest.git) had following comment merged: commit fc4cd0977538e46dd479a117958b8d0c6ab20017 Author: Vishal Bhoj <vishal.bhoj(a)linaro.org> Date: Sun Jul 5 11:03:22 2015 +0100 Clean up manifest to have only ART specific components Signed-off-by: Vishal Bhoj <vishal.bhoj(a)linaro.org> Change-Id: I6b066e9504a0ad0d8b137eae0f92edf53f978c85 Two questions regarding this change: 1. It make me can't download the old LCR drop like 15.06/15.05. Because it removed some projects which were included in 15.06. I need to revert this commit. 2. I saw you remove all other changes except ART. Does this mean the coming mem-lcr just inlcudes ART related changes? I also saw a new remote branch linaro-lollipop which match the old mem-lcr exactly. Should we update the the linaro_android_build_cmds.sh for old mem-lcr release so people don't need to play with local manifest for old mem-lcr downloading? Thanks. Regards Yin, Fengwei

8 years, 10 months

access to /sys/class/android_usb/ on master

by YongQin Liu

Hi, Amit I see following warnings when boot master builds, do you have any idea about such thing? [ 26.253969] init: write_file: Unable to open '/sys/class/android_usb/android0/enable': No such file or directory [ 26.253991] init: write_file: Unable to open '/sys/class/android_usb/android0/idVendor': No such file or directory [ 26.254010] init: write_file: Unable to open '/sys/class/android_usb/android0/idProduct': No such file or directory [ 26.254031] init: write_file: Unable to open '/sys/class/android_usb/android0/functions': No such file or directory [ 26.254049] init: write_file: Unable to open '/sys/class/android_usb/android0/enable': No such file or directory What's changed in master? Anything we need to update for these files access? -- Best Regards, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android

8 years, 10 months

Access to ssh://git@dev-private-git.linaro.org/linaro-art/platform/manifest.git

by yfw

Hi, I tried to download the source code of LCR 15.05 and noticed there are two type: reference-lcr member-lcr For member-lcr, I got access DENIED when clone local manifest. So my question is how can I get the access to this private git? Let me know if this is not correct place to ask this question. Thanks. Regards Yin, Fengwei

8 years, 11 months

Re: Quick hacks to reduce your code download and save disk space

by YongQin Liu

share it in linaro-android mailing list, so that others could try it and might have better options. On 9 June 2015 at 10:45, Vishal Bhoj <vishal.bhoj(a)linaro.org> wrote: > > > On 9 June 2015 at 06:46, YongQin Liu <yongqin.liu(a)linaro.org> wrote: > >> Thanks Vishal, this mail is really in time! >> >> >> On 8 June 2015 at 14:23, Vishal Bhoj <vishal.bhoj(a)linaro.org> wrote: >> >>> Hi, >>> >>> Most of you might already be knowing this. If you already have a version >>> of source say AOSP in a folder "mydroid" and you want to repo sync code >>> base from a vendor, you can do this: >>> >>> repo init -u $MANIFEST_URL --reference=<path/mydroid> >>> repo sync >>> >>> It will reuse the previous git objects and only download and store the >>> new git objects. This way a lot of space is saved. >>> >>> Another way to get code downloaded faster is: >>> >>> repo init -u $MANIFEST_URL --depth=1 >>> repo sync -jX -c >>> >>> This way it will only download the relevant branch with only last git >>> commit history of the project. Once this is done, you can do a repo init >>> with "--depth" option >>> >> here I think it should --depth=0 >> >>> and then repo sync -c for the relevant project you are interested in to >>> have the complete history of that branch. The size of .repo folder was >>> reduced to 6 GB from the original 16GB size. >>> >>> >> And we can use the group option, with "-darwin,-mips,-x86" will not >> download the toolchain binary for x86/mips, it will save us some space too. >> > +1. -notdefault can be included as well. > >> >> -- >> Best Regards, >> Yongqin Liu >> --------------------------------------------------------------- >> #mailing list >> linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> >> http://lists.linaro.org/mailman/listinfo/linaro-android >> > > -- Best Regards, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android

8 years, 11 months

← Newer
1
2
3
4
5
6
7
8
9
...
108
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-android