Hi All,
I notice that there are still some jobs being submitted to LAVA with the device-type "vexpress". This device type is now deprecated and has been replaced by the more specific device type vexpress-a9. The jobs seem to be coming from CI and Android. Could someone amend these submissions?
Thanks
Dave
Dave Pigott Validation Engineer T: +44 1223 40 00 63 | M +44 7940 45 93 44 Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog
Hello,
On Mon, 24 Sep 2012 08:30:34 +0100 Dave Pigott dave.pigott@linaro.org wrote:
Hi All,
I notice that there are still some jobs being submitted to LAVA with the device-type "vexpress". This device type is now deprecated and has been replaced by the more specific device type vexpress-a9. The jobs seem to be coming from CI and Android. Could someone amend these submissions?
Tracked as https://bugs.launchpad.net/linaro-ci/+bug/1055354 (Critical).
Thanks
Dave
could we keep deprecated backward compatibility mapping on LAVA side for a while? On Sep 24, 2012 10:01 AM, "Paul Sokolovsky" paul.sokolovsky@linaro.org wrote:
Hello,
On Mon, 24 Sep 2012 08:30:34 +0100 Dave Pigott dave.pigott@linaro.org wrote:
Hi All,
I notice that there are still some jobs being submitted to LAVA with the device-type "vexpress". This device type is now deprecated and has been replaced by the more specific device type vexpress-a9. The jobs seem to be coming from CI and Android. Could someone amend these submissions?
Tracked as https://bugs.launchpad.net/linaro-ci/+bug/1055354 (Critical).
Thanks
Dave
-- Best Regards, 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
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
Unfortunately, not as easy as it sounds. We'd have to actually change the dispatcher to intercept submissions to vexpress, and then re-route them to vexpress-a9, because we can'\t have two device instances talking to the same device. I'll look into it, but it would be quite a nasty bodge.
Dave
On 24 Sep 2012, at 10:23, Alexander Sack wrote:
could we keep deprecated backward compatibility mapping on LAVA side for a while?
On Sep 24, 2012 10:01 AM, "Paul Sokolovsky" paul.sokolovsky@linaro.org wrote: Hello,
On Mon, 24 Sep 2012 08:30:34 +0100 Dave Pigott dave.pigott@linaro.org wrote:
Hi All,
I notice that there are still some jobs being submitted to LAVA with the device-type "vexpress". This device type is now deprecated and has been replaced by the more specific device type vexpress-a9. The jobs seem to be coming from CI and Android. Could someone amend these submissions?
Tracked as https://bugs.launchpad.net/linaro-ci/+bug/1055354 (Critical).
Thanks
Dave
-- Best Regards, 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
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
On Mon, Sep 24, 2012 at 12:48 PM, Dave Pigott dave.pigott@linaro.org wrote:
Unfortunately, not as easy as it sounds. We'd have to actually change the dispatcher to intercept submissions to vexpress, and then re-route them to vexpress-a9, because we can'\t have two device instances talking to the same device. I'll look into it, but it would be quite a nasty bodge.
right. guess would justify an "alias" feature for device-types in LAVA framework before we can do that.
For now let's move our builds over to use vexpress-a9
1. android-build should be fixed now (at least the code got submitted); if you still see it tomorrow let me know. 2. for ci.linaro.org I have to talk to fabo; will not bother him until he has worked around the android-build git timeout issues currently blocking release.
Alexander Sack alexander.sack@linaro.org writes:
On Mon, Sep 24, 2012 at 12:48 PM, Dave Pigott dave.pigott@linaro.org wrote:
Unfortunately, not as easy as it sounds. We'd have to actually change the dispatcher to intercept submissions to vexpress, and then re-route them to vexpress-a9, because we can'\t have two device instances talking to the same device. I'll look into it, but it would be quite a nasty bodge.
right. guess would justify an "alias" feature for device-types in LAVA framework before we can do that.
Yeah, I think so too. I filed https://bugs.launchpad.net/lava-scheduler/+bug/1055821 in an effort not to forget about this for next time :)
Cheers, mwh
On 24 Sep 2012, at 12:03, Alexander Sack wrote:
On Mon, Sep 24, 2012 at 12:48 PM, Dave Pigott dave.pigott@linaro.org wrote:
Unfortunately, not as easy as it sounds. We'd have to actually change the dispatcher to intercept submissions to vexpress, and then re-route them to vexpress-a9, because we can'\t have two device instances talking to the same device. I'll look into it, but it would be quite a nasty bodge.
right. guess would justify an "alias" feature for device-types in LAVA framework before we can do that.
For now let's move our builds over to use vexpress-a9
- android-build should be fixed now (at least the code got
submitted); if you still see it tomorrow let me know. 2. for ci.linaro.org I have to talk to fabo; will not bother him until he has worked around the android-build git timeout issues currently blocking release.
Looks like android is switched over. I assume Fathi is still blocked for getting ci switched.
Dave
On 25 September 2012 10:22, Dave Pigott dave.pigott@linaro.org wrote:
On 24 Sep 2012, at 12:03, Alexander Sack wrote:
On Mon, Sep 24, 2012 at 12:48 PM, Dave Pigott dave.pigott@linaro.org wrote:
Unfortunately, not as easy as it sounds. We'd have to actually change the dispatcher to intercept submissions to vexpress, and then re-route them to vexpress-a9, because we can'\t have two device instances talking to the same device. I'll look into it, but it would be quite a nasty bodge.
right. guess would justify an "alias" feature for device-types in LAVA framework before we can do that.
For now let's move our builds over to use vexpress-a9
- android-build should be fixed now (at least the code got
submitted); if you still see it tomorrow let me know. 2. for ci.linaro.org I have to talk to fabo; will not bother him until he has worked around the android-build git timeout issues currently blocking release.
Looks like android is switched over. I assume Fathi is still blocked for getting ci switched.
All jobs are now updated. Only 3 missing, fixed now by Deepti.
Cheers,
Fathi
On 25 Sep 2012, at 08:40, Fathi Boudra wrote:
On 25 September 2012 10:22, Dave Pigott dave.pigott@linaro.org wrote:
On 24 Sep 2012, at 12:03, Alexander Sack wrote:
On Mon, Sep 24, 2012 at 12:48 PM, Dave Pigott dave.pigott@linaro.org wrote:
Unfortunately, not as easy as it sounds. We'd have to actually change the dispatcher to intercept submissions to vexpress, and then re-route them to vexpress-a9, because we can'\t have two device instances talking to the same device. I'll look into it, but it would be quite a nasty bodge.
right. guess would justify an "alias" feature for device-types in LAVA framework before we can do that.
For now let's move our builds over to use vexpress-a9
- android-build should be fixed now (at least the code got
submitted); if you still see it tomorrow let me know. 2. for ci.linaro.org I have to talk to fabo; will not bother him until he has worked around the android-build git timeout issues currently blocking release.
Looks like android is switched over. I assume Fathi is still blocked for getting ci switched.
All jobs are now updated. Only 3 missing, fixed now by Deepti.
Thanks Fathi. Backlog of vexpress jobs has now been cleared.
Dave
-
Alexander Sack -
Dave Pigott -
Fathi Boudra -
Michael Hudson-Doyle -
Paul Sokolovsky