shutdown FSM breaks ttcn3-bsc-test

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Tue Jun 23 23:21:28 UTC 2020


dear Pau,

please fix either osmo-bts or ttcn3-bsc-tests so that running ttcn3-bsc-tests works again.
The failure I get for each and every BSC test:

  Verdict: fail reason: "Timeout waiting for BTS0 oml-connection-state ""degraded"

When I downgrade osmo-bts to 580a27e97c3f0e139dfd7b0c10de24463d4b5294 (just
before the shutdown FSM was introduced), the tests work again.
(I didn't bisect, just picked that commit.)

This failure is particularly harmful now because we're currently struggling
with quite a couple of other reasons that cause the ttcn3-bsc-tests to fail. So
when we fix those, jenkins won't show the fix, but yet a different error.

I'm reluctant to revert your patches now, hopefully you can find a fix quickly
to move forward instead.

BTW, I also have introduced another new segfault in osmo-bsc myself, testing
the fix now and merging it directly when successful, so that we don't all go
insane.

~N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20200624/36e18e0b/attachment.bin>


More information about the OpenBSC mailing list