Hi,

The models are currently stable. Here are the jobs for release. Most of it has completed:
http://validation.linaro.org/scheduler/job/87699
https://validation.linaro.org/scheduler/job/87700
https://validation.linaro.org/scheduler/job/87701

Submitted one more with partial test from job 87700:
http://validation.linaro.org/scheduler/job/88187

Its okay to have multiple models per machine but we need to have only one model running Android per machine which has proven to be stable. If we run Android on more than one model per machine then it results in adb errors. Hence Yongqin requested to take _04 offline.

Currently juice is the only project where Android is booted extensively on "rtsm_fvp_base-aemv8a" models. It is preferred to have only one such model per H/W instance to have the setup stable for Android.

Regards,
Vishal

On 25 November 2013 15:01, Jakub Pavelek <jakub.pavelek@linaro.org> wrote:

Hi guys,

we should have setup with one model per HW instance. (Otherwise our tests will not run reliably). Guys help us getting that up and running again, it is release week.

Br,

--jakub

On 24 November 2013 14:52, Antonio Terceiro <antonio.terceiro@linaro.org> wrote:

On Sat, Nov 23, 2013 at 12:54:40AM +0800, Yongqin Liu wrote:
> Hi, Antonio
>
> Thanks for the help.
> http://validation.linaro.org/scheduler/job/87680/log_file is booted up with
> the latest build#219.
>
> But one thing I noticed that, both rtsm_fvp_base-aemv8a_02 and
> rtsm_fvp_base-aemv8a_04 are on fastmodels02.localdomain,
> could you help to disable rtsm_fvp_base-aemv8a_04?
> since when run two instances on one node at the same time, it may cause the
> adb problem.

There are fastmodels on the same machine (which may also cause the same
problem?) so I doubt if take _04 offline will make any difference.
--
Antonio Terceiro
Software Engineer - Linaro
http://www.linaro.org