June 2024 - jenkins-notifications

Build failed in Jenkins: ttcn3-bts-test-io_uring #24
by jenkins＠lists.osmocom.org 09 Jul '24

09 Jul '24

See <https://jenkins.osmocom.org/jenkins/job/ttcn3-bts-test-io_uring/24/display/…> Changes: [Pau Espin Pedrol] asterisk: pjsip.conf: Update IMS port asterisk config [Pau Espin Pedrol] asterisk: pjsip.conf: Set default p_access_network_info ------------------------------------------ [...truncated 682.71 KB...] <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1475 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:157 TC_sabm_ua_dcch_sapi0_nopayload testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_sabm_ua_dcch_sapi3' time='15.024293'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1476 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:162 TC_sabm_ua_dcch_sapi3 testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_sabm_ua_dcch_sapi4' time='15.024392'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1477 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:167 TC_sabm_ua_dcch_sapi4 testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_sabm_contention' time='15.025596'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1478 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:201 TC_sabm_contention testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_sabm_retransmit' time='15.025919'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1479 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:225 TC_sabm_retransmit testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_sabm_retransmit_bts' time='15.026129'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1480 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:315 TC_sabm_retransmit_bts testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_sabm_invalid_resp' time='15.025628'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1481 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:379 TC_sabm_invalid_resp testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_sabm_dm' time='15.025747'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1482 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:425 TC_sabm_dm testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_establish_ign_first_sabm' time='15.021335'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1483 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:488 TC_establish_ign_first_sabm testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_iframe_seq_and_ack' time='15.025521'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1484 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:579 TC_iframe_seq_and_ack testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_iframe_timer_recovery' time='15.011392'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1485 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:685 TC_iframe_timer_recovery testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_ns_seq_error' time='15.024381'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1486 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:768 TC_ns_seq_error testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_nr_seq_error' time='15.024102'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1487 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:831 TC_nr_seq_error testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_rec_invalid_frame' time='15.023878'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1488 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:961 TC_rec_invalid_frame testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_segm_concat_dcch' time='15.024231'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1489 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:1088 TC_segm_concat_dcch testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_segm_concat_sacch' time='15.023148'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1490 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:1093 TC_segm_concat_sacch testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_t200_n200' time='15.025509'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1491 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:1182 TC_t200_n200 testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_rr_response_frame_loss' time='15.025883'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1492 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:1239 TC_rr_response_frame_loss testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_incorrect_cr' time='15.011787'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1493 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:1293 TC_incorrect_cr testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_sabm_incorrect_c' time='15.026046'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1494 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:1341 TC_sabm_incorrect_c testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_normal_reestablishment' time='15.025797'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1495 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:1403 TC_normal_reestablishment testcase </failure> </testcase> <testcase classname='BTS_Tests_LAPDm' name='TC_normal_reestablishment_state_unacked' time='15.025865'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_LAPDm.ttcn:1496 BTS_Tests_LAPDm control part BTS_Tests_LAPDm.ttcn:1470 TC_normal_reestablishment_state_unacked testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_act_vff' time='15.026314'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:316 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:210 TC_vamos_chan_act_vff testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_act_vhh' time='15.026396'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:317 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:224 TC_vamos_chan_act_vhh testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_act_hvhh' time='15.026057'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:318 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:234 TC_vamos_chan_act_hvhh testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_act_dyn_ipa_vff' time='15.026330'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:319 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:214 TC_vamos_chan_act_dyn_ipa_vff testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_act_dyn_osmo_vff' time='15.025989'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:320 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:218 TC_vamos_chan_act_dyn_osmo_vff testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_act_dyn_osmo_vhh' time='15.025778'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:321 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:228 TC_vamos_chan_act_dyn_osmo_vhh testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_act_dyn_osmo_hvhh' time='15.026069'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:322 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:238 TC_vamos_chan_act_dyn_osmo_hvhh testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_mode_modify_vff' time='15.044920'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:325 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:283 TC_vamos_chan_mode_modify_vff testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_mode_modify_vhh' time='15.025766'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:326 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:297 TC_vamos_chan_mode_modify_vhh testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_mode_modify_hvhh' time='15.026382'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:327 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:307 TC_vamos_chan_mode_modify_hvhh testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_mode_modify_dyn_ipa_vff' time='15.026058'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:328 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:287 TC_vamos_chan_mode_modify_dyn_ipa_vff testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_mode_modify_dyn_osmo_vff' time='15.041878'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:329 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:291 TC_vamos_chan_mode_modify_dyn_osmo_vff testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_mode_modify_dyn_osmo_vhh' time='15.027828'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:330 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:301 TC_vamos_chan_mode_modify_dyn_osmo_vhh testcase </failure> </testcase> <testcase classname='BTS_Tests_VAMOS' name='TC_vamos_chan_mode_modify_dyn_osmo_hvhh' time='15.023763'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_VAMOS.ttcn:331 BTS_Tests_VAMOS control part BTS_Tests_VAMOS.ttcn:311 TC_vamos_chan_mode_modify_dyn_osmo_hvhh testcase </failure> </testcase> <testcase classname='BTS_Tests_ASCI' name='TC_vbs_notification' time='15.026025'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_ASCI.ttcn:415 BTS_Tests_ASCI control part BTS_Tests_ASCI.ttcn:77 TC_vbs_notification testcase </failure> </testcase> <testcase classname='BTS_Tests_ASCI' name='TC_vgcs_uplink_free_and_busy' time='15.025921'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_ASCI.ttcn:416 BTS_Tests_ASCI control part BTS_Tests_ASCI.ttcn:183 TC_vgcs_uplink_free_and_busy testcase </failure> </testcase> <testcase classname='BTS_Tests_ASCI' name='TC_vgcs_talker_fail' time='15.025864'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_ASCI.ttcn:417 BTS_Tests_ASCI control part BTS_Tests_ASCI.ttcn:282 TC_vgcs_talker_fail testcase </failure> </testcase> <testcase classname='BTS_Tests_ASCI' name='TC_vgcs_talker_est_rel' time='15.025600'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_ASCI.ttcn:418 BTS_Tests_ASCI control part BTS_Tests_ASCI.ttcn:326 TC_vgcs_talker_est_rel testcase </failure> </testcase> <testcase classname='BTS_Tests_ASCI' name='TC_vgcs_listener_det' time='15.025562'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_ASCI.ttcn:419 BTS_Tests_ASCI control part BTS_Tests_ASCI.ttcn:404 TC_vgcs_listener_det testcase </failure> </testcase> </testsuite> Build step 'Execute shell' marked build as failure Recording test results [Checks API] No suitable checks publisher found.

1 33

Jenkins build became unstable: ttcn3-gbproxy-test-io_uring #111
by jenkins＠lists.osmocom.org 03 Jul '24

03 Jul '24

See <https://jenkins.osmocom.org/jenkins/job/ttcn3-gbproxy-test-io_uring/111/dis…>

1 1

Build failed in Jenkins: master-openbsc » --disable-iu,--disable-mgcp-transcoding,--enable-smpp,default,osmocom-master #17121
by jenkins＠lists.osmocom.org 30 Jun '24

30 Jun '24

See <https://jenkins.osmocom.org/jenkins/job/master-openbsc/IU=--disable-iu,MGCP…> Changes: ------------------------------------------ [...truncated 470.78 KB...] > ss -tln State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess LISTEN 0 1 0.0.0.0:5001 0.0.0.0:* LISTEN 0 1 127.0.0.1:5000 0.0.0.0:* LISTEN 0 10 127.0.0.1:4244 0.0.0.0:* LISTEN 0 10 127.0.0.1:4250 0.0.0.0:* > ps xua | grep osmo build 43688 0.0 0.0 13452 7500 ? S 00:05 0:00 ./src/osmo-bsc_nat/osmo-bsc_nat -l 127.0.0.1 -c /build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg build 43695 0.0 0.0 2576 892 ? S 00:05 0:00 /bin/sh -c ps xua | grep osmo build 43697 0.0 0.0 3700 1896 ? S 00:05 0:00 grep osmo Socket: in 1 tries, connected to 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33052), raddr=('127.0.0.1', 4244)> (1 sockets open) MSC is ready at 127.0.0.1 'show msc connection' says: 'MSC is connected: 1' ERROR Socket: closing 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33052), raddr=('127.0.0.1', 4244)> (0 sockets open) Process returned code: -15 testEnsureNoEnsureModeSet (__main__.TestVTYNAT.testEnsureNoEnsureModeSet) ... Launching: PWD=/build/openbsc './src/osmo-bsc_nat/osmo-bsc_nat' '-l' '127.0.0.1' '-c' '/build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg' > ls -l /proc/43427/fd total 0 lr-x------ 1 build build 64 Jun 30 00:04 0 -> pipe:[201944326] l-wx------ 1 build build 64 Jun 30 00:04 1 -> pipe:[201944327] l-wx------ 1 build build 64 Jun 30 00:04 2 -> pipe:[201944328] l-wx------ 1 build build 64 Jun 30 00:04 3 -> /dev/null > ss -tn State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess > ss -tln State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess LISTEN 0 1 0.0.0.0:5001 0.0.0.0:* LISTEN 0 1 127.0.0.1:5000 0.0.0.0:* LISTEN 0 10 127.0.0.1:4244 0.0.0.0:* LISTEN 0 10 127.0.0.1:4250 0.0.0.0:* > ps xua | grep osmo build 43698 0.0 0.0 13452 6912 ? S 00:05 0:00 ./src/osmo-bsc_nat/osmo-bsc_nat -l 127.0.0.1 -c /build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg build 43705 0.0 0.0 2576 944 ? S 00:05 0:00 /bin/sh -c ps xua | grep osmo build 43707 0.0 0.0 3700 1840 ? S 00:05 0:00 grep osmo Socket: in 1 tries, connected to 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33058), raddr=('127.0.0.1', 4244)> (1 sockets open) Socket: closing 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33058), raddr=('127.0.0.1', 4244)> (0 sockets open) Process returned code: -15 ok testPrefixTreeLoading (__main__.TestVTYNAT.testPrefixTreeLoading) ... Launching: PWD=/build/openbsc './src/osmo-bsc_nat/osmo-bsc_nat' '-l' '127.0.0.1' '-c' '/build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg' > ls -l /proc/43427/fd total 0 lr-x------ 1 build build 64 Jun 30 00:04 0 -> pipe:[201944326] l-wx------ 1 build build 64 Jun 30 00:04 1 -> pipe:[201944327] l-wx------ 1 build build 64 Jun 30 00:04 2 -> pipe:[201944328] l-wx------ 1 build build 64 Jun 30 00:04 3 -> /dev/null > ss -tn State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess > ss -tln State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess LISTEN 0 1 0.0.0.0:5001 0.0.0.0:* LISTEN 0 1 127.0.0.1:5000 0.0.0.0:* LISTEN 0 10 127.0.0.1:4244 0.0.0.0:* LISTEN 0 10 127.0.0.1:4250 0.0.0.0:* > ps xua | grep osmo build 43708 0.0 0.0 13452 7604 ? S 00:05 0:00 ./src/osmo-bsc_nat/osmo-bsc_nat -l 127.0.0.1 -c /build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg build 43715 0.0 0.0 2576 912 ? S 00:05 0:00 /bin/sh -c ps xua | grep osmo build 43717 0.0 0.0 3700 1808 ? S 00:05 0:00 grep osmo Socket: in 1 tries, connected to 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33060), raddr=('127.0.0.1', 4244)> (1 sockets open) Socket: closing 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33060), raddr=('127.0.0.1', 4244)> (0 sockets open) Process returned code: -15 ok testRewriteNoRewrite (__main__.TestVTYNAT.testRewriteNoRewrite) ... Launching: PWD=/build/openbsc './src/osmo-bsc_nat/osmo-bsc_nat' '-l' '127.0.0.1' '-c' '/build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg' > ls -l /proc/43427/fd total 0 lr-x------ 1 build build 64 Jun 30 00:04 0 -> pipe:[201944326] l-wx------ 1 build build 64 Jun 30 00:04 1 -> pipe:[201944327] l-wx------ 1 build build 64 Jun 30 00:04 2 -> pipe:[201944328] l-wx------ 1 build build 64 Jun 30 00:04 3 -> /dev/null > ss -tn State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess > ss -tln State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess LISTEN 0 1 0.0.0.0:5001 0.0.0.0:* LISTEN 0 1 127.0.0.1:5000 0.0.0.0:* LISTEN 0 10 127.0.0.1:4244 0.0.0.0:* LISTEN 0 10 127.0.0.1:4250 0.0.0.0:* > ps xua | grep osmo build 43718 0.0 0.0 13452 6884 ? S 00:05 0:00 ./src/osmo-bsc_nat/osmo-bsc_nat -l 127.0.0.1 -c /build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg build 43725 0.0 0.0 2576 928 ? S 00:05 0:00 /bin/sh -c ps xua | grep osmo build 43727 0.0 0.0 3700 1800 ? S 00:05 0:00 grep osmo Socket: in 1 tries, connected to 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33076), raddr=('127.0.0.1', 4244)> (1 sockets open) Socket: closing 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33076), raddr=('127.0.0.1', 4244)> (0 sockets open) Process returned code: -15 ok testRewritePostNoRewrite (__main__.TestVTYNAT.testRewritePostNoRewrite) ... Launching: PWD=/build/openbsc './src/osmo-bsc_nat/osmo-bsc_nat' '-l' '127.0.0.1' '-c' '/build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg' > ls -l /proc/43427/fd total 0 lr-x------ 1 build build 64 Jun 30 00:04 0 -> pipe:[201944326] l-wx------ 1 build build 64 Jun 30 00:04 1 -> pipe:[201944327] l-wx------ 1 build build 64 Jun 30 00:04 2 -> pipe:[201944328] l-wx------ 1 build build 64 Jun 30 00:04 3 -> /dev/null > ss -tn State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess > ss -tln State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess LISTEN 0 1 0.0.0.0:5001 0.0.0.0:* LISTEN 0 1 127.0.0.1:5000 0.0.0.0:* LISTEN 0 10 127.0.0.1:4244 0.0.0.0:* LISTEN 0 10 127.0.0.1:4250 0.0.0.0:* > ps xua | grep osmo build 43728 0.0 0.0 13452 6904 ? S 00:05 0:00 ./src/osmo-bsc_nat/osmo-bsc_nat -l 127.0.0.1 -c /build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg build 43735 0.0 0.0 2576 912 ? S 00:05 0:00 /bin/sh -c ps xua | grep osmo build 43737 0.0 0.0 3700 1820 ? S 00:05 0:00 grep osmo Socket: in 1 tries, connected to 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33080), raddr=('127.0.0.1', 4244)> (1 sockets open) Socket: closing 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33080), raddr=('127.0.0.1', 4244)> (0 sockets open) Process returned code: -15 ok testUssdSideChannelProvider (__main__.TestVTYNAT.testUssdSideChannelProvider) ... Launching: PWD=/build/openbsc './src/osmo-bsc_nat/osmo-bsc_nat' '-l' '127.0.0.1' '-c' '/build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg' > ls -l /proc/43427/fd total 0 lr-x------ 1 build build 64 Jun 30 00:04 0 -> pipe:[201944326] l-wx------ 1 build build 64 Jun 30 00:04 1 -> pipe:[201944327] l-wx------ 1 build build 64 Jun 30 00:04 2 -> pipe:[201944328] l-wx------ 1 build build 64 Jun 30 00:04 3 -> /dev/null > ss -tn State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess > ss -tln State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess LISTEN 0 1 0.0.0.0:5001 0.0.0.0:* LISTEN 0 1 127.0.0.1:5000 0.0.0.0:* LISTEN 0 10 127.0.0.1:4244 0.0.0.0:* LISTEN 0 10 127.0.0.1:4250 0.0.0.0:* > ps xua | grep osmo build 43738 0.0 0.0 13452 7480 ? S 00:05 0:00 ./src/osmo-bsc_nat/osmo-bsc_nat -l 127.0.0.1 -c /build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg build 43745 0.0 0.0 2576 948 ? S 00:05 0:00 /bin/sh -c ps xua | grep osmo build 43747 0.0 0.0 3700 1744 ? S 00:05 0:00 grep osmo Socket: in 1 tries, connected to 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33088), raddr=('127.0.0.1', 4244)> (1 sockets open) Connected to 127.0.0.1:5001 Expecting ID_GET request Going to send ID_RESP response Going to send PING request Expecting PONG response Going to shut down connection Expecting EOF Socket: closing 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33088), raddr=('127.0.0.1', 4244)> (0 sockets open) Process returned code: -15 ok testVtyTree (__main__.TestVTYNAT.testVtyTree) ... Launching: PWD=/build/openbsc './src/osmo-bsc_nat/osmo-bsc_nat' '-l' '127.0.0.1' '-c' '/build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg' > ls -l /proc/43427/fd total 0 lr-x------ 1 build build 64 Jun 30 00:04 0 -> pipe:[201944326] l-wx------ 1 build build 64 Jun 30 00:04 1 -> pipe:[201944327] l-wx------ 1 build build 64 Jun 30 00:04 2 -> pipe:[201944328] l-wx------ 1 build build 64 Jun 30 00:04 3 -> /dev/null > ss -tn State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess > ss -tln State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess LISTEN 0 1 0.0.0.0:5001 0.0.0.0:* LISTEN 0 1 127.0.0.1:5000 0.0.0.0:* LISTEN 0 10 127.0.0.1:4244 0.0.0.0:* LISTEN 0 10 127.0.0.1:4250 0.0.0.0:* > ps xua | grep osmo build 43748 0.0 0.0 13452 6916 ? S 00:05 0:00 ./src/osmo-bsc_nat/osmo-bsc_nat -l 127.0.0.1 -c /build/openbsc/tests/../doc/examples/osmo-bsc_nat/osmo-bsc-nat.cfg build 43755 0.0 0.0 2576 932 ? S 00:05 0:00 /bin/sh -c ps xua | grep osmo build 43757 0.0 0.0 3700 1900 ? S 00:05 0:00 grep osmo Socket: in 1 tries, connected to 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33102), raddr=('127.0.0.1', 4244)> (1 sockets open) Socket: closing 127.0.0.1:4244 <socket.socket fd=4, family=2, type=1, proto=0, laddr=('127.0.0.1', 33102), raddr=('127.0.0.1', 4244)> (0 sockets open) Process returned code: -15 ok ====================================================================== ERROR: testBSCreload (__main__.TestVTYNAT.testBSCreload) ---------------------------------------------------------------------- Traceback (most recent call last): File "/build/openbsc/tests/./vty_test_runner.py", line 803, in testBSCreload msc_socket, msc = nat_msc_test(self, ip, port, verbose=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/build/openbsc/tests/./vty_test_runner.py", line 1047, in nat_msc_test raise Exception("VTY reports MSC is connected, but I haven't" Exception: VTY reports MSC is connected, but I haven't connected yet: '127.0.0.1' 5522 ---------------------------------------------------------------------- Ran 33 tests in 80.721s FAILED (errors=1) make[5]: *** [Makefile:717: python-tests] Error 1 make[5]: Leaving directory '/build/openbsc/tests' make[4]: *** [Makefile:726: check-local] Error 2 make[4]: Leaving directory '/build/openbsc/tests' make[3]: *** [Makefile:575: check-am] Error 2 make[3]: Leaving directory '/build/openbsc/tests' make[2]: *** [Makefile:425: check-recursive] Error 1 make[2]: Leaving directory '/build/openbsc/tests' make[1]: Leaving directory '/build/openbsc' make[1]: *** [Makefile:457: check-recursive] Error 1 make: *** [Makefile:756: check] Error 2 + cat-testlogs.sh Build step 'Execute shell' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 3970993 killed; [ssh-agent] Stopped. Archiving artifacts

1 1

Jenkins build became unstable: ttcn3-mme-test-ogs #358
by jenkins＠lists.osmocom.org 29 Jun '24

29 Jun '24

See <https://jenkins.osmocom.org/jenkins/job/ttcn3-mme-test-ogs/358/display/redi…>

1 0

Build failed in Jenkins: update-osmo-ci-on-slaves » rpi4-raspbian11build-ansible-1 #2365
by jenkins＠lists.osmocom.org 28 Jun '24

28 Jun '24

See <https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/label=rpi4…> Changes: ------------------------------------------ Started by upstream project "update-osmo-ci-on-slaves" build number 2365 originally caused by: Started by timer Running as SYSTEM Building remotely on rpi4-raspbian11build-ansible-1 (rpi4-raspbian11) in workspace /home/osmocom-build/jenkins/workspace/update-osmo-ci-on-slaves/label/rpi4-raspbian11build-ansible-1 FATAL: java.io.IOException: Unexpected termination of the channel java.io.EOFException at java.base/java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2915) at java.base/java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3410) at java.base/java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:954) at java.base/java.io.ObjectInputStream.<init>(ObjectInputStream.java:392) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:142) at hudson.remoting.Command.readFrom(Command.java:128) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:61) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:75) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to rpi4-raspbian11build-ansible-1 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1787) at hudson.remoting.Request.call(Request.java:199) at hudson.remoting.Channel.call(Channel.java:1002) at hudson.FilePath.act(FilePath.java:1192) at hudson.FilePath.act(FilePath.java:1181) at hudson.FilePath.mkdirs(FilePath.java:1372) at hudson.model.AbstractProject.checkout(AbstractProject.java:1242) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:649) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:85) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1895) at hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:442) Caused: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:346) at hudson.remoting.Channel.terminate(Channel.java:1083) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:90)

1 1

Build failed in Jenkins: update-osmo-ci-on-slaves » rpi4-raspbian11build-ansible-2 #2365
by jenkins＠lists.osmocom.org 28 Jun '24

28 Jun '24

See <https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/label=rpi4…> Changes: ------------------------------------------ Started by upstream project "update-osmo-ci-on-slaves" build number 2365 originally caused by: Started by timer Running as SYSTEM Building remotely on rpi4-raspbian11build-ansible-2 (rpi4-raspbian11) in workspace /home/osmocom-build/jenkins/workspace/update-osmo-ci-on-slaves/label/rpi4-raspbian11build-ansible-2 FATAL: java.io.IOException: Unexpected termination of the channel java.io.EOFException at java.base/java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2915) at java.base/java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3410) at java.base/java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:954) at java.base/java.io.ObjectInputStream.<init>(ObjectInputStream.java:392) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:142) at hudson.remoting.Command.readFrom(Command.java:128) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:61) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:75) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to rpi4-raspbian11build-ansible-2 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1787) at hudson.remoting.Request.call(Request.java:199) at hudson.remoting.Channel.call(Channel.java:1002) at hudson.FilePath.act(FilePath.java:1192) at hudson.FilePath.act(FilePath.java:1181) at hudson.FilePath.mkdirs(FilePath.java:1372) at hudson.model.AbstractProject.checkout(AbstractProject.java:1242) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:649) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:85) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1895) at hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:442) Caused: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:346) at hudson.remoting.Channel.terminate(Channel.java:1083) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:90)

1 1

Build failed in Jenkins: update-osmo-ci-on-slaves » rpi4-raspbian11build-ansible-3 #2365
by jenkins＠lists.osmocom.org 28 Jun '24

28 Jun '24

See <https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/label=rpi4…> Changes: ------------------------------------------ Started by upstream project "update-osmo-ci-on-slaves" build number 2365 originally caused by: Started by timer Running as SYSTEM Building remotely on rpi4-raspbian11build-ansible-3 (rpi4-raspbian11) in workspace /home/osmocom-build/jenkins/workspace/update-osmo-ci-on-slaves/label/rpi4-raspbian11build-ansible-3 FATAL: java.io.IOException: Unexpected termination of the channel java.io.EOFException at java.base/java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2915) at java.base/java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3410) at java.base/java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:954) at java.base/java.io.ObjectInputStream.<init>(ObjectInputStream.java:392) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:142) at hudson.remoting.Command.readFrom(Command.java:128) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:61) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:75) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to rpi4-raspbian11build-ansible-3 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1787) at hudson.remoting.Request.call(Request.java:199) at hudson.remoting.Channel.call(Channel.java:1002) at hudson.FilePath.act(FilePath.java:1192) at hudson.FilePath.act(FilePath.java:1181) at hudson.FilePath.mkdirs(FilePath.java:1372) at hudson.model.AbstractProject.checkout(AbstractProject.java:1242) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:649) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:85) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1895) at hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:442) Caused: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:346) at hudson.remoting.Channel.terminate(Channel.java:1083) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:90)

1 1

Build failed in Jenkins: update-osmo-ci-on-slaves » lx2-raspbian11build-ansible #2365
by jenkins＠lists.osmocom.org 28 Jun '24

28 Jun '24

See <https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/label=lx2-…> Changes: ------------------------------------------ Started by upstream project "update-osmo-ci-on-slaves" build number 2365 originally caused by: Started by timer Running as SYSTEM Building remotely on lx2-raspbian11build-ansible (rpi4-raspbian11) in workspace /home/osmocom-build/jenkins/workspace/update-osmo-ci-on-slaves/label/lx2-raspbian11build-ansible FATAL: java.io.IOException: Unexpected termination of the channel java.io.EOFException at java.base/java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2915) at java.base/java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3410) at java.base/java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:954) at java.base/java.io.ObjectInputStream.<init>(ObjectInputStream.java:392) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:142) at hudson.remoting.Command.readFrom(Command.java:128) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:61) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:75) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to lx2-raspbian11build-ansible at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1787) at hudson.remoting.Request.call(Request.java:199) at hudson.remoting.Channel.call(Channel.java:1002) at hudson.FilePath.act(FilePath.java:1192) at hudson.FilePath.act(FilePath.java:1181) at hudson.FilePath.mkdirs(FilePath.java:1372) at hudson.model.AbstractProject.checkout(AbstractProject.java:1242) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:649) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:85) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1895) at hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:442) Caused: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:346) at hudson.remoting.Channel.terminate(Channel.java:1083) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:90)

1 1

Build failed in Jenkins: update-osmo-ci-on-slaves » simtester #2365
by jenkins＠lists.osmocom.org 28 Jun '24

28 Jun '24

See <https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/label=simt…> Changes: ------------------------------------------ Started by upstream project "update-osmo-ci-on-slaves" build number 2365 originally caused by: Started by timer Running as SYSTEM Building remotely on simtester in workspace /home/jenkins/workspace/update-osmo-ci-on-slaves/label/simtester FATAL: java.io.IOException: Unexpected termination of the channel java.io.EOFException at java.base/java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2915) at java.base/java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3410) at java.base/java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:954) at java.base/java.io.ObjectInputStream.<init>(ObjectInputStream.java:392) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:142) at hudson.remoting.Command.readFrom(Command.java:128) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:61) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:75) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to simtester at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1787) at hudson.remoting.Request.call(Request.java:199) at hudson.remoting.Channel.call(Channel.java:1002) at hudson.FilePath.act(FilePath.java:1192) at hudson.FilePath.act(FilePath.java:1181) at hudson.FilePath.mkdirs(FilePath.java:1372) at hudson.model.AbstractProject.checkout(AbstractProject.java:1242) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:649) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:85) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1895) at hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:442) Caused: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:346) at hudson.remoting.Channel.terminate(Channel.java:1083) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:90)

1 1

Build failed in Jenkins: update-osmo-ci-on-slaves » gtp0-deb10fr #2365
by jenkins＠lists.osmocom.org 28 Jun '24

28 Jun '24

See <https://jenkins.osmocom.org/jenkins/job/update-osmo-ci-on-slaves/label=gtp0…> Changes: ------------------------------------------ Started by upstream project "update-osmo-ci-on-slaves" build number 2365 originally caused by: Started by timer Running as SYSTEM Building remotely on gtp0-deb10fr (hdlc dahdi) in workspace /home/osmocom-build/jenkins/workspace/update-osmo-ci-on-slaves/label/gtp0-deb10fr FATAL: java.io.IOException: Unexpected termination of the channel java.io.EOFException at java.base/java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2915) at java.base/java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3410) at java.base/java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:954) at java.base/java.io.ObjectInputStream.<init>(ObjectInputStream.java:392) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:142) at hudson.remoting.Command.readFrom(Command.java:128) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:61) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:75) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to gtp0-deb10fr at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1787) at hudson.remoting.Request.call(Request.java:199) at hudson.remoting.Channel.call(Channel.java:1002) at hudson.FilePath.act(FilePath.java:1192) at hudson.FilePath.act(FilePath.java:1181) at hudson.FilePath.mkdirs(FilePath.java:1372) at hudson.model.AbstractProject.checkout(AbstractProject.java:1242) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:649) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:85) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1895) at hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:442) Caused: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:346) at hudson.remoting.Channel.terminate(Channel.java:1083) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:90)

1 1

2025

2024

2023

2022

2021

2020

2019

jenkins-notifications June 2024