Started by an SCM change0000168916891.086218621010310862086203391cc86e2396c98815506c4270b364da0f8974f824acc86e2396c98815506c4270b364da0f8974f824aorigin/mastercc86e2396c98815506c4270b364da0f8974f824acc86e2396c98815506c4270b364da0f8974f824aorigin/master26947fb8722448b9c523cdd1edda8f89c100880316be7fb8722448b9c523cdd1edda8f89c100880316berefs/remotes/origin/master7fb8722448b9c523cdd1edda8f89c100880316be7fb8722448b9c523cdd1edda8f89c100880316berefs/remotes/origin/mastercc86e2396c98815506c4270b364da0f8974f824acc86e2396c98815506c4270b364da0f8974f824aorigin/masterhttps://gerrit.osmocom.org/osmo-ttcn3-hackshttps://jenkins.osmocom.org/jenkins/job/registry-trigger-osmo-ttcn3-hacks/lastCompletedBuild/artifacthttps://jenkins.osmocom.org/jenkins/job/registry-trigger-osmo-ttcn3-hacks/changeshttps://jenkins.osmocom.org/jenkins/job/registry-trigger-osmo-ttcn3-hacks/lastCompletedBuild/https://jenkins.osmocom.org/jenkins/job/registry-trigger-osmo-ttcn3-hacks/lastCompletedBuild/testReportfalse#339116891558registry-trigger-osmo-ttcn3-hacks #33913391falsefalse3391187391SUCCESS1785838389050https://jenkins.osmocom.org/jenkins/job/registry-trigger-osmo-ttcn3-hacks/3391/build4-deb12build-ansible- eim/testenv.cfgcc86e2396c98815506c4270b364da0f8974f824a1785838234000https://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.depmaier@sysmocom.deeim/testenv: put mnesia database into volatile location
When running the TTCN3 testsuite in testenv, we create the database
files in a non-volatile location. This means that with every
consecutive test run, the database from the first test run is
re-used. This may lead to unexpected behaviour.
With this patch we change the location of the database to a volatile
location, so that each testrun uses a fresh database.
Related: SYS#8100
Change-Id: I178e4fcd29880668467b6deaa44f44d142b8c29c
2026-08-04 10:10:34 +0000cc86e2396c98815506c4270b364da0f8974f824aeim/testenv: put mnesia database into volatile locationediteim/testenv.cfg
githttps://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.depmaier