We've got some RC builds available to test:
Android Panda LEB https://android-build.linaro.org/builds/~patrik-ryd/dev1106lebp/
Android Generic Panda https://android-build.linaro.org/builds/~patrik-ryd/dev1106genericp/
Beagle does not boot.
I have attached a little script that makes this easy. Go to the build page and copy the start of the boot image's URL. Plug in an SD card and the serial terminal and run:
trybuild.sh https://android-build.linaro.org/jenkins/job/patrik-ryd_dev1106lebp/6/artifa... /dev/sdd
Once its done it'll drop you into a minicom session.
For those who test would you mind updating:
https://bugs.launchpad.net/bugs/803014 with the type of monitor you used? The build works with some monitors, but not others.
Paul,
Would you manually test these in validation?
Fathi,
Please copy these builds as the rc. There's no beagle board build since it doesn't boot.
-Zach
On Tue, Jun 28, 2011 at 8:26 PM, Zach Pfeffer zach.pfeffer@linaro.orgwrote:
We've got some RC builds available to test:
Android Panda LEB https://android-build.linaro.org/builds/~patrik-ryd/dev1106lebp/
This one seems to be taking a very long time to complete... I think it's stuck. Here's a partial from the log. [1] It will eventually timeout and dump the entire serial log, which you will see linked to a test result at: http://validation.linaro.org/launch-control/dashboard/reports/android-runs/
Android Generic Panda https://android-build.linaro.org/builds/~patrik-ryd/dev1106genericp/
This one worked fine, here are the the results with serial log: http://validation.linaro.org/launch-control/dashboard/test-runs/3803dae8-a1b... ...And the detailed results which even got parsed with this kernel! http://validation.linaro.org/launch-control/dashboard/test-runs/bba4300f-316...
Thanks, Paul Larson
[1] - graphics H/W... E/SurfaceFlinger( 4562): Couldn't open /sys/power/wait_for_fb_sleep or /sys/power/wait_for_fb_wake E/FramebufferNativeWindow( 4562): couldn't open framebuffer HAL (No such device) I/DEBUG ( 1097): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** I/DEBUG ( 1097): Build fingerprint: 'pandaboard/pandaboard/pandaboard:2.3.4/GRJ22/6:eng/test-keys' I/DEBUG ( 1097): pid: 4562, tid: 4570 >>> system_server <<< I/DEBUG ( 1097): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000005c I/DEBUG ( 1097): r0 0008f610 r1 435b9dcc r2 00000000 r3 00000000 I/DEBUG ( 1097): r4 0008f5c8 r5 801499f4 r6 00000000 r7 0008f728 I/DEBUG ( 1097): r8 0000053c r9 001938c8 10 00100000 fp 00000001 I/DEBUG ( 1097): ip 8352f7d4 sp 435b9d70 lr 804048f8 pc 8351cd3c cpsr 60000130 I/DEBUG ( 1097): d0 2068637573206f64 d1 4148207265666665 I/DEBUG ( 1097): d2 6e2c000000000076 d3 0700000400000069 I/DEBUG ( 1097): d4 0000000707000004 d5 004ff0000f400000 I/DEBUG ( 1097): d6 0000000002014200 d7 0000000807000005 I/DEBUG ( 1097): d8 0000000000000000 d9 0000000000000000 I/DEBUG ( 1097): d10 0000000000000000 d11 0000000000000000 I/DEBUG ( 1097): d12 0000000000000000 d13 0000000000000000 I/DEBUG ( 1097): d14 0000000000000000 d15 0000000000000000 I/DEBUG ( 1097): d16 3fe99999a0000000 d17 3fe999999999999a I/DEBUG ( 1097): d18 40cdf60000000000 d19 3fcef049fb9094d1 I/DEBUG ( 1097): d20 3f8948b0fcd6e9e0 d21 3fe555b0aaeac752 I/DEBUG ( 1097): d22 4008000000000000 d23 3fcc7288e957b53b I/DEBUG ( 1097): d24 3fc74721cad6b0ed d25 3fc39a09d078c69f I/DEBUG ( 1097): d26 0000000000000000 d27 0000000000000000 I/DEBUG ( 1097): d28 0000000000000000 d29 0000000000000000 I/DEBUG ( 1097): d30 0000000000000000 d31 0000000000000000 I/DEBUG ( 1097): scr 20000012 I/DEBUG ( 1097): I/DEBUG ( 1097): #00 pc 0001cd3c /system/lib/libsurfaceflinger.so I/DEBUG ( 1097): #01 pc 0001d210 /system/lib/libsurfaceflinger.so I/DEBUG ( 1097): #02 pc 00024c7a /system/lib/libsurfaceflinger.so I/DEBUG ( 1097): #03 pc 0001f28c /system/lib/libutils.so I/DEBUG ( 1097): #04 pc 0001ee74 /system/lib/libutils.so I/DEBUG ( 1097): #05 pc 0000cf38 /system/lib/libc.so I/DEBUG ( 1097): #06 pc 0000ca8c /system/lib/libc.so I/DEBUG ( 1097): I/DEBUG ( 1097): code around pc: I/DEBUG ( 1097): 8351cd1c f7fe4606 4631edba 0048f104 ffbbf7ff I/DEBUG ( 1097): 8351cd2c 23006ca7 6efe6afa 6b3961e2 a9176221 I/DEBUG ( 1097): 8351cd3c 64e36df0 f8df6260 44780434 eafaf7fe I/DEBUG ( 1097): 8351cd4c b9409507 f1049817 6941024c f8df680d I/DEBUG ( 1097): 8351cd5c 44791420 f8df47a8 ad09e41c 97152700 I/DEBUG ( 1097): I/DEBUG ( 1097): code around lr: I/DEBUG ( 1097): 804048d8 1afffffb ebffffcc e1a00004 e8bd8010 I/DEBUG ( 1097): 804048e8 e92d4038 e1a04000 e1a05001 ebffffc6 I/DEBUG ( 1097): 804048f8 e1950f9f e0802004 e1853f92 e3530000 I/DEBUG ( 1097): 80404908 1afffffa e8bd8038 e1a01000 e3a00001 I/DEBUG ( 1097): 80404918 eafffff2 [ 863.444671] init: untracked pid 4554 exited e1a01000 e3e0000[ 863.450347] init: untracked pid 4553 exited 0 eaffffef I/DEBUG ( 1097): I/DEBUG ( 1097): stack: I/DEBUG ( 1097): 435b9d30 000000a3 I/DEBUG ( 1097): 435b9d34 0008f728 I/DEBUG ( 1097): 435b9d38 00000250 I/DEBUG ( 1097): 435b9d3c 0000023c I/DEBUG ( 1097): 435b9d40 0000053c I/DEBUG ( 1097): 435b9d44 843031ec I/DEBUG ( 1097): 435b9d48 8010f045 /system/lib/libc.so I/DEBUG ( 1097): 435b9d4c 0008f5c8 I/DEBUG ( 1097): 435b9d50 00000000 I/DEBUG ( 1097): 435b9d54 0008f610 I/DEBUG ( 1097): 435b9d58 0008f728 I/DEBUG ( 1097): 435b9d5c 8351ccb3 /system/lib/libsurfaceflinger.so I/DEBUG ( 1097): 435b9d60 00000000 I/DEBUG ( 1097): 435b9d64 0008f5c8 I/DEBUG ( 1097): 435b9d68 df002777 I/DEBUG ( 1097): 435b9d6c e3a070ad I/DEBUG ( 1097): #00 435b9d70 8010f045 /system/lib/libc.so I/DEBUG ( 1097): 435b9d74 435b9dd4 I/DEBUG ( 1097): 435b9d78 00000000 I/DEBUG ( 1097): 435b9d7c 00001000 I/DEBUG ( 1097): 435b9d80 83528f3a /system/lib/libsurfaceflinger.so I/DEBUG ( 1097): 435b9d84 8051eded /system/lib/libutils.so I/DEBUG ( 1097): 435b9d88 fffffff8 I/DEBUG ( 1097): 435b9d8c 001938c8 I/DEBUG ( 1097): 435b9d90 00000000 I/DEBUG ( 1097): 435b9d94 0008f6c8 I/DEBUG ( 1097): 435b9d98 00000000 I/DEBUG ( 1097): 435b9d9c 001938c8 I/DEBUG ( 1097): 435b9da0 00000001 I/DEBUG ( 1097): 435b9da4 8051ed17 /system/lib/libutils.so I/DEBUG ( 1097): 435b9da8 8352c0fc /system/lib/libsurfaceflinger.so I/DEBUG ( 1097): 435b9dac 805180ef /system/lib/libutils.so I/DEBUG ( 1097): 435b9db0 0008f6c0 I/DEBUG ( 1097): 435b9db4 801499f4 I/DEBUG ( 1097): 435b9db8 00000018 I/DEBUG ( 1097): 435b9dbc 00000001 I/DEBUG ( 1097): 435b9dc0 00000000 I/DEBUG ( 1097): 435b9dc4 00100000 I/DEBUG ( 1097): 435b9dc8 00001000 I/DEBUG ( 1097): 435b9dcc 00000000 I/DEBUG ( 1097): 435b9dd0 00000000 I/DEBUG ( 1097): 435b9dd4 0008f680 I/DEBUG ( 1097): 435b9dd8 0008f188 I/DEBUG ( 1097): 435b9ddc 0008f620 I/DEBUG ( 1097): 435b9de0 0008f570 I/DEBUG ( 1097): 435b9de4 0008f620 I/DEBUG ( 1097): 435b9de8 0008f218 I/DEBUG ( 1097): 435b9dec 0008f5c8 I/DEBUG ( 1097): 435b9df0 001938c8
http://validation.linaro.org/launch-control/dashboard/attachments/2755/
Tested on the released panda-leb version, here's the serial log showing the same errors I mentioned in the previous results? Is this a known problem?
Yeah. Those results seem rational. Would you test:
https://android-build.linaro.org/builds/~linaro-android/panda-11.06-release/...
https://android-build.linaro.org/builds/~linaro-android/leb-panda-11.06-rele...
https://android-build.linaro.org/builds/~linaro-android/beagle-11.06-release...
...and update the build note on each page with the validation results?
Here's how to update the description from Paul Sokolovsky:
1. Make sure you're registered with Jenkins: https://android-build.linaro.org/jenkins/people/ 2. If you aren't, sign up at https://android-build.linaro.org/jenkins/signup and let me know your username, so I can give you appropriate permissions (Zach, this point is for you) 3. Browse to needed job from Jenkins frontpage: https://android-build.linaro.org/jenkins/ 4. Once you at job's page (e.g. https://android-build.linaro.org/jenkins/job/linaro-android_beagle/), click "add description"/"edit description" in the top right corner, and edit the description. Full HTML is allowed. 5. Click Submit and see if it looks OK. Repeat editing if needed. Otherwise, the description is immediately available at frontend's page for the job. (Though for your own browser, you sometime need to Ctrl+R it to refresh cache).
Please add the validation stuff to the bottom.
Would you do this for all validation results from builds we manual request tested from here on out?
-Zach
On 30 June 2011 17:37, Paul Larson paul.larson@linaro.org wrote:
http://validation.linaro.org/launch-control/dashboard/attachments/2755/ Tested on the released panda-leb version, here's the serial log showing the same errors I mentioned in the previous results? Is this a known problem?
On Sun, Jul 3, 2011 at 9:13 PM, Zach Pfeffer zach.pfeffer@linaro.orgwrote:
Yeah. Those results seem rational. Would you test:
https://android-build.linaro.org/builds/~linaro-android/panda-11.06-release/...
This one is currently running
https://android-build.linaro.org/builds/~linaro-android/leb-panda-11.06-rele...
This one is identical to the above
https://android-build.linaro.org/builds/~linaro-android/beagle-11.06-release...
This one is complete, results can be easily found at the usual place based on the url: http://validation.linaro.org/launch-control/dashboard/reports/android-runs/
...and update the build note on each page with the validation results?
What is this build note and where is it displayed?
Here's how to update the description from Paul Sokolovsky:
- Make sure you're registered with Jenkins:
https://android-build.linaro.org/jenkins/people/ 2. If you aren't, sign up at https://android-build.linaro.org/jenkins/signup and let me know your username, so I can give you appropriate permissions (Zach, this point is for you) 3. Browse to needed job from Jenkins frontpage: https://android-build.linaro.org/jenkins/ 4. Once you at job's page (e.g. https://android-build.linaro.org/jenkins/job/linaro-android_beagle/), click "add description"/"edit description" in the top right corner, and edit the description. Full HTML is allowed. 5. Click Submit and see if it looks OK. Repeat editing if needed. Otherwise, the description is immediately available at frontend's page for the job. (Though for your own browser, you sometime need to Ctrl+R it to refresh cache).
Is there an easier way of doing this? I don't think anyone wants to be doing this for every single test. Our goal was to automate this, so we really need a way to link the results back in some automated fashion, or they need to just be searched by the person looking for them.
Please add the validation stuff to the bottom.
I held off on this for the time being, pending the answer to my question above. This appeared to be a pretty generic place associated with the whole build, not that specific build id. Is there a better place to add it?
Would you do this for all validation results from builds we manual request tested from here on out?
If it's one or two a month, sure. Or better yet, we'll soon be able to let you schedule your own jobs. We're deploying the new lava-server/lava-dashboard this week, and on top of that will be the scheduler as well. This would enable you to kick off your own jobs for one-offs like this.
Thanks, Paul Larson
On Mon, 4 Jul 2011 12:29:19 -0500 Paul Larson paul.larson@linaro.org wrote:
[]
Is there an easier way of doing this? I don't think anyone wants to be doing this for every single test. Our goal was to automate this, so we really need a way to link the results back in some automated fashion, or they need to just be searched by the person looking for them.
My idea was that LAVA will be our CI Central. I.e., if one wants just builds, one would look at android-build, but if one wants all info at all, and validation results in particular, one would look into LAVA. Is that viable idea at all?
On Mon, Jul 4, 2011 at 12:34 PM, Paul Sokolovsky <paul.sokolovsky@linaro.org
wrote:
On Mon, 4 Jul 2011 12:29:19 -0500 Paul Larson paul.larson@linaro.org wrote:
[]
Is there an easier way of doing this? I don't think anyone wants to be doing this for every single test. Our goal was to automate this, so we really need a way to link the results back in some automated fashion, or they need to just be searched by the person looking for them.
My idea was that LAVA will be our CI Central. I.e., if one wants just builds, one would look at android-build, but if one wants all info at all, and validation results in particular, one would look into LAVA. Is that viable idea at all?
But LAVA doesn't have information about the builds. So it seems to me we want to somehow get that information back to the location that does have information about the builds -or- make it easy for people to find results for the build they care about. Can you give more detail about what you are suggesting?
Thanks, Paul Larson
Hello Paul,
On Mon, 4 Jul 2011 12:54:04 -0500 Paul Larson paul.larson@linaro.org wrote:
[]
My idea was that LAVA will be our CI Central. I.e., if one wants just builds, one would look at android-build, but if one wants all info at all, and validation results in particular, one would look into LAVA. Is that viable idea at all?
But LAVA doesn't have information about the builds. So it seems to me we want to somehow get that information back to the location that does have information about the builds -or- make it easy for people to find results for the build they care about. Can you give more detail about what you are suggesting?
Well, but LAVA would get at least minimal information about the build, and as soon as it gets at least build type, build name, and build URL, it can show report like:
------------------------------------------------------------- | Type | Build Name | Results | | Android | ~linaro-android/leb-panda #100 | 10 pass/4 fail | -------------------------------------------------------------
Where specific build name leads to page build's page in outside system (like android-build), where they can get additional info, download it, etc. By adding filtering by build type (and having good inventory of types, for example maybe separate "Android Devel" and "Android Release"), it would be easy to let people find what they want.
And if not to do it that way, then this functionality will need to be duplicated in every upstream system of CI, like android-build, offspring, etc.
Thanks, Paul Larson
On 4 July 2011 12:29, Paul Larson paul.larson@linaro.org wrote:
On Sun, Jul 3, 2011 at 9:13 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Yeah. Those results seem rational. Would you test:
https://android-build.linaro.org/builds/~linaro-android/panda-11.06-release/...
This one is currently running
Where are the results?
https://android-build.linaro.org/builds/~linaro-android/leb-panda-11.06-rele...
This one is identical to the above
The leb is different than the one above, dis you test this? Do we have results?
https://android-build.linaro.org/builds/~linaro-android/beagle-11.06-release...
This one is complete, results can be easily found at the usual place based on the url: http://validation.linaro.org/launch-control/dashboard/reports/android-runs/
This link is dead.
...and update the build note on each page with the validation results?
What is this build note and where is it displayed?
Here's the one for beagle:
https://android-build.linaro.org/jenkins/view/Official%20builds/job/linaro-a...
Here's how to update the description from Paul Sokolovsky:
- Make sure you're registered with Jenkins:
https://android-build.linaro.org/jenkins/people/ 2. If you aren't, sign up at https://android-build.linaro.org/jenkins/signup and let me know your username, so I can give you appropriate permissions (Zach, this point is for you) 3. Browse to needed job from Jenkins frontpage: https://android-build.linaro.org/jenkins/ 4. Once you at job's page (e.g. https://android-build.linaro.org/jenkins/job/linaro-android_beagle/), click "add description"/"edit description" in the top right corner, and edit the description. Full HTML is allowed. 5. Click Submit and see if it looks OK. Repeat editing if needed. Otherwise, the description is immediately available at frontend's page for the job. (Though for your own browser, you sometime need to Ctrl+R it to refresh cache).
Is there an easier way of doing this? I don't think anyone wants to be doing this for every single test. Our goal was to automate this, so we really need a way to link the results back in some automated fashion, or they need to just be searched by the person looking for them.
Once its automated then you won't have to do it by hand anymore.
Please add the validation stuff to the bottom.
I held off on this for the time being, pending the answer to my question above. This appeared to be a pretty generic place associated with the whole build, not that specific build id. Is there a better place to add it?
Just put a note in the 11.06 builds indicating the build number that was validated. Please make sure this is done for the 11.06 builds.
Would you do this for all validation results from builds we manual request tested from here on out?
If it's one or two a month, sure. Or better yet, we'll soon be able to let you schedule your own jobs. We're deploying the new lava-server/lava-dashboard this week, and on top of that will be the scheduler as well. This would enable you to kick off your own jobs for one-offs like this. Thanks, Paul Larson
Here's the builds we still need validated:
https://android-build.linaro.org/builds/~linaro-android/panda-11.06-release/ https://android-build.linaro.org/builds/~linaro-android/leb-panda-11.06-rele... https://android-build.linaro.org/builds/~linaro-android/beagle-11.06-release...
Descriptions can be updated at:
https://android-build.linaro.org/jenkins/job/linaro-android_beagle-11.06-rel... https://android-build.linaro.org/jenkins/job/linaro-android_leb-panda-11.06-... https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
On Tue, Jul 12, 2011 at 10:44 AM, Zach Pfeffer zach.pfeffer@linaro.orgwrote:
This one is complete, results can be easily found at the usual place
based
on the url:
http://validation.linaro.org/launch-control/dashboard/reports/android-runs/
This link is dead.
Well, you waited too long to check it :) No, we had a major update that involved integrating the lava-server core for all lava related webapps now (not to mention renaming launch-control). If you want a direct link to the android results now, you can find them at: http://validation.linaro.org/lava-server/dashboard/reports/android-runs/
Here's the builds we still need validated:
All of these were done a while back, and you can find the links by looking at the page mentioned above
https://android-build.linaro.org/builds/~linaro-android/panda-11.06-release/
http://validation.linaro.org/lava-server/dashboard/test-runs/55d4508e-a362-1...
https://android-build.linaro.org/builds/~linaro-android/leb-panda-11.06-rele...
http://validation.linaro.org/lava-server/dashboard/test-runs/b097ae5c-a660-1...
https://android-build.linaro.org/builds/~linaro-android/beagle-11.06-release...
http://validation.linaro.org/lava-server/dashboard/test-runs/f2fc85b0-a656-1...
Descriptions can be updated at:
https://android-build.linaro.org/jenkins/job/linaro-android_beagle-11.06-rel...
https://android-build.linaro.org/jenkins/job/linaro-android_leb-panda-11.06-...
https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
Updated. Just out of curiosity, is there a script that updates those descriptions with the wget links, or are those manually updated right now?
Also, if you, or someone on your team want's access to submit jobs, they need to login to lava (recommend using their launchpad id and openauth). Then I need to know what their ID was so I can give them the proper permissions.
Thanks, Paul Larson
Hello Paul,
On Tue, 12 Jul 2011 13:34:58 -0500 Paul Larson paul.larson@linaro.org wrote:
[]
https://android-build.linaro.org/builds/~linaro-android/beagle-11.06-release...
http://validation.linaro.org/lava-server/dashboard/test-runs/f2fc85b0-a656-1...
Descriptions can be updated at:
https://android-build.linaro.org/jenkins/job/linaro-android_beagle-11.06-rel...
https://android-build.linaro.org/jenkins/job/linaro-android_leb-panda-11.06-...
https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
Updated. Just out of curiosity, is there a script that updates those descriptions with the wget links, or are those manually updated right now?
They're manually updated. For release builds that's probably not too much problem, as releases happen only one a month. However, Jenkins has special "symlink" URLs which point to the latest successful build for example: https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
So, instead of https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
wget could refer to:
https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
Also, if you, or someone on your team want's access to submit jobs, they need to login to lava (recommend using their launchpad id and openauth). Then I need to know what their ID was so I can give them the proper permissions.
I'm not involved directly with integration so far, but would like to be ready to test it. I logged in to LAVA, user name is "pfalcon".
Thanks, Paul Larson
Thanks, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
On Wed, 13 Jul 2011 18:58:09 +0300 Paul Sokolovsky Paul.Sokolovsky@linaro.org wrote:
[]
They're manually updated. For release builds that's probably not too much problem, as releases happen only one a month. However, Jenkins has special "symlink" URLs which point to the latest successful build for example: https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
So, instead of https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
wget could refer to:
https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
And actually, android-build frontend has special short-circuit access to build results via raw HTTP FS access. It turned out to be broken, but I fixed it now:
https://android-build.linaro.org/builds/~linaro-android/leb-panda/120/output...
So instead of using 3 wget commands, only one with "wget -r -np" could be used instead.
And I just made it work for last successful build also:
https://android-build.linaro.org/builds/~linaro-android/leb-panda/lastSucces...
Also, if you, or someone on your team want's access to submit jobs, they need to login to lava (recommend using their launchpad id and openauth). Then I need to know what their ID was so I can give them the proper permissions.
I'm not involved directly with integration so far, but would like to be ready to test it. I logged in to LAVA, user name is "pfalcon".
Thanks, Paul Larson
Thanks, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
You and fgiff should have permissions to do this now. Start by going to: http://validation.linaro.org/api/tokens and make sure you can create a token. Also, starting tomorrow whenever Dave gets in and fixes a firewall rule, you should be able to submit requests via ssl.
Thanks, Paul Larson
On Wed, Jul 13, 2011 at 10:58 AM, Paul Sokolovsky < paul.sokolovsky@linaro.org> wrote:
Hello Paul,
On Tue, 12 Jul 2011 13:34:58 -0500 Paul Larson paul.larson@linaro.org wrote:
[]
https://android-build.linaro.org/builds/~linaro-android/beagle-11.06-release...
http://validation.linaro.org/lava-server/dashboard/test-runs/f2fc85b0-a656-1...
Descriptions can be updated at:
https://android-build.linaro.org/jenkins/job/linaro-android_beagle-11.06-rel...
https://android-build.linaro.org/jenkins/job/linaro-android_leb-panda-11.06-...
https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
Updated. Just out of curiosity, is there a script that updates those descriptions with the wget links, or are those manually updated right now?
They're manually updated. For release builds that's probably not too much problem, as releases happen only one a month. However, Jenkins has special "symlink" URLs which point to the latest successful build for example:
https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
So, instead of
https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
wget could refer to:
https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
Also, if you, or someone on your team want's access to submit jobs, they need to login to lava (recommend using their launchpad id and openauth). Then I need to know what their ID was so I can give them the proper permissions.
I'm not involved directly with integration so far, but would like to be ready to test it. I logged in to LAVA, user name is "pfalcon".
Thanks, Paul Larson
Thanks, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
On 12 July 2011 13:34, Paul Larson paul.larson@linaro.org wrote:
On Tue, Jul 12, 2011 at 10:44 AM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
This one is complete, results can be easily found at the usual place based on the
url: http://validation.linaro.org/launch-control/dashboard/reports/android-runs/
This link is dead.
Well, you waited too long to check it :) No, we had a major update that involved integrating the lava-server core for all lava related webapps now (not to mention renaming launch-control). If you want a direct link to the android results now, you can find them at: http://validation.linaro.org/lava-server/dashboard/reports/android-runs/
Here's the builds we still need validated:
All of these were done a while back, and you can find the links by looking at the page mentioned above
https://android-build.linaro.org/builds/~linaro-android/panda-11.06-release/
http://validation.linaro.org/lava-server/dashboard/test-runs/55d4508e-a362-1...
https://android-build.linaro.org/builds/~linaro-android/leb-panda-11.06-rele...
http://validation.linaro.org/lava-server/dashboard/test-runs/b097ae5c-a660-1...
https://android-build.linaro.org/builds/~linaro-android/beagle-11.06-release...
http://validation.linaro.org/lava-server/dashboard/test-runs/f2fc85b0-a656-1...
Descriptions can be updated at:
https://android-build.linaro.org/jenkins/job/linaro-android_beagle-11.06-rel...
https://android-build.linaro.org/jenkins/job/linaro-android_leb-panda-11.06-...
https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-rele...
Updated. Just out of curiosity, is there a script that updates those descriptions with the wget links, or are those manually updated right now? Also, if you, or someone on your team want's access to submit jobs, they need to login to lava (recommend using their launchpad id and openauth). Then I need to know what their ID was so I can give them the proper permissions.
Cool. Thanks Paul. Everything's manual at the moment. Thanks for the LAVA info.
Thanks, Paul Larson
We have
Android Generic Beagle https://android-build.linaro.org/builds/~patrik-ryd/dev1106genericb/
as well, but it doesn't get out of uboot. Filing a bug,
On 28 June 2011 14:26, Zach Pfeffer zach.pfeffer@linaro.org wrote:
We've got some RC builds available to test:
Android Panda LEB https://android-build.linaro.org/builds/~patrik-ryd/dev1106lebp/
Android Generic Panda https://android-build.linaro.org/builds/~patrik-ryd/dev1106genericp/
Beagle does not boot.
I have attached a little script that makes this easy. Go to the build page and copy the start of the boot image's URL. Plug in an SD card and the serial terminal and run:
trybuild.sh https://android-build.linaro.org/jenkins/job/patrik-ryd_dev1106lebp/6/artifa... /dev/sdd
Once its done it'll drop you into a minicom session.
For those who test would you mind updating:
https://bugs.launchpad.net/bugs/803014 with the type of monitor you used? The build works with some monitors, but not others.
Paul,
Would you manually test these in validation?
Fathi,
Please copy these builds as the rc. There's no beagle board build since it doesn't boot.
-Zach
-
Paul Larson -
Paul Sokolovsky -
Zach Pfeffer