Log all RA values which cause test failure
Previously the first timeout in TC_rach_content() caused test to
fail. Related TC_rach_count() test shows that there're some (13-16 out
of 1000) RA values which are problematic. Let's log all such values in
TC_rach_content() before failing the test to, hopefully, spot the
pattern which sets such RA values apart.
Change-Id: Ibfeb377101f406608c0193f08729c0e6d084281e
Related: OS#1854
diff --git a/bts/BTS_Tests.ttcn b/bts/BTS_Tests.ttcn
index 66bf040..279b437 100644
--- a/bts/BTS_Tests.ttcn
+++ b/bts/BTS_Tests.ttcn
@@ -996,6 +996,7 @@
f_l1_tune(L1CTL);
var GsmFrameNumber fn_last := 0;
+ var boolean test_failed := false;
for (var integer i := 0; i < 1000; i := i+1) {
var OCT1 ra := f_rnd_ra_cs();
var GsmFrameNumber fn := f_L1CTL_RACH(L1CTL, oct2int(ra));
@@ -1015,11 +1016,14 @@
}
[] RSL_CCHAN.receive { repeat; }
[] T.timeout {
- Misc_Helpers.f_shutdown(__BFILE__, __LINE__, fail, log2str("Timeout waiting for CHAN RQD FN=", fn, " RA=", ra));
+ test_failed := true;
+ log("[", i, "] Timeout waiting for CHAN RQD FN=", fn, " RA=", ra);
}
}
}
- setverdict(pass);
+ if (test_failed == false) {
+ setverdict(pass);
+ }
Misc_Helpers.f_shutdown(__BFILE__, __LINE__);
}