Hi Pau,
Thanks for your advice. We're now seeing srsepc being deployed to the machine and
attempting to run but the test job eventually fails as a timeout expires after five
minutes. It appears as if srsepc is being told to run without any configuration as per the
output of "ps aux" below:
jenkins 10292 0.0 0.0 2608 596 pts/0 Ss+ 16:07 0:00 sh -c sudo
osmo-gsm-tester_setcap_net_admin.sh /osmo-gsm-tester-srsepc/srslte/bin/srsepc
root 10293 0.0 0.0 8816 4388 pts/0 S+ 16:07 0:00 sudo
osmo-gsm-tester_setcap_net_admin.sh /osmo-gsm-tester-srsepc/srslte/bin/srsepc
The full job log is available here as a GitHub Gist:
https://gist.github.com/callumsnowden/8c1c52353f8adbdead318612d4f9efe4
There looks to be a full configuration successfully generated and I can see this on the
slave machine. Our test suite configuration is located here
https://github.com/callumsnowden/osmo-gsm-tester/tree/lc_srsran_config_test…
and only has changes relating to the hardware configuration for the test suite.
Is there some other configuration that needs to be done to get srsepc to launch with the
generated configuration? Any help/advice you could offer would be most appreciated.
Best,
Callum.