[Fuego] [PATCH 9/9] pi_tests: add meaningful specs
Daniel Sangorrin
daniel.sangorrin at toshiba.co.jp
Fri Jan 12 03:08:23 UTC 2018
> > -----Original Message-----
> > From: fuego-bounces at lists.linuxfoundation.org [mailto:fuego-
> > bounces at lists.linuxfoundation.org] On Behalf Of Daniel Sangorrin
> > Sent: Thursday, January 11, 2018 12:29 AM
> > To: fuego at lists.linuxfoundation.org
> > Subject: [Fuego] [PATCH 9/9] pi_tests: add meaningful specs
> >
> > Signed-off-by: Daniel Sangorrin <daniel.sangorrin at toshiba.co.jp>
> > ---
> > engine/tests/Functional.pi_tests/spec.json | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/engine/tests/Functional.pi_tests/spec.json
> > b/engine/tests/Functional.pi_tests/spec.json
> > index 0a429c9..96f51a4 100644
> > --- a/engine/tests/Functional.pi_tests/spec.json
> > +++ b/engine/tests/Functional.pi_tests/spec.json
> > @@ -4,6 +4,15 @@
> > "default": {
> > "PARAMS": "--duration=60"
> > },
> > + "roundrobin": {
> > + "PARAMS": "--duration=60 --rr"
> > + },
> > + "uniprocessor": {
> > + "PARAMS": "--duration=60 --uniprocessor"
> > + },
> > + "stress": {
> > + "PARAMS": "--duration=60 --groups=20"
> > + },
>
>
> These are nice additions. The stress test has some weird behavior on one
> of my systems (I only tested on one system so far). The test fails, and Fuego
> doesn't end up collecting all of its output.
>
> If I run it on the command line (on the target board), I get the following output:
>
> Starting PI Stress Test
> Number of thread groups: 20
> Duration of test run: 60 seconds
> Number of inversions per group: unlimited
> Admin thread SCHED_FIFO priority 4
> 20 groups of 3 threads will be created
> High thread SCHED_FIFO priority 3
> Med thread SCHED_FIFO priority 2
> Low thread SCHED_FIFO priority 1
> Current Inversions: 122740
> WATCHDOG triggered: group 2 is deadlocked!
> WATCHDOG triggered: group 3 is deadlocked!
> WATCHDOG triggered: group 4 is deadlocked!
> WATCHDOG triggered: group 5 is deadlocked!
> WATCHDOG triggered: group 6 is deadlocked!
> WATCHDOG triggered: group 7 is deadlocked!
> WATCHDOG triggered: group 8 is deadlocked!
> WATCHDOG triggered: group 9 is deadlocked!
> WATCHDOG triggered: group 10 is deadlocked!
> WATCHDOG triggered: group 11 is deadlocked!
> WATCHDOG triggered: group 12 is deadlocked!
> WATCHDOG triggered: group 13 is deadlocked!
> WATCHDOG triggered: group 14 is deadlocked!
> WATCHDOG triggered: group 15 is deadlocked!
> WATCHDOG triggered: group 17 is deadlocked!
> WATCHDOG triggered: group 19 is deadlocked!
> reporter stopping due to watchdog event
> Stopping test
> Terminated
> ---------------------------------
>
> The testlog.txt file for a run from Fuego is:
>
> Starting PI Stress Test
> Number of thread groups: 20
> Duration of test run: 60 seconds
> Number of inversions per group: unlimited
> Admin thread SCHED_FIFO priority 4
> 20 groups of 3 threads will be created
> High thread SCHED_FIFO priority 3
> Med thread SCHED_FIFO priority 2
> Low thread SCHED_FIFO priority 1
>
> [1ACurrent Inversions: 42702
> [1ACurrent Inversions: 62390
> [1ACurrent Inversions: 82293
> [1ACurrent Inversions: 103649
>
> In the console log, I see a signal from the Jenkins handling process (I think).
>
> I need to dig into this and see:
> 1) is the failure expected for this board? - if not, it's a bug with the board or software
> 2) why does Fuego not have the full program output?
>
> In any event - these have nothing to do with the spec additions per se.
> But I need to track down if the stress test has uncovered some board bugs
> or other Fuego bugs.
>
> The spec changes are approved, and I applied the patch.
>
> Thanks!
> -- Tim
>
Sorry this is a bug on my side. I will fix it soon.
Thanks,
Daniel
More information about the Fuego
mailing list