Task #2168
closedJenkins: FreeBSD 10.1 slave
100%
Description
Deploy FreeBSD 10.1-RELEASE slaves.
Use i386 architecture.
Collect the list of packages needed by projects, so that the deployment can be repeated.
Updated by Lan Wang about 10 years ago
- Assignee changed from Lan Wang to Ashlesh Gawande
Updated by Ashlesh Gawande about 10 years ago
- % Done changed from 0 to 50
Installed Virtual Machines and configured Networking and ssh.
Updated by Ashlesh Gawande about 10 years ago
- Status changed from New to In Progress
Updated by Junxiao Shi almost 10 years ago
FreeBSD 10.1 is released. Shall we change this Task to use 10.1?
Updated by Alex Afanasyev almost 10 years ago
Yes. Let's use 10.1, as it is the latest production release.
Updated by Junxiao Shi almost 10 years ago
- Subject changed from Jenkins: FreeBSD 10.0 slave to Jenkins: FreeBSD 10.1 slave
- Description updated (diff)
Updated by Alex Afanasyev almost 10 years ago
A note.
In order for test cases of ndn-cxx (specifically related to IPv6 DNS) to pass on FreeBSD, it is necessary to configure at least fake IPv6 address.
For example, the following needs to be added to /etc/rc.conf
ifconfig_le0_ipv6="inet6 2001:db8:4672:6565:2026:5043:2d42:5344 prefixlen 64"
The issue is related to some strange issue with Boost.Asio (resolv call) on FreeBSD platform.
Updated by Alex Afanasyev almost 10 years ago
How much RAM and CPUs are allocated for VM? Please make sure it is at least 2.5Gb ram and 1 CPU.
The same question applies to other VMs. Also. Do all three VMs have the same set of resources (they should)?
Updated by Alex Afanasyev almost 10 years ago
http://jenkins.named-data.net/job/ndn-cxx/OS=FreeBSD10/1689/console
I believe this is a memory issue and will go away after we have 2.5 gigs of RAM available.
Updated by Ashlesh Gawande almost 10 years ago
I have given 2 GB to each, I will increase it to 2.5 GB. So is it fine if I restart the machine to do so?
Updated by Ashlesh Gawande almost 10 years ago
Ok I increased the RAM to 2.5 GB on each machine and restarted.
Updated by Ashlesh Gawande almost 10 years ago
I have FreeBSD running on different machine. Can anybody check if this too segfaults at random places?
ssh -p 20003 jenkins@europa.cs.memphis.edu
Updated by Ashlesh Gawande almost 10 years ago
I have installed java on FreeBSD.
When I tried to compile ndn-cxx it said that my version is way old. (I will check why it was working on the old machine). So I updated to gcc49 (using pkg) and had to use the CXX flag to specify gcc49 (I created a symbolic link after that from gcc49 to gcc).
Now it configures fine with C++11 but the compilation fails:
Waf: Entering directory `/usr/home/jenkins/ndn-cxx/build'
[ 60/111] Compiling src/util/ethernet.cpp
../src/util/ethernet.cpp: In member function 'std::string ndn::util::ethernet::Address::toString(char) const':
../src/util/ethernet.cpp:83:3: error: 'snprintf' is not a member of 'std'
std::snprintf(s, sizeof(s), "%02x%c%02x%c%02x%c%02x%c%02x%c%02x",
^
../src/util/ethernet.cpp:83:3: note: suggested alternative:
In file included from /usr/local/lib/gcc49/include/c++/cstdio:42:0,
from /usr/local/lib/gcc49/include/c++/fstream:41,
from ./../src/common-pch.hpp:37,
from <command-line>:0:
/usr/local/lib/gcc49/gcc/i386-portbld-freebsd10.0/4.9.3/include-fixed/stdio.h:293:6: note: 'snprintf'
int snprintf(char * __restrict, size_t, const char * __restrict,
^
Waf: Leaving directory `/usr/home/jenkins/ndn-cxx/build'
Build failed
-> task in 'ndn-cxx' failed (exit status 1):
{task 689374316: cxx ethernet.cpp -> ethernet.cpp.2.o}
['/usr/bin/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-fPIC', '-include', '/usr/home/jenkins/ndn-cxx/build/ndn-cxx.2', '-I/usr/hom$
This looks related to: http://redmine.named-data.net/issues/2299?
Updated by Alex Afanasyev almost 10 years ago
- Related to Task #2404: Incorrect compiler defaults on FreeBSD platform added
Updated by Alex Afanasyev almost 10 years ago
The issues are related, but the problem does not exist if compiled with clang compiler (the default compiler for FreeBSD 10 platform). While I will fix the issue, I prefer using platform-provided compiler, especially for CI.
Updated by Alex Afanasyev almost 10 years ago
I have enabled FreeBSD slave for ndn-cxx and ndns project. Seem to be working now.
Is it a permanent slave or you intent do move it somewhere else?
We also need at least two copies of the slave, as we do with all other slaves (this enables us to parallelize builds)
Updated by Ashlesh Gawande almost 10 years ago
This is not permanent but this machine will be here for some time. As we get other machines ready I will install the machines and update here.
Updated by Ashlesh Gawande over 9 years ago
Okay can anybody test if arcturus machine still segfaults (I removed two RAMs, wanted to make sure those were the bad ones before adding new ones): FreeBSD: port 20023 jenkins@arcturus.cs.memphis.edu?
Updated by Ashlesh Gawande over 9 years ago
I will wait some more to see if there are any more connection issues before closing this.
Updated by Junxiao Shi over 9 years ago
- Status changed from In Progress to Closed
- % Done changed from 50 to 100
Updated by Alex Afanasyev almost 9 years ago
- Status changed from Closed to Feedback
I'm experiencing numerous unit test failures of ndn-cxx on FreeBSD 10.1(32bit) slave, as well as related unit-test failure of NLSR.
I'm removing the slave from NLSR CI build until figuring out what's going on.
Updated by Alex Afanasyev almost 9 years ago
- Status changed from Feedback to In Progress
I will update the slave to 10.2 and select a non-default compiler.
Updated by Alex Afanasyev almost 9 years ago
- Status changed from In Progress to Feedback
Updated by Alex Afanasyev almost 9 years ago
- Status changed from Feedback to Closed
The FreeBSD slave is back in business and is attached to NLSR project. I'm considering adding it to other projects as well, but it can wait.