Yeah. Those results seem rational. Would you test: https://android-build.linaro.org/builds/~linaro-android/panda-11.06-release/#build=3
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/#build=2 ...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.lar...@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? _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
