osmo-bts build verification broken
All build verification by jenkins for osmo-bts is broken, as a new version of the OCTPHY headers was pushed to
octphy-2g-headers/master without previously merging the osmo-bts related patches to actually support those headers.
I've now force-pushed an older version to "master" and started a new "next" branch for the latest (but not yet supported by osmo-bts!) version of the headers that was pushed on April 14.
#1 Updated by dexter over 1 year ago
- Status changed from New to Feedback
- Assignee changed from dexter to laforge
The patch that addes support was merged on April 9 (https://gerrit.osmocom.org/#/c/osmo-bts/+/7487/) I re-tested it locally with the current master of osmo-bts and octphy-2g-headers/next and it compiles fine.
When I look at the log output from jenkins I can see:
checking whether to enable support for Octasic OCTPHY-2G... yes checking for octphy/octvc1/gsm/octvc1_gsm_default.h... yes checking for tOCTVC1_GSM_TRX_CONFIG.usCentreArfcn... yes checking for tOCTVC1_HW_RF_PORT_RX_STATS.Frequency... yes checking for tOCTVC1_HW_MSG_CLOCK_SYNC_MGR_STATS_RSP.ulSyncLossCnt... no checking for tOCTVC1_HW_MSG_RF_PORT_INFO_ANTENNA_TX_CONFIG_RSP.TxConfig... yes checking for tOCTVC1_HW_MSG_RF_PORT_INFO_ANTENNA_RX_CONFIG_RSP.RxConfig... yes checking for tOCTVC1_GSM_RF_CONFIG.ulTxAntennaId... yes
This is output is clearly from the status before the patch for the new headers has been merged. Somehow Jenkins decided to compile against an older state. I am a bit lost here. Any ideas?