Task #4301
closedJenkins macOS 10.13 agents
100%
      
      Updated by Eric Newberry about 8 years ago
      
    
    Bump.
I disabled the 10.10 platform on Jenkins because one of the two agents was encountering difficulties and it would not be good to push the entire platform onto only one node (10.10 is also now unsupported per the platform policy, so there's little motivation to fix it or set up a new agent).
      
      Updated by Alex Afanasyev about 8 years ago
      
    
    - Status changed from New to In Progress
 - Assignee set to Alex Afanasyev
 
      
      Updated by Alex Afanasyev about 8 years ago
      
    
    - % Done changed from 0 to 60
 
The slaves are up. Eric, can you try them out?
      
      Updated by Eric Newberry about 8 years ago
      
    
    I've enabled the 10.13 platform on ndn-cxx, ndn-tools, and NFD since these are built fairly regularly (especially ndn-cxx and NFD). Once one of them builds without encountering any weird errors, I'll go ahead and add the platform to the rest of the projects.
      
      Updated by Eric Newberry about 8 years ago
      
    
    ndn-tools had a successful build on 10.13, so I went ahead and enabled 10.13 on all relevant projects, except NLSR. NLSR didn't have 10.12 enabled, so I figured there may have been a specific reason it wasn't enabled. Is there any reason for this?
      
      Updated by Davide Pesavento about 8 years ago
      
    
    - % Done changed from 60 to 90
 
Eric Newberry wrote:
NLSR didn't have 10.12 enabled, so I figured there may have been a specific reason it wasn't enabled. Is there any reason for this?
Maybe it was just an oversight? You should ask NLSR devs directly, I doubt they're reading this issue.
      
      Updated by Ashlesh  Gawande about 8 years ago
      
    
    As far as I know, NLSR doesn't have any particular reason to disable 10.12/10.13 builds.
      
      Updated by Eric Newberry about 8 years ago
      
    
    I've enabled 10.12 and 10.13 for NLSR.
      
      Updated by Ashlesh  Gawande about 8 years ago
      
    
    Thanks Eric! For 10.13 NLSR gets the error while configuring dependencies:
+ brew link --force log4cxx
Error: Could not symlink lib/pkgconfig/liblog4cxx.pc
/usr/local/lib/pkgconfig is not writable.
Linking /usr/local/Cellar/log4cxx/0.10.0_1... 
Build step 'Execute shell' marked build as failure
http://jenkins.named-data.net/job/NLSR/1659/label=OSX-10.13/console
      
      Updated by Davide Pesavento about 8 years ago
      
    
    Maybe you need a sudo in the brew link command? Although I wonder if that step is really necessary...
      
      Updated by Alex Afanasyev about 8 years ago
      
    
    No. There was a strange interaction between brew and our sudo ./waf install (from ndn-cxx).  Fixed now on both new slaves.
      
      Updated by Eric Newberry about 8 years ago
      
    
    One of the agents was broken for ndns builds, but I fixed it by running "brew link log4cxx".
      
      Updated by Davide Pesavento about 8 years ago
      
    
    NFD test Face/TestTcpTransport/PermanentReconnectWithExponentialBackoff fails on 10.13
http://jenkins.named-data.net/job/NFD/5812/OS=OSX-10.13/
      
      Updated by Alex Afanasyev about 8 years ago
      
    
    I saw it, but what we can do to slave except "fixing" TcpTransport in the code?
      
      Updated by Davide Pesavento about 8 years ago
      
    
    - Status changed from In Progress to Code review
 - Target version set to v0.7
 - % Done changed from 90 to 100
 
It turns out that the test case is actually completely broken. It has worked until now for pure coincidence, and because a second mistake in the same test was canceling out the first mistake, so the error was never caught.
      
      Updated by Davide Pesavento about 8 years ago
      
    
    - Status changed from Code review to Closed
 
      
      Updated by Junxiao Shi almost 7 years ago
      
    
    - Status changed from Closed to Feedback
 
I notice that both macOS 10.13 slaves are deployed on the same site. One needs to be moved to fulfill resiliency requirements and prevent downtime due to single site failure.
      
      Updated by Davide Pesavento about 6 years ago
      
    
    - Status changed from Feedback to Closed