I wanted to give a heads up on the LAVA results that show up in android-build.linaro.org.
As per the Linaro Data Privacy Policy, the viewing of raw test results/metrics are now only viewable to members of Linaro. In practice, this means the android-build UI won't show test results unless you've logged in to validation.linaro.org with your launchpad ID.
If you are in Linaro and are logged into validation.linaro.org, then everything should magically work.
-andy
On Wed, 2012-05-23 at 09:21 -0500, Andy Doan wrote:
I wanted to give a heads up on the LAVA results that show up in android-build.linaro.org.
As per the Linaro Data Privacy Policy, the viewing of raw test results/metrics are now only viewable to members of Linaro. In practice, this means the android-build UI won't show test results unless you've logged in to validation.linaro.org with your launchpad ID.
If you are in Linaro and are logged into validation.linaro.org, then everything should magically work.
Might be nice if the android-build pages mentioned this next to the test results section for each build, ideally as a link to http://validation.linaro.org/lava-server/accounts/login/ with text like 'login to LAVA to see results'.
Without this, I for one would forget what URL I needed to login to to see results and I wouldn't be able to find this mail to check :-)
On Wed, May 23, 2012 at 5:28 PM, Jon Medhurst (Tixy) tixy@linaro.org wrote:
On Wed, 2012-05-23 at 09:21 -0500, Andy Doan wrote:
I wanted to give a heads up on the LAVA results that show up in android-build.linaro.org.
As per the Linaro Data Privacy Policy, the viewing of raw test results/metrics are now only viewable to members of Linaro. In practice, this means the android-build UI won't show test results unless you've logged in to validation.linaro.org with your launchpad ID.
If you are in Linaro and are logged into validation.linaro.org, then everything should magically work.
Might be nice if the android-build pages mentioned this next to the test results section for each build, ideally as a link to http://validation.linaro.org/lava-server/accounts/login/ with text like 'login to LAVA to see results'.
+1, we should direct users to the login page of lava from the "failed" test result display.
CCed Paul who probably has all the pointers on what to do to get that.
Hello,
On Wed, 23 May 2012 18:18:35 +0200 Alexander Sack asac@linaro.org wrote:
On Wed, May 23, 2012 at 5:28 PM, Jon Medhurst (Tixy) tixy@linaro.org wrote:
On Wed, 2012-05-23 at 09:21 -0500, Andy Doan wrote:
I wanted to give a heads up on the LAVA results that show up in android-build.linaro.org.
As per the Linaro Data Privacy Policy, the viewing of raw test results/metrics are now only viewable to members of Linaro. In practice, this means the android-build UI won't show test results unless you've logged in to validation.linaro.org with your launchpad ID.
If you are in Linaro and are logged into validation.linaro.org, then everything should magically work.
Might be nice if the android-build pages mentioned this next to the test results section for each build, ideally as a link to http://validation.linaro.org/lava-server/accounts/login/ with text like 'login to LAVA to see results'.
+1, we should direct users to the login page of lava from the "failed" test result display.
Or, following the discussion we've been having, we can redirect users to LAVA to see/use/manage test results right away and unconditionally, and just got yet another case which backs such workflow: access restrictions and control. One original objection to such workflow was "why would be people need to do a single click to see LAVA results, if so far they somehow were able to see them without clicks", well we seem to be over even that argument because now most people would need to read that notice, click on a login link, login, find their way back to original android-build frontend page, etc, etc. Why don't we cut that "to login to LAVA and start to explore and use its wealth"?
I for one already tried to see results in LAVA after recent private streams introduction, and faced a bug:
https://bugs.launchpad.net/lava-dashboard/+bug/1003817
CCed Paul who probably has all the pointers on what to do to get that.
On Thu, May 24, 2012 at 10:28 AM, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
Hello,
On Wed, 23 May 2012 18:18:35 +0200 Alexander Sack asac@linaro.org wrote:
On Wed, May 23, 2012 at 5:28 PM, Jon Medhurst (Tixy) tixy@linaro.org wrote:
On Wed, 2012-05-23 at 09:21 -0500, Andy Doan wrote:
I wanted to give a heads up on the LAVA results that show up in android-build.linaro.org.
As per the Linaro Data Privacy Policy, the viewing of raw test results/metrics are now only viewable to members of Linaro. In practice, this means the android-build UI won't show test results unless you've logged in to validation.linaro.org with your launchpad ID.
If you are in Linaro and are logged into validation.linaro.org, then everything should magically work.
Might be nice if the android-build pages mentioned this next to the test results section for each build, ideally as a link to http://validation.linaro.org/lava-server/accounts/login/ with text like 'login to LAVA to see results'.
+1, we should direct users to the login page of lava from the "failed" test result display.
Or, following the discussion we've been having, we can redirect users to LAVA to see/use/manage test results right away and unconditionally, and just got yet another case which backs such workflow: access restrictions and control. One original objection to such workflow was "why would be people need to do a single click to see LAVA results, if so far they somehow were able to see them without clicks", well we seem to be over even that argument because now most people would need to read that notice, click on a login link, login, find their way back to original android-build frontend page, etc, etc. Why don't we cut that "to login to LAVA and start to explore and use its wealth"?
I for one already tried to see results in LAVA after recent private streams introduction, and faced a bug:
I think mid term we can think about making lava the build frontend and dashboard, but as of now we don't have a compelling view and having results displayed colocated to the build is sexy.
e.g. for now I am still +1 on displaying a link that opens a validation.linaro.org login window if no results can be retrieved.
On Thu, 24 May 2012 13:10:28 +0200 Alexander Sack asac@linaro.org wrote:
On Thu, May 24, 2012 at 10:28 AM, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
Hello,
On Wed, 23 May 2012 18:18:35 +0200 Alexander Sack asac@linaro.org wrote:
On Wed, May 23, 2012 at 5:28 PM, Jon Medhurst (Tixy) tixy@linaro.org wrote:
On Wed, 2012-05-23 at 09:21 -0500, Andy Doan wrote:
I wanted to give a heads up on the LAVA results that show up in android-build.linaro.org.
As per the Linaro Data Privacy Policy, the viewing of raw test results/metrics are now only viewable to members of Linaro. In practice, this means the android-build UI won't show test results unless you've logged in to validation.linaro.org with your launchpad ID.
If you are in Linaro and are logged into validation.linaro.org, then everything should magically work.
Might be nice if the android-build pages mentioned this next to the test results section for each build, ideally as a link to http://validation.linaro.org/lava-server/accounts/login/ with text like 'login to LAVA to see results'.
+1, we should direct users to the login page of lava from the "failed" test result display.
Or, following the discussion we've been having, we can redirect users to LAVA to see/use/manage test results right away and unconditionally, and just got yet another case which backs such workflow: access restrictions and control. One original objection to such workflow was "why would be people need to do a single click to see LAVA results, if so far they somehow were able to see them without clicks", well we seem to be over even that argument because now most people would need to read that notice, click on a login link, login, find their way back to original android-build frontend page, etc, etc. Why don't we cut that "to login to LAVA and start to explore and use its wealth"?
I for one already tried to see results in LAVA after recent private streams introduction, and faced a bug:
I think mid term we can think about making lava the build frontend and
Well, my point is that I don't propose to shift build frontend's duties to LAVA, but instead to separate their responsibilities and let each piece do what it can do best.
dashboard, but as of now we don't have a compelling view and having results displayed colocated to the build is sexy.
Well, if only "sexy", because implementation of piles and layers of hackish proxying we do for that is neither sexy to look at nor maintain ;-).
e.g. for now I am still +1 on displaying a link that opens a validation.linaro.org login window if no results can be retrieved.
We definitely can hack up something, though at this time I'm not sure what UI that would have or that it will be "easy" (beautiful) to do (for example, the bug I quoted may preclude easily figuring out when results can't be retrieved vs don't exist). Well, Connect hacking sessions are just the right place to resolve all that, so on TODO.
linaro-android@lists.linaro.org
-
Alexander Sack -
Andy Doan -
Jon Medhurst (Tixy) -
Paul Sokolovsky