Commit 0addb17
committed
checkpoints: do not use SOF_TEST_INTERVAL in test _iterations_
The purpose of SOF_TEST_INTERVAL is to avoid log gaps between tests,
_not_ between test iterations of the same test.
Fixes issue where the (recent) check-kmod-load-unload.sh was catching
_multiple_ firmware boots, including boots from previous test
iterations, example:
sof-test/test-case/check-mod-load-unload.sh -l 50
Polling 'sof_firmware_boot_complete --since=@1646100584' every 1s for 10s
[ 2968.155103] kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: firmware boot complete
[ 2970.706560] kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: firmware boot complete
[ 2974.522111] kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: firmware boot complete
Completed 'sof_firmware_boot_complete --since=@1646100584' after 0s and 1 attempts
This may fix other, similar tests too.
Signed-off-by: Marc Herbert <marc.herbert@intel.com>1 parent 71291e1 commit 0addb17
2 files changed
Lines changed: 12 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
86 | 86 | | |
87 | 87 | | |
88 | 88 | | |
| 89 | + | |
| 90 | + | |
89 | 91 | | |
90 | 92 | | |
91 | 93 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
82 | 82 | | |
83 | 83 | | |
84 | 84 | | |
85 | | - | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
| 90 | + | |
| 91 | + | |
| 92 | + | |
86 | 93 | | |
87 | 94 | | |
88 | 95 | | |
| |||
425 | 432 | | |
426 | 433 | | |
427 | 434 | | |
| 435 | + | |
| 436 | + | |
428 | 437 | | |
429 | 438 | | |
430 | 439 | | |
| |||
0 commit comments