May 2025 - jenkins-notifications

Build failed in Jenkins: master-osmo-rp2040-firmware » a1=default,a2=default,a3=default,a4=default,osmocom-master #3

by jenkins＠lists.osmocom.org

See <https://jenkins.osmocom.org/jenkins/job/master-osmo-rp2040-firmware/a1=defa…> Changes: ------------------------------------------ Started by upstream project "master-osmo-rp2040-firmware" build number 3 originally caused by: Started by an SCM change Running as SYSTEM Building remotely on build4-deb12build-ansible (ttcn3 obs osmo-gsm-tester-build ttcn3_with_linux_6.1_or_higher qemu io_uring osmocom-gerrit coverity osmocom-master) in workspace <https://jenkins.osmocom.org/jenkins/job/master-osmo-rp2040-firmware/a1=defa…> [ssh-agent] Looking for ssh-agent implementation... $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-37yatffm5boP/agent.302608 SSH_AGENT_PID=302610 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: <https://jenkins.osmocom.org/jenkins/job/master-osmo-rp2040-firmware/a1=defa…> (osmocom-jenkins) [ssh-agent] Using credentials binaries (OS#5798) The recommended git tool is: NONE No credentials specified > git rev-parse --resolve-git-dir <https://jenkins.osmocom.org/jenkins/job/master-osmo-rp2040-firmware/a1=defa…> # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://gerrit.osmocom.org/osmo-rp2040-firmware # timeout=10 Fetching upstream changes from https://gerrit.osmocom.org/osmo-rp2040-firmware > git --version # timeout=10 > git --version # 'git version 2.39.5' > git fetch --tags --force --progress -- https://gerrit.osmocom.org/osmo-rp2040-firmware +refs/heads/*:refs/remotes/origin/* # timeout=10 Checking out Revision f326f3c310ea44a3c7ca131f83a31a1d52cd470c (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f f326f3c310ea44a3c7ca131f83a31a1d52cd470c # timeout=10 Commit message: "CMakeLists.txt: set project: osmo-rp2040-firmware" First time build. Skipping changelog. [osmocom-master] $ /bin/sh -xe /tmp/jenkins14946346435585415219.sh + docker pull registry.osmocom.org/osmocom-build/debian-bookworm-rp2040 Using default tag: latest latest: Pulling from osmocom-build/debian-bookworm-rp2040 Digest: sha256:9b001057ddd19f671b8e67b34706a7936e225c5edb326b9868811423a299d74a Status: Image is up to date for registry.osmocom.org/osmocom-build/debian-bookworm-rp2040:latest registry.osmocom.org/osmocom-build/debian-bookworm-rp2040:latest + readlink -f /tmp/ssh-37yatffm5boP/agent.302608 + docker run --rm=true --cap-add SYS_PTRACE --security-opt seccomp=/home/osmocom-build/osmo-ci/_docker_playground/seccomp_profile.json --ulimit fsize=1000000000 -e ASCIIDOC_WARNINGS_CHECK=1 -e HOME=/build -e IS_MASTER_BUILD=1 -e JOB_NAME=master-osmo-rp2040-firmware/a1=default,a2=default,a3=default,a4=default,label=osmocom-master -e MAKE=make -e OSMOPY_DEBUG_TCP_SOCKETS=1 -e OSMO_GSM_MANUALS_DIR=/opt/osmo-gsm-manuals -e PARALLEL_MAKE=-j 12 -e PUBLISH=1 -e SSH_AUTH_SOCK=/ssh-agent -e WITH_MANUALS=1 -w /build -i -u build -v /tmp/ssh-37yatffm5boP/agent.302608:/ssh-agent -v /home/osmocom-build/osmo-ci:/osmo-ci:ro -v <https://jenkins.osmocom.org/jenkins/job/master-osmo-rp2040-firmware/a1=defa…>:/build -v /home/osmocom-build/.ssh:/home/build/.ssh:ro registry.osmocom.org/osmocom-build/debian-bookworm-rp2040 /usr/bin/timeout 30m contrib/jenkins.sh + mkdir build mkdir: cannot create directory 'build': File exists Build step 'Execute shell' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 302610 killed; [ssh-agent] Stopped. Archiving artifacts

5 months, 1 week

1
0
0 0

Jenkins build became unstable: ttcn3-stp-test #2047

by jenkins＠lists.osmocom.org

See <https://jenkins.osmocom.org/jenkins/job/ttcn3-stp-test/2047/display/redirec…>

5 months, 1 week

1
0
0 0

Build failed in Jenkins: ttcn3-bts-test-latest #2403

by jenkins＠lists.osmocom.org

See <https://jenkins.osmocom.org/jenkins/job/ttcn3-bts-test-latest/2403/display/…> Changes: ------------------------------------------ [...truncated 4.42 MiB...] <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.039993'> <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.041906'> <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.013445'> <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.041582'> <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.041531'> <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.037747'> <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.041834'> <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.039109'> <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.036136'> <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.035370'> <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.040439'> <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.028208'> <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.035343'> <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.024032'> <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.029384'> <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.024319'> <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.039012'> <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.027196'> <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.039759'> <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.038847'> <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.036558'> <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.043496'> <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.040177'> <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.032676'> <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.041174'> <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.036684'> <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.037131'> <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.036310'> <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.036722'> <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.041688'> <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.040604'> <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.038726'> <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.036881'> <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.041751'> <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.037421'> <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.037903'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_ASCI.ttcn:422 BTS_Tests_ASCI control part BTS_Tests_ASCI.ttcn:83 TC_vbs_notification testcase </failure> </testcase> <testcase classname='BTS_Tests_ASCI' name='TC_vgcs_uplink_free_and_busy' time='15.039635'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_ASCI.ttcn:423 BTS_Tests_ASCI control part BTS_Tests_ASCI.ttcn:190 TC_vgcs_uplink_free_and_busy testcase </failure> </testcase> <testcase classname='BTS_Tests_ASCI' name='TC_vgcs_talker_fail' time='15.040067'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_ASCI.ttcn:424 BTS_Tests_ASCI control part BTS_Tests_ASCI.ttcn:289 TC_vgcs_talker_fail testcase </failure> </testcase> <testcase classname='BTS_Tests_ASCI' name='TC_vgcs_talker_est_rel' time='15.027722'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_ASCI.ttcn:425 BTS_Tests_ASCI control part BTS_Tests_ASCI.ttcn:333 TC_vgcs_talker_est_rel testcase </failure> </testcase> <testcase classname='BTS_Tests_ASCI' name='TC_vgcs_listener_det' time='15.038048'> <failure type='fail-verdict'>"BTS_Tests.ttcn:291 : Timeout waiting for RSL bring up" BTS_Tests_ASCI.ttcn:426 BTS_Tests_ASCI control part BTS_Tests_ASCI.ttcn:411 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.

5 months, 1 week

1
12
0 0

Jenkins build became unstable: ttcn3-pcu-test-sns-asan #193

by jenkins＠lists.osmocom.org

See <https://jenkins.osmocom.org/jenkins/job/ttcn3-pcu-test-sns-asan/193/display…>

5 months, 1 week

1
1
0 0

Build failed in Jenkins: master-osmo-trx » --with-neon,0,a3=default,a4=default,raspbian #7977

by jenkins＠lists.osmocom.org

See <https://jenkins.osmocom.org/jenkins/job/master-osmo-trx/INSTR=--with-neon,W…> Changes: ------------------------------------------ Started by upstream project "master-osmo-trx" build number 7977 originally caused by: Started by timer Running as SYSTEM Building remotely on rpi4-raspbian12build-ansible-1 (raspbian) in workspace /home/osmocom-build/jenkins/workspace/master-osmo-trx/INSTR/--with-neon/WITH_MANUALS/0/a3/default/a4/default/label/raspbian [ssh-agent] Looking for ssh-agent implementation... $ ssh-agent FATAL: [ssh-agent] Unable to start agent java.io.IOException: Unexpected EOF at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:111) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:62) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to rpi4-raspbian12build-ansible-1 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1923) at hudson.remoting.Request.call(Request.java:204) at hudson.remoting.Channel.call(Channel.java:1111) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1121) at hudson.Launcher$ProcStarter.start(Launcher.java:507) at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.exec.ExecRemoteAgent.<init>(ExecRemoteAgent.java:52) at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.<init>(SSHAgentBuildWrapper.java:309) at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:246) at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:223) at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:75) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1833) at PluginClassLoader for matrix-project//hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:446) Caused: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:358) at hudson.remoting.Channel.terminate(Channel.java:1196) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:95) Caused: java.io.IOException: [ssh-agent] Unable to start agent at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:251) at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:223) at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:75) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1833) at PluginClassLoader for matrix-project//hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:446) ERROR: Step ‘Archive the artifacts’ failed: no workspace for master-osmo-trx/INSTR=--with-neon,WITH_MANUALS=0,a3=default,a4=default,label=raspbian #7977

5 months, 1 week

1
1
0 0

Build failed in Jenkins: master-osmo-trx » --with-neon-vfpv4,0,a3=default,a4=default,raspbian #7977

by jenkins＠lists.osmocom.org

See <https://jenkins.osmocom.org/jenkins/job/master-osmo-trx/INSTR=--with-neon-v…> Changes: ------------------------------------------ Started by upstream project "master-osmo-trx" build number 7977 originally caused by: Started by timer Running as SYSTEM Building remotely on rpi4-raspbian12build-ansible-3 (raspbian) in workspace /home/osmocom-build/jenkins/workspace/master-osmo-trx/INSTR/--with-neon-vfpv4/WITH_MANUALS/0/a3/default/a4/default/label/raspbian [ssh-agent] Looking for ssh-agent implementation... $ ssh-agent FATAL: [ssh-agent] Unable to start agent java.io.IOException: Unexpected EOF at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:111) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:62) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to rpi4-raspbian12build-ansible-3 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1923) at hudson.remoting.Request.call(Request.java:204) at hudson.remoting.Channel.call(Channel.java:1111) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1121) at hudson.Launcher$ProcStarter.start(Launcher.java:507) at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.exec.ExecRemoteAgent.<init>(ExecRemoteAgent.java:52) at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.<init>(SSHAgentBuildWrapper.java:309) at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:246) at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:223) at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:75) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1833) at PluginClassLoader for matrix-project//hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:446) Caused: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:358) at hudson.remoting.Channel.terminate(Channel.java:1196) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:95) Caused: java.io.IOException: [ssh-agent] Unable to start agent at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:251) at PluginClassLoader for ssh-agent//com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:223) at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:75) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1833) at PluginClassLoader for matrix-project//hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:446) ERROR: Step ‘Archive the artifacts’ failed: no workspace for master-osmo-trx/INSTR=--with-neon-vfpv4,WITH_MANUALS=0,a3=default,a4=default,label=raspbian #7977

5 months, 1 week