Repository navigation
FreeBSD 10.1: build fails #324
Copy link
Copy link
Closed
aliscco/alisco-node
#232Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.freebsdIssues and PRs related to the FreeBSD platform.Issues and PRs related to the FreeBSD platform.
Description
Activity
/cc @indutny
I have 2 FreeBSD boxes from Voxer to hook up to CI but it's going to have to wait post 1.0.0 for now, having the tests pass prior to 1.0.0 would be really nice though, if possible.
- added a commit that references this issue
on Jan 13, 2015 See https://github.com/iojs/io.js/pull/332/files for a fix. Still has lots of test failures :)
After lots of fixes:
=== release test-http-default-encoding === Path: parallel/test-http-default-encoding 200 Command: out/Release/iojs /usr/home/indutny/io.js/test/parallel/test-http-default-encoding.js === release test-http-request-end === Path: parallel/test-http-request-end 200 Command: out/Release/iojs /usr/home/indutny/io.js/test/parallel/test-http-request-end.js --- TIMEOUT --- === release test-net-better-error-messages-port-hostname === Path: parallel/test-net-better-error-messages-port-hostname Command: out/Release/iojs /usr/home/indutny/io.js/test/parallel/test-net-better-error-messages-port-hostname.js --- TIMEOUT --- === release test-net-connect-immediate-finish === Path: parallel/test-net-connect-immediate-finish Command: out/Release/iojs /usr/home/indutny/io.js/test/parallel/test-net-connect-immediate-finish.js --- TIMEOUT --- === release test-child-process-execsync === Path: sequential/test-child-process-execsync assert.js:100 throw new assert.AssertionError({ ^ AssertionError: false == true at Object.<anonymous> (/usr/home/indutny/io.js/test/sequential/test-child-process-execsync.js:28:3) at Module._compile (module.js:446:26) at Object.Module._extensions..js (module.js:464:10) at Module.load (module.js:341:32) at Function.Module._load (module.js:296:12) at Function.Module.runMain (module.js:487:10) at startup (node.js:111:16) at node.js:809:3 Command: out/Release/iojs /usr/home/indutny/io.js/test/sequential/test-child-process-execsync.js [02:27|% 100|+ 785|- 5]: DoneShould be better now.
Just for posterity: https://codereview.chromium.org/839053004
- addedbuildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.freebsdIssues and PRs related to the FreeBSD platform.Issues and PRs related to the FreeBSD platform.
on Sep 2, 2015
Metadata
Metadata
Assignees
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.freebsdIssues and PRs related to the FreeBSD platform.Issues and PRs related to the FreeBSD platform.
Couldn't find any other open bugs about clang compatibility, but this error probably just affects FreeBSD:
V8 seems to call
g++instead ofc++(ratherclang++) which makes the build fail. If I set CC/CPP/CXX environment flags it at least builds, but fails here:This is FreeBSD builder 10.1-RELEASE amd64, clang 3.4.1.