https://osmocom.org/https://osmocom.org/favicon.ico?16647414092017-10-04T12:23:20ZOpen Source Mobile CommunicationsOsmoMSC - Feature #2477: Automate execution and reporting of OsmoMSC interop tests with NG40 core simulatorhttps://osmocom.org/issues/2477?journal_id=55182017-10-04T12:23:20Zpespin
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> OsmoMSC - Feature #2477: Automate execution and reporting of OsmoMSC interop tests with NG40 core simulatorhttps://osmocom.org/issues/2477?journal_id=59592017-10-29T18:29:00Zlaforge
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Urgent</i></li></ul> OsmoMSC - Feature #2477: Automate execution and reporting of OsmoMSC interop tests with NG40 core simulatorhttps://osmocom.org/issues/2477?journal_id=60282017-11-01T18:49:31Zroh
<ul></ul><p>i move the 2 machines over to the osmocom segment now. the new addresses are in the wiki dokumentation page.<br />they should be accessible by jenkins now.</p> OsmoMSC - Feature #2477: Automate execution and reporting of OsmoMSC interop tests with NG40 core simulatorhttps://osmocom.org/issues/2477?journal_id=60572017-11-03T11:53:14Zpespin
<ul></ul><p>Basic setup with 1 test is running in a job from sysmocom's jenkins. We can move the jenkins job to osmocom jenkin's once we define what can be shown there (like ng40tester configs laying in the git repository and then also in the jenkins workspace).</p> OsmoMSC - Feature #2477: Automate execution and reporting of OsmoMSC interop tests with NG40 core simulatorhttps://osmocom.org/issues/2477?journal_id=61432017-11-07T21:35:58Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-3 priority-3 priority-high3 closed" href="/issues/2478">Feature #2478</a>: Manual interop testing with NG40 core simulator</i> added</li></ul> OsmoMSC - Feature #2477: Automate execution and reporting of OsmoMSC interop tests with NG40 core simulatorhttps://osmocom.org/issues/2477?journal_id=64672017-12-01T11:31:10Zpespin
<ul></ul><p>How are we expectred to proceed with this?<br />Everything is setup in an automated way, sysmocom's jenkins fetches repo from sysmocom's private git repository, updates and builds nightly osmocom and runs osmo-msc on Bob, then it runs NG40 test (only 1 so far) and reports it as junit.</p>
<p>Do we want to move it to osmocom's jenkins instance? In that case, we require moving "config-alice" repo to sysmocom's public git repository. The only things in there which may cause some problems are NG40 config files and some audio files (wav, amr).</p>
<p>If it's fine keeping it in sysmocom's jenkins, then I think we can close this task.</p> OsmoMSC - Feature #2477: Automate execution and reporting of OsmoMSC interop tests with NG40 core simulatorhttps://osmocom.org/issues/2477?journal_id=64682017-12-01T12:10:11Zlaforge
<ul></ul><p>On Fri, Dec 01, 2017 at 11:31:10AM +0000, pespin [REDMINE] wrote:</p>
<blockquote>
<p>If it's fine keeping it in sysmocom's jenkins, then I think we can close this task.</p>
</blockquote>
<p>yes, let's keep it this way for the time being. Please add a new ticket/task for expanding<br />the test suite to more comprehensive tests than just a single one :)</p> OsmoMSC - Feature #2477: Automate execution and reporting of OsmoMSC interop tests with NG40 core simulatorhttps://osmocom.org/issues/2477?journal_id=64702017-12-01T12:36:16Zpespin
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-1 priority-lowest" href="/issues/2698">Bug #2698</a>: Add more tests to jenkins job testing osmo-msc against NG40tester</i> added</li></ul> OsmoMSC - Feature #2477: Automate execution and reporting of OsmoMSC interop tests with NG40 core simulatorhttps://osmocom.org/issues/2477?journal_id=64712017-12-01T12:36:36Zpespin
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul> OsmoMSC - Feature #2477: Automate execution and reporting of OsmoMSC interop tests with NG40 core simulatorhttps://osmocom.org/issues/2477?journal_id=74902018-02-06T08:26:41Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>