Console Output

Started by upstream project "buildsystem" build number 1474
originally caused by:
 Started by user Vincent Sanders
Building remotely on ciworker0 (x86_64-linux-gnu runner) in workspace /var/lib/jenkins/workspace/librosprite
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.netsurf-browser.org/librosprite.git # timeout=10
Fetching upstream changes from git://git.netsurf-browser.org/librosprite.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress git://git.netsurf-browser.org/librosprite.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 019b9c168a050db136d127083d91238b2b5c29fc (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 019b9c168a050db136d127083d91238b2b5c29fc
 > git rev-list 019b9c168a050db136d127083d91238b2b5c29fc # timeout=10
 > git tag -a -f -m Jenkins Build #256 jenkins-librosprite-256 # timeout=10
Triggering librosprite ? i686-w64-mingw32
Triggering librosprite ? arm-riscos-gnueabi
Triggering librosprite ? arm-unknown-riscos
Triggering librosprite ? x86_64-linux-gnu
Triggering librosprite ? x86_64-unknown-freebsd14.0
Triggering librosprite ? m5475-atari-mint
Triggering librosprite ? m68k-atari-mint
librosprite ? i686-w64-mingw32 completed with result SUCCESS
Configuration librosprite ? arm-riscos-gnueabi is still in the queue: Waiting for next available executor on ciworker2
librosprite ? arm-riscos-gnueabi completed with result SUCCESS
librosprite ? arm-unknown-riscos completed with result SUCCESS
librosprite ? x86_64-linux-gnu completed with result SUCCESS
librosprite ? x86_64-unknown-freebsd14.0 completed with result SUCCESS
Configuration librosprite ? m5475-atari-mint is still in the queue: Waiting for next available executor on ciworker1
librosprite ? m5475-atari-mint completed with result SUCCESS
librosprite ? m68k-atari-mint completed with result SUCCESS
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Triggering a new build of netsurf
Triggering a new build of coverage-librosprite
Triggering a new build of scan-build-librosprite
Finished: SUCCESS