Hey
Today I've noticed that my panda 'tests' builds are failing, a quick
chat with bhoj later I knew about the new kernel and updated my 'tests'
configuration to build properly.
Now I've noticed that snowball builds differ vs non-tests variant (they
didn't build properly) so after eyeballing both configurations I've
updated mine to match again.
Is there a way to request being notified whenever configuration is changed?
Alternatively, could you please me in CC when that happens so that I can
keep track of my builds. Thanks
--
Zygmunt Krynicki
Linaro Validation Team
s/Validation/Android/
Hey everyone!
As per blueprint:
https://blueprints.launchpad.net/linaro-android/+spec/build-tests
I'd like to switch our official builds to use TARGET_BUILD_VARIANT=tests
I'd like to make the change on *Friday* (29th).
During the rest of the month I'll assist in fixing any issues that we
end up discovering in practice. I've compiled a quick list of things
that seem to be affected by this here:
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgiculnRh94adFY1T…
There are a few things that raise concern but they will be all gone by
the time we do the switch.
If you have any concerns or questions now is the time to voice them!
Thanks for your attention
ZK
--
Zygmunt Krynicki
Linaro Validation Team
s/Validation/Android/
Hi,
We have recently updated our panda builds due to which the instructions on
building the sources have changed a little:
tracking-panda.xml based build is now update to pick 3.4 tilt-tracking
kernel and currently doesn't have hw accelerated graphics and hence the
graphics binaries need not be installed (skip running
install-binaries-4.0.4.sh) .
You need to export these parameters before triggering the build:
export TARGET_NO_HARDWAREGFX=1
export KERNEL_CONFIG=omap4plus_defconfig
Here is the update build:
https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-til…
The staging-panda.xml manifest has been updated to track the 3.2 kernel
which was previously used in tracking-panda builds. This build would now
need the graphics binaries (Run install-binaries-4.0.4.sh ) after creating
the sdcard. This build would have the features/bugs of previous
tracking-panda builds:
https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-til…
Regards,
Vishal
Hey everyone.
I found that my snowball builds fail on this problem:
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: ***
[out/target/product/snowball/obj/SHARED_LIBRARIES/libskia_intermediates/src/opts/SkBlitRow_opts_arm.o]
Error 1
Full log is available at
https://android-build.linaro.org/jenkins/job/zkrynicki_snowball-ics-gcc46-i…
Bero mentioned that 4.7 has this particular error fixed, shall I open a
bug on 4.6 somehow?
Thanks for the advice
ZK
--
Zygmunt Krynicki
Linaro Validation Team
s/Validation/Android/
FYI
---------- Forwarded message ----------
From: Jean-Baptiste Queru <jbq(a)android.com>
Date: 21 June 2012 12:22
Subject: Contributing to dalvik/libcore: small changes
To: android-contrib(a)googlegroups.com
We're slightly changing the way we manage some branches, please note
the following changes in the way contributions now work in the dalvik
and libcore projects:
-New contributions to those projects need to be prepared in the
master-dalvik branch. The master branch (and other active development
branches) use a frozen snapshot of those projects, on top of which we
can't accept contributions.
-Existing contributions to those projects (i.e. that have been
uploaded) need no further action.
-If you have a master client, you can switch to master-dalvik with
"repo init -b master-dalvik ; repo sync".
-Technically, you can use master-dalvik to contribute to any project,
but that's not recommended. Unless you're explicitly contributing to
dalvik or libcore, please use the plain master branch to prepare your
contributions.
-Note that, since the master branch uses a frozen snapshot, changes
contributed to the dalvik and libcore projects in master-dalvik don't
get reflected in master.
-This does not affect tagged releases, those will continue to be
managed as usual.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
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
Hello everyone,
the Infrastructure Team is going to deploy a new version of the
android-build frontend, in order to address bug #1015651.
We are planning to deploy it today (June 21st) at 12UTC, and the
deployment shouldn't take more than 10 minutes.
Only the frontend will be affected.
If the downtime will cause you significant problems, please get in
touch with us.
Thanks.
--
Milo Casagrande
Infrastructure Engineer
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs