Linaro-android March 2012

linaro-android@lists.linaro.org

52 participants
56 discussions

tilt-linaro-android-3.1 branch on linaro github

by C.A, Subramaniam

Hi All, I see that the linaro branch tilt-linaro-android-3.1 is not available in this tree (git://git.linaro.org/landing-teams/working/ti/kernel.git ). The branch name is the one mentioned under linaro-android- + Panda enablement. Is there an alternate branch that can be used? or should I just use the tilt-linaro-android-3.0? -- Thank you and Regards Subbu

13 years, 10 months

Agenda posted to https://wiki.linaro.org/Platform/Android/Meetings/2012-03-28

by Zach Pfeffer

Feel free to add to it and please add your status. -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams 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

13 years, 10 months

Brave 12.03 testers, a call to action

by Zach Pfeffer

Here are our bold volunteers! Annamalai https://android-build.linaro.org/builds/~linaro-android/origen-ics-gcc46-sa… Bero https://android-build.linaro.org/builds/~linaro-android/imx6-ics-gcc46-free… https://android-build.linaro.org/builds/~linaro-android/imx6-ics-gcc47-free… Mathieu https://android-build.linaro.org/builds/~linaro-android/snowball-ics-gcc46-… Abhishek https://android-build.linaro.org/builds/~linaro-android/vexpress-ics-gcc46-… Botao https://android-build.linaro.org/builds/~linaro-android/imx53-ics-gcc46-fre… Vishal 4460 Chenglie 4430 https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc46-til… (4430 and 4460) https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc46-til… (4430 and 4460) https://android-build.linaro.org/builds/~linaro-android/panda-master-gcc44-… (4430 and 4460) Amber 4430, Tony 4460 https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc44-kwg… (4430 and 4460) https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc46-kwg… (4430 and 4460) <clap> <clap> <clap> <clap> <clap> <clap> Here's the process: Abhishek will cut the builds on Monday 3/26, India Morning. He will boottest each tip. Please watch email or IRC in case he needs some help. After the builds are done he will enter the released build to test into the test spreadsheets (build row) listed here. Please test this build exactly. __Test Spreadsheets__ iMX53, iMX6 https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadDE1M… Snowball https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadEF1N… Origen https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadDRDV… Panda https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… Vexpress https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… __Process__ STarting on Tuesday, please program the builds and boot um up. The tests are documented at the "Test Description" link on each test sheet. Run through the tests starting with tests that were red in the last release, then tests that were yellow, then the rest and enter in the new results in the spreadsheet in the right column. In this case r12.03. It'll be the column with the build listed in the build row. note which tab you're on. You should see the build name. Also make sure you put the kernel and toolchain that the build is run against. and the build number. Also, and this is new from last time, look at all the bugs in the linaro-android project in launchpad that are marked Fix Committed and if they're fixed, mark them Fix Released with the build you tested. If they're not, please update the bug and set it back to In Progress. When you run into a new issue, please file a bug with the test that was run and the build that it was tested on. For existing issues, please update the bug with the build link that was tested, with a note, "still an issue on http://....#123," etc. If you have any questons, call, email or IRC me. -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams 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

13 years, 10 months

Please report status

by Tony Mansson

Hello Android Team. Please update your status at https://wiki.linaro.org/Platform/Android/Meetings/2012-03-28 Would you also make sure your BPs are updated. We need to describe the release as accurately as possible already today, so Work Items must have the status that corresponds to the release builds. Use the comment section to explain further if you need to. BR, Tony

13 years, 10 months

Hiding RC candidate columns

by Zach Pfeffer

Team, Would you "hide" RC candidate columns in your test sheets (select the columns, then right click on the selection and select hide). It visually easier to see the enablement evolution. -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams 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

13 years, 10 months

[build does not go thru]

by Aditya Podila

Hi Linaro team, I have followed the the instructions given in https://wiki.linaro.org/Platform/Android/BuildSource site And i see that my build does not go thru. In the sense "make" stops and exists with out any error find the build log attaches with the mail, please guide me through. Regards Aditya Aptina India Private Limited / Frontline Grandeur, 14 Walton Road, Bangalore - 560001, India This e-mail and any attachments contain confidential information and are solely for the review and use of the intended recipient. If you have received this e-mail in error, please notify the sender and destroy this e-mail and any copies.

13 years, 10 months

[Boot stop]

by Aditya Podila

Hi Linaro, Following is my setup. Repo used --------- repo init -u git://android.git.linaro.org/platform/manifest.git -b linaro_android_4.0.3 -m staging-panda.xml Tool chain used --------------- Android prebuilt tool chain is used and location in the repo is /prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/ Make Command ------------- make TARGET_PRODUCT=pandaboard TARGET_TOOLS_PREFIX=./prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/arm-linux-androideabi- boottarball systemtarball userdatatarball Preparing the SDCard --------------------- linaro-android-media-create --mmc /dev/sdb --dev panda --system out/target/product/pandaboard/system.tar.bz2 --userdata out/target/product/pandaboard/userdata.tar.bz2 --boot out/target/product/pandaboard/boot.tar.bz2 I am facing the problem when i placed sdcard and started the panda board. It stops with "Uncompressing Linux... done, booting the kernel." Any help would be well come. Minicom Log -----------U-Boot 2011.12-00001-g8df5795 (Mar 27 2012 - 03:35:53) Texas Instruments OMAP4430 ES2.1 Bypassing DPLL failed 4a008180 OMAP SD/MMC: 0 reading u-boot.img reading u-boot.img CPU : OMAP4430 ES2.1 Board: OMAP4 Panda I2C: ready DRAM: 1 GiB WARNING: Caches not enabled MMC: OMAP SD/MMC: 0 Using default environment In: serial Out: serial Err: serial Net: No ethernet found. checking for preEnv.txt reading preEnv.txt ** Unable to read "preEnv.txt" from mmc 0:1 ** Hit any key to stop autoboot: 0 reading uEnv.txt ** Unable to read "uEnv.txt" from mmc 0:1 ** reading boot.scr 449 bytes read Loaded script from boot.scr Running bootscript from mmc0 ... ## Executing script at 82000000 reading uImage 4586988 bytes read reading uInitrd 216182 bytes read ## Booting kernel from Legacy Image at 80200000 ... Image Name: Linux-3.1.0+ Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4586924 Bytes = 4.4 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 81600000 ... Image Name: Android Ramdisk Image Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 216118 Bytes = 211.1 KiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Aptina India Private Limited / Frontline Grandeur, 14 Walton Road, Bangalore - 560001, India This e-mail and any attachments contain confidential information and are solely for the review and use of the intended recipient. If you have received this e-mail in error, please notify the sender and destroy this e-mail and any copies.

13 years, 10 months

Daily/Weekly/Monthly Android Testing

by Zach Pfeffer

I've clarified what should be tested daily/weekly/monthly on Android builds. Take a look at: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadHpDR… I've marked tests with a d and w for daily and weekly. Anything without a mark will be done during the QA cycle. As always the test descriptions can be found from a link on the test spreadsheets. __Test Spreadsheets__ iMX53, iMX6 https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadDE1M… Snowball https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadEF1N… Origen https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadDRDV… Panda https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… Vexpress https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams 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

13 years, 10 months

About the interface on android-build on the support of android command for LAVA

by YongQin Liu

Hi, All Now lava can support to specify android commands in the job file directly, and this makes it necessary for us to discuss the interface on android-build page that used to generate the expected lava job files. I have written some description about this interface on the wiki: https://wiki.linaro.org/Platform/Android/AndroidBuild-LavaIntegration The BP is https://blueprints.launchpad.net/lava-android-test/+spec/modify-android-bui…, and pfalcon has already given some comments there. You can see that for your reference. And here I want to get more feedback from you about it to make it more convenient for us to use. Please give me your comments. BRs, Yongqin Liu

13 years, 10 months

Re: [rt.linaro.org #363] android-build jenkins only looks like it can use one builder

by Paul Sokolovsky

Hello, On Sat, 24 Mar 2012 12:12:15 +0200 Fathi Boudra <fathi.boudra(a)linaro.org> wrote: > On 23 March 2012 21:26, Zach Pfeffer via RT <rt(a)linaro.org> wrote: > > > > Fri Mar 23 19:26:01 2012: Request 363 was acted upon. > > Transaction: Ticket created by zach.pfeffer(a)linaro.org > > Queue: [T] Linaro > > Subject: android-build jenkins only looks like it can use one > > builder Owner: Nobody > > Requestors: zach.pfeffer(a)linaro.org > > Status: new > > Ticket <URL: https://rt.linaro.org//Ticket/Display.html?id=363 > > > > > Would someone take a look? Mathieu is saying Jenkins can only use > > one builder. > > Situation is back to normal ~2h after the ticket was submitted. Well, actually I did some actions after 10 mins after seeing that info on IRC. > Closing. For reference, IS isn't in charge of this service. > > Please, report a bug on Linaro Android Infrastructure for > investigation: > https://bugs.launchpad.net/linaro-android-infrastructure/+filebug +1. Information Services (IS) should be contacted directly only on selected limited number of questions, like recent case of updating a file http://snapshots.linaro.org/android/binaries/ in, where Infra team doesn't access. The rest is still handled by Infra team by that link. Such discrepancy in procedures may seem counterintuitive, and I used to see it such, and did some noise about that yet on Connect Q4.11, Danilo can prove ;-). In the end it was decided that responsibility separation is good, and we won't get around it anyway, as Linaro consists of many different teams. > > Note: we have an instance cap limit shared between android-build.l.o > and ci.l.o, set to 20. If the builds have been queued on > android-build.l.o and 19 instances are already taken by ci.l.o, only > one instance is remaining for a-b. That's true. And recently we had: 1) more permanent instances added to runs services (9 total); 2) cases of zombie instances due to ci.linaro.org issues (wild suspicion is that it still happens, I'll be watching it closely). So, we actually had/have some instance scarcity these days. I however did audit of all running instances yesterday, and caught few more ci.linaro.org-forgotten instances. So, we should be better now. There's also discussion of increasing our global EC2 instance limit (that should be possible, but I imagine may require some paperwork with Amazon). > > Cheers, > > Fathi -- Best Regards, 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

13 years, 10 months

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-android March 2012