On 4 July 2011 12:29, Paul Larson <paul.lar...@linaro.org> wrote: > > On Sun, Jul 3, 2011 at 9:13 PM, Zach Pfeffer <zach.pfef...@linaro.org> > wrote: >> >> Yeah. Those results seem rational. Would you test: >> >> >> https://android-build.linaro.org/builds/~linaro-android/panda-11.06-release/#build=3 > > This one is currently running
Where are the results? >> >> >> https://android-build.linaro.org/builds/~linaro-android/leb-panda-11.06-release/ > > 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/#build=2 > > 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-android_beagle-11.06-release/ > >> >> 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). > > 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-release/ 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-release/ https://android-build.linaro.org/jenkins/job/linaro-android_leb-panda-11.06-release/ https://android-build.linaro.org/jenkins/job/linaro-android_panda-11.06-release/ _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
