Hi all,
I'm working from home today. If there are any urgent lab issues, please ping me on IRC. I'll be out for about an hour some time between 12:00 and 14:00 UTC.
Thanks
Dave
Kindly review this and let me know, what to be done next?
---------- Forwarded message ----------
From: Harigopal Gollamudi <harigopal.gollamudi(a)linaro.org>
Date: 8 March 2013 14:15
Subject: Pushing to 0xbench stuff to git
To: Senthil Kumaran S <senthil.kumaran(a)linaro.org>
Hi Senthil,
how can I push 0xbench code to git? As there is one change in portion of
code for pumping the output to Stdout. This change in code can pushed to
android.git.linaro.org once it is reviewed.
please find the attached file
--
Thanks and Regards,
HariGopal G
Android Engineer
--
Thanks and Regards,
HariGopal G
Android Engineer
Hello all,
After up and running LAVA with lava-deployment-tool, I have ran wrong
command to upgrade my LAVA packages
1. Move to lava-deployment-tool
*2. *$bzr pull (this is my mistake)**
3. After then I got a following message whenever I try to upgrade
“$lava-deployment-tool upgrade <reno>
A. *“Please run './lava-deployment-tool setup' first’”*
In this situation, how to resolve this issue and upgrade easily?
Thanks, Bernard
Hi,
Release test report week-11: Here is test result summary for big.LITTLE MP
Scheduler test on TC2 platform with Android image
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 -
mpbasicsuite 10 9 9 1 90 -
mpcoresuite 4 4 4 0 75 -
mpextendedsuite 6 6 4 2 66.7 -
mploadbalance 2 2 2 0 100 -
Android Build:
https://android-build.linaro.org/builds/~linaro-android/vexpress-linaro-mp/…
Linux kernel:
Linux version 3.9.0-rc2-00306-g59074f9 (jenkins-build@ip-10-226-115-80)
(gcc version 4.7.3
20130205 (prerelease) (Linaro GCC 4.7-2013.02) ) #1 SMP Thu Mar 14
05:16:16 UTC 2013
Results spread sheet:
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0Ai9ggMs8bsGJdER3a…
summary:
- Linaro Linux kernel updated to 3.9.0-rc2
- No regression or new bugs found in this test cycle.
- Results are same as week-9.
Best regards
Naresh Kamboju
This is to let you know that the migration of lists.linaro.org has been
successfully completed.
As per the email I sent on Wednesday, it may take some time for the new
address of the server to be seen by your computer. You can check this by
trying to connect to the web site:
http://lists.linaro.org/
If you are able to connect and you do not get an error, this means you are
connecting to the new server and you can send email to the lists.
If you experience any problems after the weekend and you find that you
still cannot connect to the server, please reply to this email to let us
know.
Regards
Philip
IT Services Manager
Linaro
Hi guys,
Are there any plans to deploy a fresher version lava-android-test? When can
we expect it to happen next? (the currently deployed version is about a
month old I think)
There are a number of tests which have been developed for juice, (with
corresponding wrappers added to lava-android-test). We would like to verify
that we get the same results in automation as we get when running manually
but are unable to do that until we get a fresher version of
lava-android-test deployed.
BR,
Axel
Hello
You are receiving this email because you are subscribed to one or more
mailing lists provided by the lists.linaro.org server.
IT Services are announcing planned maintenance for this server scheduled
for *Friday 15th March 2013, starting at 2pm GMT*. The purpose of the work
is to move the service to another server. There will be some disruption
during this maintenance.
In order to ensure that you do not accidentally try to use the service
while it is being moved, the current server will be shut down at 2pm.
A further email will be sent on Friday afternoon to confirm that the
migration of the service is completed. However, due to the way servers are
found, it may take a while before your computer is able to connect to the
relocated service.
After the old server has been shut down, email sent to any of the lists
will be queued, but it is possible that the sending server will still
trying to deliver the email to the old server rather than the new one when
it is started.
It is therefore *strongly* recommended that you do not send any email to an
@lists.linaro.org email address until you can connect to the new service,
which you will be able to test by trying to use a web browser to connect to
http://lists.linaro.org after you receive the email confirming that the
migration has been completed. Since the old service will be shut down, if
you are able to connect, you can be sure you have connected to the new
service.
If by Monday you are still unable to connect to the service or you are not
able to send email to an @lists.linaro.org email address, please send an
email to its(a)linaro.org.
Thank you.
Regards
Philip
IT Services Manager
Linaro
Hi all
I want to write/run a test-shell locally,and upload to the dashboard
finally.
Because I want to test locally so I think I just need to handle two
components: lava-test-shell and lava-dashboard.
1. lava-test-shell
My test-script is a python base program and want to executing standalone.
In old way (lava-test), I can use lava-test to call my test program without
deploy any image.
But lava-test is in processing of being deprecated if favor of using
lava-test-shell.
The new way (lava-test-shell) seems not support test standalone yet? (or
not intend to support?)
So should I writing my custom test script without lava-test
(lava-test-shell) and upload to the lava-dashboard directly ?
2. lava-dashboard
Inherited the problem before (point 1.),
Maybe I should write my test script without lava-test (lava-test-shell),
and upload lava-dashboard directly.
But how to do that?
If in the way to use lava-test or a job of lava-scheduler, it can
be submitted.
But can I upload test case (or test result) just using my own test script?
The lava-dashboard document unfinished so I have no idea about that:
http://lava-dashboard.readthedocs.org/en/latest/usage.html#usage
anyone helps ? :-)
thanks.