Attention is currently required from: jolly.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33817 )
Change subject: BTS_Test_ASCI: Add UPLINK FREE / UPLINK BUSY test
......................................................................
Patch Set 3: Code-Review+1
(1 comment)
File bts/BTS_Tests_ASCI.ttcn:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33817/comment/4f5e55a1_6e5e…
PS3, Line 158: RSL.send(ts_RSL_UNITDATA_REQ(g_chan_nr, ts_RslLinkID_DCCH(0), uplink_free));
: for (var integer i := 0; i < 20; i := i + 1) {
: f_l1_exp_lapdm(tr_LAPDm_Bter_UI(uplink_free));
: log("Received UPLINK FREE.");
: }
:
: /* Send one UPLINK BUSY message and expect it to be received. */
: log("Send UPLINK BUSY.");
: RSL.send(ts_RSL_UNITDATA_REQ(g_chan_nr, ts_RslLinkID_DCCH(0), uplink_busy));
: f_l1_exp_lapdm(tr_LAPDm_UI(0, cr_MT_CMD, uplink_busy));
> again here I smell the potential for race conditions. […]
nevermind. this is unit-data and there are no re-transmissions at BTS level, so this should be safe here.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33817
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: I2f70adb4a6f71eb8972feccf9dda0f77e7a942b9
Gerrit-Change-Number: 33817
Gerrit-PatchSet: 3
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: jolly <andreas(a)eversberg.eu>
Gerrit-Comment-Date: Wed, 19 Jul 2023 08:12:22 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: comment
Attention is currently required from: jolly.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33817 )
Change subject: BTS_Test_ASCI: Add UPLINK FREE / UPLINK BUSY test
......................................................................
Patch Set 3:
(1 comment)
File bts/BTS_Tests_ASCI.ttcn:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33817/comment/ed116d0b_efb5…
PS3, Line 158: RSL.send(ts_RSL_UNITDATA_REQ(g_chan_nr, ts_RslLinkID_DCCH(0), uplink_free));
: for (var integer i := 0; i < 20; i := i + 1) {
: f_l1_exp_lapdm(tr_LAPDm_Bter_UI(uplink_free));
: log("Received UPLINK FREE.");
: }
:
: /* Send one UPLINK BUSY message and expect it to be received. */
: log("Send UPLINK BUSY.");
: RSL.send(ts_RSL_UNITDATA_REQ(g_chan_nr, ts_RslLinkID_DCCH(0), uplink_busy));
: f_l1_exp_lapdm(tr_LAPDm_UI(0, cr_MT_CMD, uplink_busy));
again here I smell the potential for race conditions. Things don't happen synchronously and there are many queues involved. So you cannot reliably guarantee there's no old uplink_free still receiveda this point here.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33817
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: I2f70adb4a6f71eb8972feccf9dda0f77e7a942b9
Gerrit-Change-Number: 33817
Gerrit-PatchSet: 3
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: jolly <andreas(a)eversberg.eu>
Gerrit-Comment-Date: Wed, 19 Jul 2023 08:11:21 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: mschramm, roh.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-remsim/+/33812 )
Change subject: log at NOTICE level if somebody uses loopback addresses.
......................................................................
Patch Set 2: Code-Review-1
(1 comment)
File src/client/main_fsm.c:
https://gerrit.osmocom.org/c/osmo-remsim/+/33812/comment/62e55518_1f10ce37
PS2, Line 252: LOGPFSML(fi, LOGL_NOTICE, "we were instructed to connect to a bankd on a loopback address "
: "%s. This is most likely a BROKEN CONFIGURATION, unless this client runs on the "
: "same host as remsim-bankd\n", bc->bankd_conn.server_host);
we can actually be smarter about this message (on the client side): Only log this message if we ourselves are also using a loopback address. This way no NOTICE messages are printed when somebody actually does run bankd+client on localhost (which works). you just cannot run one on non-localhost and the other on it.
--
To view, visit https://gerrit.osmocom.org/c/osmo-remsim/+/33812
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-remsim
Gerrit-Branch: master
Gerrit-Change-Id: I3b4eda10e81a705aef8d647a860890a74cba8f13
Gerrit-Change-Number: 33812
Gerrit-PatchSet: 2
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: mschramm <mschramm(a)sysmocom.de>
Gerrit-Reviewer: roh <jsteiger(a)sysmocom.de>
Gerrit-Attention: mschramm <mschramm(a)sysmocom.de>
Gerrit-Attention: roh <jsteiger(a)sysmocom.de>
Gerrit-Comment-Date: Wed, 19 Jul 2023 08:09:45 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: jolly.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33816 )
Change subject: BTS_Test_ASCI: Add first ASCI test to check NCH support
......................................................................
Patch Set 3:
(2 comments)
Patchset:
PS3:
a
File bts/BTS_Tests_ASCI.ttcn:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33816/comment/600c512b_9222…
PS3, Line 107: RSL_CCHAN.send(ts_ASP_RSL_UD(ts_RSL_NOTIF_CMD_STOP(gcr)));
:
: /* NCH must not be received. */
there is a potential race condition here between the last L1CTL.receive above, and the time you send the NOTIF_CMD_STOP. Another NCH message might be stored in any of the buffers of osmo-bts, the kernel, trxcon, or a TITAN component, and then magically appear below when you no longer expect them.
This is the kind of race condition which makes tests fail occasionally and reuslts in ustable test results in jenkins.
If there is no confirmation message to the CMD_STOP from the BTS you cannot make assumptions when it will actually arrive and execute.
Hence, as a work-around it might be prudent to wait for somehing like 0.5s and then flush any pending L1CTL messages before executing the below code.
There might be other solutions, just think about the problem in general and see what you can come up with.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33816
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: I3727c471663b731117a264f60d2f1ba5fd16928e
Gerrit-Change-Number: 33816
Gerrit-PatchSet: 3
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: jolly <andreas(a)eversberg.eu>
Gerrit-Comment-Date: Wed, 19 Jul 2023 08:03:11 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment