On 15/12/18 7:17 pm, Jiri Gaisler wrote:
>
> On 12/15/18 1:07 AM, Chris Johns wrote:
>> On 14/12/18 8:48 pm, Jiri Gaisler wrote:
>>> OK, I will look into this over Christmas. I have some long flights
>>> coming up so it will be a good way to kill time ... :-)
>> Great. I have been on a few flights
On 12/15/18 9:17 AM, Jiri Gaisler wrote:
>>
>> There is a ticket open on 5.1 to have tests that do fail to be tagged as
>> "Expected Fail" so we can baseline what is expected. I cannot do this alone
>> because I am not sure which ones are expected failures.
>
> I looked into the failures again and
On 12/15/18 1:07 AM, Chris Johns wrote:
> On 14/12/18 8:48 pm, Jiri Gaisler wrote:
>> OK, I will look into this over Christmas. I have some long flights
>> coming up so it will be a good way to kill time ... :-)
> Great. I have been on a few flights recently and I have been doing the same
> thing.
On 14/12/18 8:48 pm, Jiri Gaisler wrote:
> OK, I will look into this over Christmas. I have some long flights
> coming up so it will be a good way to kill time ... :-)
Great. I have been on a few flights recently and I have been doing the same
thing. Power in the seats is nice and WiFi is even bet
On 12/14/18 11:52 AM, Joel Sherrill wrote:
>
> The tsim bitmap format is easy. If it produces that there will be no
> modifications.
>
>
> The ability to control the trace file name would be nice. The
> rtems-test tool
> runs the sis simulator in parallel on the available cores and we
On Fri, Dec 14, 2018, 1:07 AM Chris Johns On 13/12/2018 20:30, Sebastian Huber wrote:
> > On 13/12/2018 09:16, Jiri Gaisler wrote:
> >>> I use the SIS every day for RTEMS development and test suite runs. The
> >>> SMP support would be a very valuable for RTEMS development. If we can
> >>> get also
On 12/14/18 7:07 AM, Chris Johns wrote:
>
> The covoar tool currently support the couverture qemu trace format. I am not
> sure if it is something Adacore invented.
>
> The covoar tool is run from within the rtems-test tool when the BSP supports
> coverage. It has the ability to support a number of
On 13/12/2018 20:30, Sebastian Huber wrote:
> On 13/12/2018 09:16, Jiri Gaisler wrote:
>>> I use the SIS every day for RTEMS development and test suite runs. The
>>> SMP support would be a very valuable for RTEMS development. If we can
>>> get also code coverage from it, then it would be perfect.
>
On 13/12/2018 09:16, Jiri Gaisler wrote:
I use the SIS every day for RTEMS development and test suite runs. The
SMP support would be a very valuable for RTEMS development. If we can
get also code coverage from it, then it would be perfect.
I can look at the coverage support. Is there a standardi
> I use the SIS every day for RTEMS development and test suite runs. The
> SMP support would be a very valuable for RTEMS development. If we can
> get also code coverage from it, then it would be perfect.
I can look at the coverage support. Is there a standardized format for
coverage data that I
On 12/12/2018 17:20, Jiri Gaisler wrote:
On 12/12/18 10:26 AM, Sebastian Huber wrote:
- Am 12. Dez 2018 um 10:01 schrieb Jiri Gaisler j...@gaisler.se:
After implementing the interrupt broadcast function, and stop telling
the software that there are 5 cores in the system when there really o
On 12/12/18 10:26 AM, Sebastian Huber wrote:
> - Am 12. Dez 2018 um 10:01 schrieb Jiri Gaisler j...@gaisler.se:
>
>> After implementing the interrupt broadcast function, and stop telling
>> the software that there are 5 cores in the system when there really only
>> are 4, all tests run fine ..
- Am 12. Dez 2018 um 10:01 schrieb Jiri Gaisler j...@gaisler.se:
> After implementing the interrupt broadcast function, and stop telling
> the software that there are 5 cores in the system when there really only
> are 4, all tests run fine ..:-)
This sounds great.
> I can run all SMP tests w
After implementing the interrupt broadcast function, and stop telling
the software that there are 5 cores in the system when there really only
are 4, all tests run fine ..:-) I can run all SMP tests with a time slot
of 50 clocks except smpclock01.exe, which fails with:
*** BEGIN OF TEST SMPCLOCK
14 matches
Mail list logo
