Project

General

Profile

Actions

Bug #3321

closed

CI script does not rebuild ndn-cxx after Boost upgrade

Added by Davide Pesavento over 8 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
Build
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
0.50 h

Description

.jenkins.d/00-deps.sh would upgrade Boost libraries to a new version if it's available.

However, after Boost upgrade, .jenkins.d/01-ndn-cxx.sh does not rebuild ndn-cxx unless a new commit has been merged.

This can cause undefined behavior such as segfaults, because ndn-cxx is linked against old Boost libraries, while NFD is linked against new Boost libraries.

Actions #1

Updated by Junxiao Shi over 8 years ago

This is probably not ndnsec problem, but due to Boost upgrade on the slave.

NFD build script won't rebuild ndn-cxx unless ndn-cxx has new commits merged.
After a Boost upgrade, old ndnsec is looking for old Boost libraries, but they no longer exist.

If the above is true, this problem would disappear when a new commit is merged into ndn-cxx.

Actions #2

Updated by Davide Pesavento over 8 years ago

Let's merge http://gerrit.named-data.net/2559 ASAP then.

Actions #3

Updated by Davide Pesavento over 8 years ago

  • Status changed from New to Resolved

This is fixed now.

Actions #4

Updated by Davide Pesavento over 8 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
Actions #5

Updated by Junxiao Shi over 8 years ago

  • Subject changed from ndnsec segfaults on all Jenkins OS X slaves to CI script does not rebuild ndn-cxx after Boost upgrade
  • Description updated (diff)
  • Category set to Build
  • Status changed from Closed to New
  • Assignee deleted (Alex Afanasyev)
  • Priority changed from Urgent to Low
  • Target version deleted (v0.4)
  • Start date set to 11/05/2015
  • % Done changed from 100 to 0

Original report:

e.g. http://jenkins.named-data.net/job/NFD/3378/OS=OSX-10.11/console

+ ndnsec-keygen /tmp/jenkins/OSX-10.11-csu-10001
+ ndnsec-install-cert -
/usr/local/bin/ndnsec-install-cert: line 4: 27694 Segmentation fault: 11  `dirname "$0"`/ndnsec cert-install "$@"
/usr/local/bin/ndnsec-keygen: line 4: 27693 Segmentation fault: 11  `dirname "$0"`/ndnsec key-gen "$@"
Build step 'Execute shell' marked build as failure

This is currently preventing all NFD integrations from succeeding.


Reopen because root cause is not solved.

Actions #6

Updated by Davide Pesavento about 7 years ago

  • Start date deleted (11/05/2015)
Actions #7

Updated by Junxiao Shi almost 7 years ago

  • Assignee set to Junxiao Shi
  • Target version set to v0.6
  • % Done changed from 0 to 100
  • Estimated time set to 0.50 h
Actions #8

Updated by Davide Pesavento almost 7 years ago

  • Status changed from New to In Progress
  • % Done changed from 100 to 50

The same is needed in ndn-tools.

Actions #9

Updated by Junxiao Shi almost 7 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 50 to 100

https://gerrit.named-data.net/3907 copies from NFD to ndn-tools.

Actions #10

Updated by Junxiao Shi almost 7 years ago

It turns out NFD's script made a mistake so that it fails to detect the latest ndn-cxx commit.
I've fixed it in https://gerrit.named-data.net/3909, and updated the ndn-tools Change.

Actions #12

Updated by Junxiao Shi almost 7 years ago

  • Status changed from Code review to Closed
Actions

Also available in: Atom PDF