On 20 August 2012 22:35, YongQin Liu <yongqin....@linaro.org> wrote:
> On 21 August 2012 10:25, YongQin Liu <yongqin....@linaro.org> wrote:
>> Hi, Paul
>>
>> I have tried with the Shift+Reload and Ctrl+R about 10 times for each,
>> but the problem still exists.
>> I have reported it as a bug here:
>> https://bugs.launchpad.net/linaro-android-infrastructure/+bug/1039319
>
> I found the reason.
> We need to access the https://validation.linaro.org/lava-server via FireFox,
> and add the exception trust(not remember the exact name:() for it,
> after that we can see the lava result on the page then.

Oh wow that's a bit convoluted.

Andy, it sounds like we just need to put some instructions together to
point people to the build test results. Do you have any instructions
like that?

>
> Thanks,
> Yongqin Liu
>
>> On 17 August 2012 19:11, Paul Sokolovsky <paul.sokolov...@linaro.org> wrote:
>>> Hello,
>>>
>>> On Fri, 17 Aug 2012 11:18:36 +0800
>>> YongQin Liu <yongqin....@linaro.org> wrote:
>>>
>>>> Hi,
>>>>
>>>> Just found that I can't view the lava result on android-build page for
>>>> some build.
>>>> but not all of them, I still can view some the information of some
>>>> builds before.
>>>> say the builds of
>>>> https://android-build.linaro.org/builds/~linaro-android/snowball-jb-gcc47-igloo-stable-blob/.
>>>> For the build #28 even I click the " login to LAVA " link and logged
>>>> in, I still get this information like the NG.png attachment file.
>>>> But for the build #26, I can see the lava information listed. Like the
>>>> attached OK.png file
>>>
>>> I was not logged into LAVA when I started, logged in from build details
>>> page, and am able to see test results for both #26 and #28 (also tried
>>> #25-#29). So, my guess would be that browser caches content - I saw
>>> such issue on few occasions on android-build.linaro.org . So, please
>>> try Shift+Reload in browser (i.e. click reload button with shift held),
>>> or Ctrl+R few times in row and see if it helps. If you still see that
>>> issue, I'd suggest opening bug at
>>> https://bugs.launchpad.net/linaro-android-infrastructure and Infra's
>>> maintenance engineers will look into it.
>>>
>>>
>>> --
>>> Best Regards,
>>> Paul
>>>
>>> Linaro.org | Open source software for ARM SoCs
>>> Follow Linaro: http://www.facebook.com/pages/Linaro
>>> http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
>>
>>
>>
>> --
>> Thanks,
>> Yongqin Liu
>> ---------------------------------------------------------------
>> #mailing list
>> linaro-andr...@lists.linaro.org
>> http://lists.linaro.org/mailman/listinfo/linaro-android
>> linaro-validat...@lists.linaro.org
>> http://lists.linaro.org/pipermail/linaro-validation
>
>
>
> --
> Thanks,
> Yongqin Liu
> ---------------------------------------------------------------
> #mailing list
> linaro-andr...@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-android
> linaro-validat...@lists.linaro.org
> http://lists.linaro.org/pipermail/linaro-validation
>
> _______________________________________________
> linaro-dev mailing list
> linaro-dev@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-dev



-- 
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Reply via email to