GitHub pull request #3227 of commit f0dba496eefdf4170c19c83fc9fbd22d38488215, no merge conflicts.
Running as SYSTEM
Setting status of f0dba496eefdf4170c19c83fc9fbd22d38488215 to PENDING with url <a href='https://buildbot.iovisor.org/jenkins/job/bcc-pr/807/'>https://buildbot.iovisor.org/jenkins/job/bcc-pr/807/</a> and message: 'Build started for merge commit.'
Building on master in workspace /var/lib/jenkins/workspace/bcc-pr
No credentials specified
 &gt; git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 &gt; git config remote.origin.url <a href='https://github.com/iovisor/bcc.git'>https://github.com/iovisor/bcc.git</a> # timeout=10
Fetching upstream changes from <a href='https://github.com/iovisor/bcc.git'>https://github.com/iovisor/bcc.git</a>
 &gt; git --version # timeout=10
 &gt; git fetch --tags --progress -- <a href='https://github.com/iovisor/bcc.git'>https://github.com/iovisor/bcc.git</a> +refs/pull/*:refs/remotes/origin/pr/* # timeout=10
 &gt; git rev-parse refs/remotes/origin/pr/3227/merge^{commit} # timeout=10
 &gt; git rev-parse refs/remotes/origin/origin/pr/3227/merge^{commit} # timeout=10
Checking out Revision b8b1ec73faad421a5510b70ee55e7f3d76503731 (refs/remotes/origin/pr/3227/merge)
 &gt; git config core.sparsecheckout # timeout=10
 &gt; git checkout -f b8b1ec73faad421a5510b70ee55e7f3d76503731 # timeout=10
Commit message: "Merge f0dba496eefdf4170c19c83fc9fbd22d38488215 into a9f97691519b5225fa8d9fb45b35ccf23e029f1c"
First time build. Skipping changelog.
Triggering <a href='/jenkins/job/bcc-pr/label=ubuntu1804/' class='model-link'>bcc-pr » ubuntu1804</a>
Triggering <a href='/jenkins/job/bcc-pr/label=fc27/' class='model-link'>bcc-pr » fc27</a>
Triggering <a href='/jenkins/job/bcc-pr/label=ubuntu1710/' class='model-link'>bcc-pr » ubuntu1710</a>
Triggering <a href='/jenkins/job/bcc-pr/label=fc25/' class='model-link'>bcc-pr » fc25</a>
Triggering <a href='/jenkins/job/bcc-pr/label=fc26/' class='model-link'>bcc-pr » fc26</a>
Triggering <a href='/jenkins/job/bcc-pr/label=fc28/' class='model-link'>bcc-pr » fc28</a>
Triggering <a href='/jenkins/job/bcc-pr/label=ubuntu1604/' class='model-link'>bcc-pr » ubuntu1604</a>
Configuration <a href='/jenkins/job/bcc-pr/label=ubuntu1804/' class='model-link'>bcc-pr » ubuntu1804</a> is still in the queue: ‘<a href='/jenkins/computer/ubuntu1804-slave-abc/' class='model-link'>ubuntu1804-slave-abc</a>’ is offline
Configuration <a href='/jenkins/job/bcc-pr/label=ubuntu1804/' class='model-link'>bcc-pr » ubuntu1804</a> is still in the queue: ‘<a href='/jenkins/computer/ubuntu1804-slave-9ca/' class='model-link'>ubuntu1804-slave-9ca</a>’ is offline
Configuration <a href='/jenkins/job/bcc-pr/label=ubuntu1804/' class='model-link'>bcc-pr » ubuntu1804</a> is still in the queue: ‘Jenkins’ doesn’t have label ‘ubuntu1804’
‘fedora25-slave-a45’ doesn’t have label ‘ubuntu1804’
‘fedora26-slave-dc9’ doesn’t have label ‘ubuntu1804’
‘fedora27-slave-aa0’ doesn’t have label ‘ubuntu1804’
‘fedora28-slave-db5’ doesn’t have label ‘ubuntu1804’
‘iovisor-repo’ doesn’t have label ‘ubuntu1804’
‘ubuntu1604-slave-978’ doesn’t have label ‘ubuntu1804’
‘ubuntu1710-slave-386’ doesn’t have label ‘ubuntu1804’
‘<a href='/jenkins/computer/ubuntu1804-slave-9ca/' class='model-link'>ubuntu1804-slave-9ca</a>’ is offline
<a href='/jenkins/job/bcc-pr/label=ubuntu1804/' class='model-link'>bcc-pr » ubuntu1804</a> completed with result SUCCESS
<a href='/jenkins/job/bcc-pr/label=fc27/' class='model-link'>bcc-pr » fc27</a> completed with result SUCCESS
<a href='/jenkins/job/bcc-pr/label=ubuntu1710/' class='model-link'>bcc-pr » ubuntu1710</a> completed with result SUCCESS
<a href='/jenkins/job/bcc-pr/label=fc25/' class='model-link'>bcc-pr » fc25</a> completed with result SUCCESS
<a href='/jenkins/job/bcc-pr/label=fc26/' class='model-link'>bcc-pr » fc26</a> completed with result SUCCESS
<a href='/jenkins/job/bcc-pr/label=fc28/' class='model-link'>bcc-pr » fc28</a> completed with result SUCCESS
<a href='/jenkins/job/bcc-pr/label=ubuntu1604/' class='model-link'>bcc-pr » ubuntu1604</a> completed with result SUCCESS
Setting status of f0dba496eefdf4170c19c83fc9fbd22d38488215 to SUCCESS with url <a href='https://buildbot.iovisor.org/jenkins/job/bcc-pr/807/'>https://buildbot.iovisor.org/jenkins/job/bcc-pr/807/</a> and message: 'Build finished. '
Finished: SUCCESS