Hello,
Per https://cards.linaro.org/browse/SYS-354 , Jenkins was upgraded to
1.580.2 and EC2 plugin to 1.24 (which is worth mentioning, as
previously we held EC2 plugin version at 1.18).
Upgrade was tested on android-build.linaro.org clone, then on
android-build itself, and over the weekend, ci.linaro.org and
tcwg-ci.linaro.org followed.
The only regression with this upgrade is related to visual UI - in
1.580, Jenkins switched to a new theme, which is not compatible with
existing Linaro theme, and Linaro theme actually causes some UI
elements to be not available on new Jenkins version. So, it was
disabled on all servers, we will look into updating Linaro theme at
later time.
Otherwise, I didn't see any build failure which can be attributed to
the upgrade. In particular, EC2 slave provision works as expected and
reliably with the new plugin.
But please let me and Andy Doan know if you see any issue or have any
question.
Thanks, and Happy New Year!
--
Best Regards,
Paul
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
"Any technology that does not appear magical is insufficiently advanced."
~ Gregory Benford
Linaro is pleased to announce the first Linaro Confectionery Release (LCR).
LCR is a reference build of the Android-5.0.1_r1 branch for ARM’s Juno and
Versatile Express TC2 hardware, and Fixed Virtual Platform (FVP) models.
The goal of LCR is to provides a foundation for tested Linaro engineering
efforts integrated with Android point releases. Only engineering efforts
which have an established validation record are allowed to be added to LCR.
LCR is conceptually similar to the Linaro Stable Kernel (LSK) project which
uses Greg Kroah-Hartman’s Long Term Stable (LTS) source tree with Linaro
members features added. LCR charts a comparable course that starts with
Android point releases and includes Linaro member directed engineering
to fix, optimize and enhance LCR.
For 14.12, LCR uses the Android AOSP 4.9 GCC toolchain for building 64bit
ARM binaries and the Android AOSP 4.8 GCC toolchain for building 32bit ARM
binaries.
LCR includes the 3.10 Android flavour of LSK for all 3 currently supported
configurations. This means that the LSK includes Android kernel patches from
the AOSP project. The Juno kernel includes ARM Mali drivers for accelerated 3D
graphics support.
LCR includes support for both single-arch 32bit ARMv7-A and multi-arch 32bit
ARMv7-A, 64bit ARMv8-A Android systems.
LCR is tested. CTS version 5.0, Android BIONIC tests, Android Monkey and other
tests are used to validate the system. Testing performed should not be
considered to exhaustive or necessarily product quality. Test results are
available to Linaro member companies.
The release can be found respectively at:
* Juno: http://releases.linaro.org/14.12/android/lcr/juno
* FVP: http://releases.linaro.org/14.12/android/lcr/fvp
* Versatile Express TC2:
http://releases.linaro.org/14.12/android/lcr/vexpress-tc2
If you should find a issue or have a question about the release, we invite you
to use one of the following mechanisms:
* IRC: irc.freenode.net - #linaro-android
* email: linaro-android(a)lists.linaro.org
* Bug Tracking System: Linaro Android project/Linaro Confectionary
release component
(https://bugs.linaro.org/enter_bug.cgi?product=Linaro%20Android)
Support is on a “best effort” basis.
--
Fathi Boudra, on behalf of the LMG/Android Team and Release Team
Linaro.org | Open source software for ARM SoCs
Hi,
Good afternoon from Tokyo.
I am working with Pandaboard and looking for android-5(Lollipop) for
Pandaboard.
By googling I got that, Pandaboard android support is provided by Linaro.
But there is not any android-5(Lollipop) release available for Pandaboard
in Linaro site.
So, could you please let me know
1) When Linaro will provide android-5(Lolipop) release for Pandaboard.
2) Is there any plan to stop supporting for Pandaboard.
3) What is the highest priority board for Linaro to provide latest release
of Android.
Thanks in advance.
Best Regards,
Imran
Hi,
I want to know how to do the following tests using LAVA testing tools.
1. Memory Leak detection
2. Unit test
3. Performance Test
4. Integration test
5. System test
6. regression test
7. Stress test
8. Test case
9. Simulation of user inputs
10. Power moding test
11. Event injection
12. Benchmarking
I found a ling which tells about what some of the above tests are but they
have not mentioned how to run those test. Can any help us how to run above
tests. We are new to this LAVA testing please provide us what to install
also for running these tests.
--
[image: tree pine]Please consider the environment before printing this
e-mail
Thanks & Regards
Narendra Kumar Chepuri
(+917353049544)
Hi,
I am checking with linaro-validation and linaro-android mailing list to
see if anyone is
still using the outdated dalvik-vm-unit test.
https://git.linaro.org/qa/test-definitions.git/blob/HEAD:/android/dalvik-vm…
Since dalvik is not used any more and dalvik-vm-unit-tests is not in the
aosp source any more, I'm planning to delete it from qa/testdefinition repo
by the end of next week if there aren't any objections :)
--
Regards,
Amit Khare
Hello,
We've been readying new publishing API for some time now, and last
week, I finished largest part of integration testing for
android-build.linaro.org. The things looks good, and to remind, new
publishing API will improve performance, security, and maintainability
of the publishing.
What's left on critical path to deployment are:
1. Resolving disk space problems on snapshots.linaro.org (which got
on brink of overflow last week) - we'll be looking into this with ITS.
2. Preparing job migration scripts - in works by me.
3. Merging changes made in dew linaro-android-build-tools forks repos
- Vishal works on this.
So, with this mail, I'd like to call for final sync on these tasks, and
schedule switchover for this week.
Please let me know how that sounds and if there're any blockers to that.
Thanks,
Paul
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Hi,
we finally have post-L-merge AOSP master building with clang for both ARMv7
and ARMv8, and all related patches are submitted upstream.
Now we just need to make sure we can fix things faster than upstream
updates break them ;)
I haven't had any success booting it yet (but the last images just finished
compiling...), but I suspect some recent upstream changes (move to C++11
etc.) may have broken master for a bit and a gcc built version won't work
either. That's the first thing I'll check tomorrow.
ttyl
bero