![[RTEMS Logo]](/images/logo.png){kind=logo}
Opened on 08/28/20 at 23:10:21
Closed on 09/25/20 at 01:16:43
#4066 closed defect (fixed)
test running for too long
| Reported by: | Chris Johns | Owned by: | Chris Johns |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.1 |
| Component: | test | Version: | 6 |
| Severity: | normal | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: |
Description
The spcache01 test on my PC test hardware is not finishing. It is looping generating output. Add a Test too long error count and end the test after 5 minutes.
Change History (5)
comment:1 follow-up: 2 Changed on 08/30/20 at 14:51:51 by Sebastian Huber
comment:2 Changed on 08/31/20 at 03:27:33 by Chris Johns
Replying to Sebastian Huber:
Which test case runs too long and why?
The test is spcache01. I do not know the reason but I am using it to add support to handle a stuck test that loops for ever generating output.
comment:3 Changed on 08/31/20 at 06:34:43 by Sebastian Huber
The spcache01 test program contains several test cases. If one of them loops forever, then there is a bug in the test or the cache support.
For the test runner wouldn't this be a timed out test?
comment:4 Changed on 08/31/20 at 07:52:45 by Chris Johns
This ticket is about the tester being able to handle that case. The failure has highlighted a need for the tester to detect this, end the test and report the failure.
comment:5 Changed on 09/25/20 at 01:16:43 by Chris Johns
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Which test case runs too long and why?