On Sun, 13 Jan 2019 at 08:41, Chris Johns wrote:
> On 13/1/19 7:19 am, Vijay Kumar Banerjee wrote:
> >
> > With the recent change to the qemu options I'm getting results invalid
> when
> > running rtems-test without the coverage option. However, it works fine
> when the
> > coverage option is ena
On 13/1/19 7:19 am, Vijay Kumar Banerjee wrote:
>
> With the recent change to the qemu options I'm getting results invalid when
> running rtems-test without the coverage option. However, it works fine when
> the
> coverage option is enabled.
>
What are the command lines for each run?
Chris
On 1/11/19 1:36 PM, Jiri Gaisler wrote:
> On 1/9/19 10:46 AM, Sebastian Huber wrote:
>> Hello Jiri,
>>
>> could you please rebase your work to this RTEMS commit:
>>
>> https://git.rtems.org/rtems/commit/?id=b9ffc41c9678fb3c5386c1a6ab394656ec85dbc6
>>
> This works fine for me - I can now pass all u
Hi,
With the recent change to the qemu options I'm getting results invalid when
running rtems-test without the coverage option. However, it works fine when
the coverage option is enabled.
==
Passed: 1
Failed: 0
User Input: 0
Expected Fail: 0
In