Patch Set 2:
> According to the commit description, both LogTest.err and
> LogTest.ok
> are related to a single disabled test. I am not sure we really need
> these files, if the test is disabled itself...
It's not the only disabled test I do the same here for other tests which are not working in its current/old form (due to changing output). I could remove the files but it can still make sense to leave them there to see better in follow-up commits how the changes affect the output. It also shows in the current commit how the output is unusable yet and why the test is disabled.
Patch-set: 2
Reviewer: Pau Espin Pedrol <1000074@035e6965-6537-41bd-912c-053f3cf69326>
Label: Code-Review=0
Patch Set 2:
According to the commit description, both LogTest.err and LogTest.ok
are related to a single disabled test. I am not sure we really need
these files, if the test is disabled itself...
Patch-set: 2
Reviewer: Vadim Yanitskiy <1000010@035e6965-6537-41bd-912c-053f3cf69326>
Label: Code-Review=0
Patch Set 2:
> Why move to tests/CommonLibs/ instead of just tests/ ?
Because it's testing stuff from CommonLibs directory. We may want to test stuff from other parts, and this way is a lot clearer which part of the code is it testing. We do the same in osmo-ggsn (subdirs gtp, lib).
Patch-set: 2
Uploaded patch set 1.
Patch-set: 1
Change-id: I3d6ba625968be09297642d18090c496490e9b8fc
Subject: Set up GNU Autotest infrastructure
Branch: refs/heads/master
Commit: b85a5ca2fa
Groups: 82f83ced73