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.deOn Thu, Nov 16, 2017 at 02:59:04PM +0000, Dees wrote: > Hi All, > Was trying to build osmocom 3g system. > Its failing in running test on osmo-hlr, any clues? > ## --------------------------------- #### osmo-hlr 0.1.0.7-8db4 test suite. #### --------------------------------- ## > Regression tests. > 1: auc ok 2: auc_ts_55_205_test_sets ok 3: gsup_server ok 4: db FAILED (testsuite.at:30) > ## ------------- #### Test results. #### ------------- ## > ERROR: All 4 tests were run,1 failed unexpectedly. > > Hi Dees, the error from your log is: -DDB (2067) abort at 18 in [INSERT INTO subscriber (imsi) VALUES ($imsi)]: UNIQUE constraint failed: subscriber.imsi +DDB (2067) abort at 35 in [INSERT INTO subscriber (imsi) VALUES ($imsi)]: UNIQUE constraint failed: subscriber.imsi which is the identical error as the test run intends to produce, except that "at 18" became "at 35" for no apparent reason. I wonder what that number is supposed to mean ... 35 could point at the IMSI value, while 18 doesn't make any sense at all. I cannot reproduce your failure locally, my test outcome expects '18', and that's what the test gives me. It has been '18' from the start in the git history of that file. Anyway, this is an error message produced by sqlite, and maybe they have fixed the number '18' to point closer to the IMSI instead? I am using libsqlite 3.16.2-5 on Debian 9, what version are you running? ...we may need to disable that error output for the test or mangle the output somehow... ~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/20171119/dfee2da7/attachment.bin>