Attention is currently required from: fixeria. arehbein has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33465 )
Change subject: WIP: sgsn: Fix TC_attach_timeout_after_pdp_act failing ...................................................................... Patch Set 2: (2 comments) File sgsn/SGSN_Tests.ttcn: https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33465/comment/928b894e_406bfddb PS2, Line 1067: setverdict(pass) > There is already `setverdict(pass)` below, this one is redundant. yes I thought so too, but just wanted to make sure it doesn't fail because of that https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33465/comment/b2e7fc91_33d8c529 PS2, Line 1078: vc_conn.done > have to say though... […] Alright my idea didn't fix anything it seems. I'm having a hard time debugging this, also because I can't find the log output coded in the `.ttcn3` file via `log()`. There seems to be all kinds of log data (e.g., output from the SGSN, packet dumps, logs in the folder `sgsn-tester` etc.) but I can't find a file with the log outputs coded in `SGSN_Tests.ttcn` (fairly certain I couldn't do so previously either - I think with another test) and I'm pretty certain the ttcn code has arrived at one of the log commands (since I don't have a debugger like gdb to wrap around the tester all I can do is try to guess until where the code is run...). I might try looking at the pcap again, but so far the output is fairly confusing for me since I don't know the procedure. Hmmm I just noticed the `log()` output is in the pcap through `GSMTAP libosmocore logging` (?) -- To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33465 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: Ibaf2134247153471bd45d7a7f91155294c6c6de5 Gerrit-Change-Number: 33465 Gerrit-PatchSet: 2 Gerrit-Owner: arehbein <[email protected]> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <[email protected]> Gerrit-Attention: fixeria <[email protected]> Gerrit-Comment-Date: Mon, 26 Jun 2023 22:33:56 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: arehbein <[email protected]> Comment-In-Reply-To: fixeria <[email protected]> Gerrit-MessageType: comment
