Build failure of network:osmocom:nightly/osmo-stp in xUbuntu_16.04/x86_64

2017-04-20 Thread OBS Notification
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/osmo-stp/xUbuntu_16.04/x86_64 Package network:osmocom:nightly/osmo-stp failed to build in xUbuntu_16.04/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-stp Last lines of build l

Build failure of network:osmocom:nightly/libosmo-sccp in xUbuntu_16.04/x86_64

2017-04-20 Thread OBS Notification
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/libosmo-sccp/xUbuntu_16.04/x86_64 Package network:osmocom:nightly/libosmo-sccp failed to build in xUbuntu_16.04/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-sccp Last lin

Build failure of network:osmocom:nightly/osmo-stp in xUbuntu_16.10/x86_64

2017-04-20 Thread OBS Notification
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/osmo-stp/xUbuntu_16.10/x86_64 Package network:osmocom:nightly/osmo-stp failed to build in xUbuntu_16.10/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-stp Last lines of build l

Build failure of network:osmocom:nightly/osmo-stp in Debian_8.0/x86_64

2017-04-20 Thread OBS Notification
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/osmo-stp/Debian_8.0/x86_64 Package network:osmocom:nightly/osmo-stp failed to build in Debian_8.0/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-stp Last lines of build log: [

Build failure of network:osmocom:nightly/libosmo-sccp in Debian_8.0/x86_64

2017-04-20 Thread OBS Notification
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/libosmo-sccp/Debian_8.0/x86_64 Package network:osmocom:nightly/libosmo-sccp failed to build in Debian_8.0/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-sccp Last lines of

Build failure of network:osmocom:nightly/libosmo-sccp in xUbuntu_16.10/x86_64

2017-04-20 Thread OBS Notification
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/libosmo-sccp/xUbuntu_16.10/x86_64 Package network:osmocom:nightly/libosmo-sccp failed to build in xUbuntu_16.10/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-sccp Last lin

Build failure of network:osmocom:nightly/osmo-stp in xUbuntu_16.10/i586

2017-04-20 Thread OBS Notification
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/osmo-stp/xUbuntu_16.10/i586 Package network:osmocom:nightly/osmo-stp failed to build in xUbuntu_16.10/i586 Check out the package for editing: osc checkout network:osmocom:nightly osmo-stp Last lines of build log:

Build failure of network:osmocom:nightly/libosmo-sccp in xUbuntu_16.10/i586

2017-04-20 Thread OBS Notification
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/libosmo-sccp/xUbuntu_16.10/i586 Package network:osmocom:nightly/libosmo-sccp failed to build in xUbuntu_16.10/i586 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-sccp Last lines o

Build failure of network:osmocom:nightly/osmo-stp in Debian_8.0/i586

2017-04-20 Thread OBS Notification
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/osmo-stp/Debian_8.0/i586 Package network:osmocom:nightly/osmo-stp failed to build in Debian_8.0/i586 Check out the package for editing: osc checkout network:osmocom:nightly osmo-stp Last lines of build log: [ 134

Build failure of network:osmocom:nightly/osmo-stp in xUbuntu_16.04/i586

2017-04-20 Thread OBS Notification
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/osmo-stp/xUbuntu_16.04/i586 Package network:osmocom:nightly/osmo-stp failed to build in xUbuntu_16.04/i586 Check out the package for editing: osc checkout network:osmocom:nightly osmo-stp Last lines of build log:

Build failure of network:osmocom:nightly/libosmo-sccp in Debian_8.0/i586

2017-04-20 Thread OBS Notification
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/libosmo-sccp/Debian_8.0/i586 Package network:osmocom:nightly/libosmo-sccp failed to build in Debian_8.0/i586 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-sccp Last lines of build

Build failure of network:osmocom:nightly/libosmo-sccp in xUbuntu_16.04/i586

2017-04-20 Thread OBS Notification
Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/libosmo-sccp/xUbuntu_16.04/i586 Package network:osmocom:nightly/libosmo-sccp failed to build in xUbuntu_16.04/i586 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-sccp Last lines o

libosmo-netif[master]: api doc: Call the variable by the right ("crx") name

2017-04-20 Thread Neels Hofmeyr
Patch Set 1: (1 comment) https://gerrit.osmocom.org/#/c/2284/1/src/datagram.c File src/datagram.c: Line 101: * \param[in] crx talloc context from which to allocate memory hmm really? "crx" for talloc context almost certainly looks like a typo and many follow-up typos? what is "crx" supposed

osmo-bts[master]: measurement/cosmetic: Fixup source code comment

2017-04-20 Thread Max
Patch Set 1: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/2387 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I3d3488c97d0bffa7d449d3675afcc75b2a6a2703 Gerrit-PatchSet: 1 Gerrit-Project: osmo-bts Gerrit-Branch: master Gerrit

osmo-bts[master]: measurement/cosmetic: Fixup source code comment

2017-04-20 Thread Max
Patch Set 1: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/2388 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ic6e4037f965772e6b851c67662d5e7bf64cc04eb Gerrit-PatchSet: 1 Gerrit-Project: osmo-bts Gerrit-Branch: master Gerrit

[PATCH] openbsc[master]: Fix measurement display

2017-04-20 Thread Max
Review at https://gerrit.osmocom.org/2391 Fix measurement display * set proper flag when saving MS Timing Offset * use gsm_subscriber's IMSI or lchan's name if bsc_subscriber is unknown * add comments with spec reference * display MS Timing Offset instead of raw Timing Offset field from RSL * r

[PATCH] osmo-bts[master]: Add MS TO to RSL measurements

2017-04-20 Thread Max
Hello Jenkins Builder, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/1700 to look at the new patch set (#5). Add MS TO to RSL measurements Add optional MS timing offset (3GPP TS 45.010 § 1.2) to RSL MEASUREMENT RESULT (3GPP TS 48.058 § 8.4.8). The value is ca

[PATCH] osmo-bts[master]: measurement: Improve log output

2017-04-20 Thread dexter
Review at https://gerrit.osmocom.org/2389 measurement: Improve log output The debug log does not print much information about the measured rxlev and rxqual values. This commit adds debug output to make measurement debugging simpler Change-Id: Ic871eed6dcbc7d10aca6cd11dbc803b3e6da449f --- M src

[PATCH] osmo-bts[master]: octphy: align frame number for new firmware versions

2017-04-20 Thread dexter
Hello Harald Welte, Jenkins Builder, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/1965 to look at the new patch set (#6). octphy: align frame number for new firmware versions Firmware releases OCTSDR-2G-02.07.00-B1314-BETA and newer require to align the GPRS

[PATCH] osmo-bts[master]: octphy: activate CBCH after all physical channels are activated

2017-04-20 Thread dexter
Hello Harald Welte, Jenkins Builder, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/2314 to look at the new patch set (#4). octphy: activate CBCH after all physical channels are activated CBCH is activated when the SAPI for TS0 is activated. Since the CBCH can

[PATCH] osmo-bts[master]: measurement/cosmetic: Fixup source code comment

2017-04-20 Thread dexter
Review at https://gerrit.osmocom.org/2388 measurement/cosmetic: Fixup source code comment the function is_meas_complete() uses the *_meas_rep_fn104[] lookup tables, defined at the beginning of the source file. These lookup tabels contain a lot of magic numbers. This commit adds a more elaborat

[PATCH] osmo-bts[master]: octphy: remove old event control code

2017-04-20 Thread dexter
Hello Jenkins Builder, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/1980 to look at the new patch set (#7). octphy: remove old event control code Event handling is done internally in the Octasic BTS. When the TRX is opened, events are enabled automatically a

[PATCH] osmo-bts[master]: measurement/cosmetic: Fixup source code comment

2017-04-20 Thread dexter
Review at https://gerrit.osmocom.org/2387 measurement/cosmetic: Fixup source code comment the function ber10k_to_rxqual() has only a very brief comment with the spec reference. This commit adds a more explainatory comment that makes it easier to understand from where the ber10k constants are ta

[PATCH] osmo-bts[master]: octphy: ensure that 11 bit rach flag is not set

2017-04-20 Thread dexter
Review at https://gerrit.osmocom.org/2390 octphy: ensure that 11 bit rach flag is not set The l1 interface does not explicitly set the flag for 11 bit rach when a rach request is received. Since the current and previous octphy firmwares do not support 11 bit rach requests, the flag should be ex

[PATCH] osmo-bts[master]: bts: revert trx shutdown order

2017-04-20 Thread dexter
Hello Harald Welte, Jenkins Builder, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/1977 to look at the new patch set (#6). bts: revert trx shutdown order When a new TRX is allocated using gsm_bts_trx_alloc() (see gsm_data_shared.c in openbsc.git), than it is

libosmocore[master]: control_if: Add helper function for 'local execution' of con...

2017-04-20 Thread Max
Patch Set 2: (2 comments) https://gerrit.osmocom.org/#/c/2376/2/src/ctrl/control_if.c File src/ctrl/control_if.c: Line 817: * talloc_freee() the return value. typo https://gerrit.osmocom.org/#/c/2376/2/tests/fsm/fsm_test.c File tests/fsm/fsm_test.c: Line 12: that seems odd - only header i