On 5/7/2022 8:50 pm, Jiri Gaisler wrote:
>
> On 7/5/22 12:45, Sebastian Huber wrote:
>>
>>
>> On 05/07/2022 12:31, Chris Johns wrote:
>>>
On 5 Jul 2022, at 6:23 pm, Sebastian
Huber wrote:
On 05/07/2022 10:21, Chris Johns wrote:
>> On 5/7/2022 4:29 pm, Sebastian Huber wrot
On 7/5/22 12:45, Sebastian Huber wrote:
On 05/07/2022 12:31, Chris Johns wrote:
On 5 Jul 2022, at 6:23 pm, Sebastian Huber
wrote:
On 05/07/2022 10:21, Chris Johns wrote:
On 5/7/2022 4:29 pm, Sebastian Huber wrote:
On 05/07/2022 08:23, Chris Johns wrote:
On 5/7/2022 4:02 pm, Sebastian
On 05/07/2022 12:31, Chris Johns wrote:
On 5 Jul 2022, at 6:23 pm, Sebastian Huber
wrote:
On 05/07/2022 10:21, Chris Johns wrote:
On 5/7/2022 4:29 pm, Sebastian Huber wrote:
On 05/07/2022 08:23, Chris Johns wrote:
On 5/7/2022 4:02 pm, Sebastian Huber wrote:
On 05/07/2022 07:14, Chris J
On 7/5/22 12:31, Chris Johns wrote:
On 5 Jul 2022, at 6:23 pm, Sebastian Huber
wrote:
On 05/07/2022 10:21, Chris Johns wrote:
On 5/7/2022 4:29 pm, Sebastian Huber wrote:
On 05/07/2022 08:23, Chris Johns wrote:
On 5/7/2022 4:02 pm, Sebastian Huber wrote:
On 05/07/2022 07:14, Chris Johns
> On 5 Jul 2022, at 6:23 pm, Sebastian Huber
> wrote:
>
> On 05/07/2022 10:21, Chris Johns wrote:
>>> On 5/7/2022 4:29 pm, Sebastian Huber wrote:
>>> On 05/07/2022 08:23, Chris Johns wrote:
On 5/7/2022 4:02 pm, Sebastian Huber wrote:
> On 05/07/2022 07:14, Chris Johns wrote:
>> O
On 05/07/2022 10:21, Chris Johns wrote:
On 5/7/2022 4:29 pm, Sebastian Huber wrote:
On 05/07/2022 08:23, Chris Johns wrote:
On 5/7/2022 4:02 pm, Sebastian Huber wrote:
On 05/07/2022 07:14, Chris Johns wrote:
On 5/7/2022 2:58 pm, Sebastian Huber wrote:
On 05/07/2022 03:08, Chris Johns wrote:
On 5/7/2022 4:29 pm, Sebastian Huber wrote:
> On 05/07/2022 08:23, Chris Johns wrote:
>> On 5/7/2022 4:02 pm, Sebastian Huber wrote:
>>> On 05/07/2022 07:14, Chris Johns wrote:
On 5/7/2022 2:58 pm, Sebastian Huber wrote:
> On 05/07/2022 03:08, Chris Johns wrote:
>> On 5/7/2022 9:44 am,
On 05/07/2022 08:23, Chris Johns wrote:
On 5/7/2022 4:02 pm, Sebastian Huber wrote:
On 05/07/2022 07:14, Chris Johns wrote:
On 5/7/2022 2:58 pm, Sebastian Huber wrote:
On 05/07/2022 03:08, Chris Johns wrote:
On 5/7/2022 9:44 am, Joel Sherrill wrote:
The limit removed in sis and tsim is the s
On 5/7/2022 4:02 pm, Sebastian Huber wrote:
> On 05/07/2022 07:14, Chris Johns wrote:
>> On 5/7/2022 2:58 pm, Sebastian Huber wrote:
>>> On 05/07/2022 03:08, Chris Johns wrote:
On 5/7/2022 9:44 am, Joel Sherrill wrote:
> The limit removed in sis and tsim is the simulated cpu time used. If
On 05/07/2022 07:14, Chris Johns wrote:
On 5/7/2022 2:58 pm, Sebastian Huber wrote:
On 05/07/2022 03:08, Chris Johns wrote:
On 5/7/2022 9:44 am, Joel Sherrill wrote:
The limit removed in sis and tsim is the simulated cpu time used. If not using
that, the behavior of the tester is to let the si
On 5/7/2022 2:58 pm, Sebastian Huber wrote:
> On 05/07/2022 03:08, Chris Johns wrote:
>> On 5/7/2022 9:44 am, Joel Sherrill wrote:
>>> The limit removed in sis and tsim is the simulated cpu time used. If not
>>> using
>>> that, the behavior of the tester is to let the simulator run for so much
>>
On 05/07/2022 03:08, Chris Johns wrote:
On 5/7/2022 9:44 am, Joel Sherrill wrote:
The limit removed in sis and tsim is the simulated cpu time used. If not using
that, the behavior of the tester is to let the simulator run for so much real
processor time.
Replacing these with a command line argu
On 5/7/2022 9:44 am, Joel Sherrill wrote:
> The limit removed in sis and tsim is the simulated cpu time used. If not using
> that, the behavior of the tester is to let the simulator run for so much real
> processor time.
>
> Replacing these with a command line argument is probably good but just
The limit removed in sis and tsim is the simulated cpu time used. If not
using that, the behavior of the tester is to let the simulator run for so
much real processor time.
Replacing these with a command line argument is probably good but just
removing these mean these simulators will just run muc
OK
Chris
On 4/7/2022 6:52 pm, Sebastian Huber wrote:
> Remove the hard coded time limits in the SIS configurations which would
> overrule the general tester settings (for example the--timeout command line
> option).
> ---
> tester/rtems/testing/bsps/erc32-sis.ini | 2 +-
> tester/rtems/test
Remove the hard coded time limits in the SIS configurations which would
overrule the general tester settings (for example the--timeout command line
option).
---
tester/rtems/testing/bsps/erc32-sis.ini | 2 +-
tester/rtems/testing/bsps/gr740-sis.ini | 2 +-
tester/rtems/testing/bsps/grisc
16 matches
Mail list logo
