Other remotes are mirrors of gerrit one, which means there's some delay
between pushing some ref to the gerrit remote and having them available
in the mirrors.
Hence, it becomes annoying while developing and new stuff to test is
pushed. Let's simply use gerrit since it's the master remote.
Change-Id: Ic87c196f8b91a3a3e6ddde2cca36482ce7070df7
So far we were executing all our TTCN-3 tests from a container
image with Debian stretch (9) plus a custom more recent eclipse-titan
package from the osmocom feed.
Let's update the container base OS from stretch (9) to bullseye (11)
while using the same packaged eclipse-titan version (8.0.0) for running
the tests. So this should be a low-risk change, as titan runtime
remains identical.
I've executed all test suites locally and couldn't see any regressions.
Related: OS#4969
Change-Id: Ib3bdfa3bec8f8ef42c55ca61cdee8fbca923874f
Write a line like 'Misc_Helpers.mp_osmo_repo := "nightly"' into the
TTCN-3 config file (e.g. BSC_Tests.cfg), before starting the testsuite.
This allows executing different code paths in the tests based on the
repository.
Related: OS#5327
Change-Id: Ic06532f7a67e59458652c5cf4c8f6fee8113e703
The failing test case should never run. The framerelay must run
it's test with dialect NS2_DIALECT_STATIC_RESETBLOCK
Change-Id: I2b1ae7cbe26c94a4a66b6a456b76b864251e0acb
The SNS tests need both NSVCs. The NS_Tests.sns.cfg from the
ttcn3 repository can be used as reference.
Change-Id: I92f2ca61af1e3d0427e6810eddab8f2d6299242d
... which requires some modifications to osmo-ns-master
regarding pipework / docker-entrypoint.sh
Change-Id: I418f81eb1fbb2b15335ef64a3aa04d1c98a452c9
Related: SYS#5396