GitHub pull request #3626 of commit f6acf5feecfc0e2858e27f8635d3202feb1880e2, no merge conflicts.
Running as SYSTEM
Setting status of f6acf5feecfc0e2858e27f8635d3202feb1880e2 to PENDING with url <a href='https://buildbot.iovisor.org/jenkins/job/bcc-pr/1154/'>https://buildbot.iovisor.org/jenkins/job/bcc-pr/1154/</a> and message: 'Build started for merge commit.'
Building on master in workspace /var/lib/jenkins/workspace/bcc-pr
The recommended git tool is: NONE
No credentials specified
 &gt; git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/bcc-pr/.git # 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 --version # 'git version 2.17.1'
 &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/3626/merge^{commit} # timeout=10
Checking out Revision 6239930becc76f210aec7425eceef2856732c6b2 (refs/remotes/origin/pr/3626/merge)
 &gt; git config core.sparsecheckout # timeout=10
 &gt; git checkout -f 6239930becc76f210aec7425eceef2856732c6b2 # timeout=10
Commit message: "Merge f6acf5feecfc0e2858e27f8635d3202feb1880e2 into 44fc17fc8ca0a53f37e82aa82a6a000ec28384c4"
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=fc28/' class='model-link'>bcc-pr » fc28</a>
Triggering <a href='/jenkins/job/bcc-pr/label=ubuntu1604/' class='model-link'>bcc-pr » ubuntu1604</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=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>
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-e39/' class='model-link'>ubuntu1804-slave-e39</a>’ is offline
Configuration <a href='/jenkins/job/bcc-pr/label=ubuntu1804/' class='model-link'>bcc-pr » ubuntu1804</a> is still in the queue: All nodes of label ‘<a href='/jenkins/label/ubuntu1804/' class='model-link'>ubuntu1804</a>’ are 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-1b1/' class='model-link'>ubuntu1804-slave-1b1</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’
‘iovisor-repo’ doesn’t have label ‘ubuntu1804’
‘ubuntu1710-slave-226’ doesn’t have label ‘ubuntu1804’
‘<a href='/jenkins/computer/ubuntu1804-slave-1b1/' class='model-link'>ubuntu1804-slave-1b1</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=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
<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=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
Setting status of f6acf5feecfc0e2858e27f8635d3202feb1880e2 to SUCCESS with url <a href='https://buildbot.iovisor.org/jenkins/job/bcc-pr/1154/'>https://buildbot.iovisor.org/jenkins/job/bcc-pr/1154/</a> and message: 'Build finished. '
Finished: SUCCESS