You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug#36235275 test_event -n Bug44915 T1, error insert 13031, 13044, 13045 are never hit
Various issues here :
1. Those error inserts are not hit as they are in SUMA execSUB_CREATE_REQ()
which is only executed on SUMA when a Subscriber (aka EventOperation) is
created.
Just creating the Event is not enough to trigger them, so the test
covers nothing and naturally they would be left behind when it finishes.
Solution :
- Add create EventOperation and check that it fails
2. The other error inserts (error2) are related to SUMA Scans, where it
asks DIH to get distribution info. The error inserts are intended
to give code coverage of some 'many fragments' continueB cases.
a) This has nothing to do with Events
b) Creating and Dropping events does not involve scanning
Solution :
- Split into separate testcase
- Add index creation which *will* trigger a SUMA scan and will
cause these error insertions to be hit.
3. Error insert 13049 causes a crash when hit.
This error insert triggers a CONTINUEB, but then carries on with
the scan.
When the CONTINUEB arrives, the scan is not in the correct state
causing a crash.
Fix by having the code return after queueing the CONTINUEB.
Summary :
Testcase was a mess, testing nothing.
Error insert being left behind was a good indicator of a problem.
New test :
test_event -n SumaScanGetNodesContinueB T1 added to daily-basic--03
Change-Id: I4c4470cc6ef2a53dd470a4e4ac90ca1085504140
0 commit comments