Description
I don't want to pollute the node issue tracker that soon, so I'm opening a ticket here to track the issues that need to be solved on V8's side.
Here is a fresh CI run of targos/v8-5.4 as reference: https://ci.nodejs.org/job/node-test-commit/4668/
1. Compilation issue on BSD
Already fixed on my branch
See https://codereview.chromium.org/2251603004/
2. Compilation issue on SmartOS
See https://ci.nodejs.org/job/node-test-commit-smartos/3808/nodes=smartos14-32/console
I think it's due to the recent https://codereview.chromium.org/2248393002
3. Windows issue with mkpeephole
See https://ci.nodejs.org/job/node-compile-windows/3798/label=win-vcbt2015/console
@ofrobots: do you have any news about this?
4. FreeBSD issue with test-tick-processor
The process is probably crashing before the skip, at https://github.com/nodejs/node/blob/8ff3d61d8ba90fde01827643db3d87ee97f502e6/test/parallel/test-tick-processor.js#L21-L29
I don't understand what this test is doing so help would be much appreciated here.
Fixed with https://codereview.chromium.org/2268993002
Edit: new CI: https://ci.nodejs.org/job/node-test-commit/4686/
Activity
matthewloring commentedon Aug 19, 2016
cc @nodejs/v8
edit: Hmmm, looks like you cannot cc a team from the parent repository?
targos commentedon Aug 19, 2016
cc @fhinkel and @bnoordhuis in case you're interested
bnoordhuis commentedon Aug 19, 2016
It's possible you need to add
'want_separate_host_toolset_mkpeephole%': 0
in common.gypi like we do forwant_separate_host_toolset
.cc @misterdjules for the smartos build error.
bnoordhuis commentedon Aug 19, 2016
From looking at the stack trace, I suspect that the fix is this:
On freebsd, sem_t is a struct with a couple of uint32_t fields. It only needs dword alignment on 64 bits architectures, not the qword (pointer) alignment that the CHECK currently enforces.
misterdjules commentedon Aug 19, 2016
Will look at this asap.
matthewloring commentedon Aug 19, 2016
Based on @bnoordhuis' comment, it doesn't look like the tick processor failure is an issue in the code that the tick processor is testing but I'm happy to help out with any questions/work related to the test.
misterdjules commentedon Aug 20, 2016
@targos
The following patch fixes the build issue on SmartOS:
ofrobots commentedon Aug 22, 2016
@targos sorry for the late reply, I was on vacation. From the new CI, it seems like that the
common.gypi
suggestion from @bnoordhuis didn't help. I will take a look at this today.targos commentedon Aug 23, 2016
@misterdjules thanks !
cc @mhart for the similar issue with https://ci.nodejs.org/job/node-test-commit-linux/4734/nodes=ubuntu1604_docker_alpine34-64/console
Do you know if there is a V8 macro applicable to this platform ?
ofrobots commentedon Aug 23, 2016
@targos: I have submitted this CL for the
mkpeephole
issue on windows: https://codereview.chromium.org/2276733002.targos commentedon Aug 24, 2016
@ofrobots your fix seems to break the build on my local machine (Linux).
Running ./configure:
ofrobots commentedon Aug 24, 2016
@targos: You still need
want_separate_host_toolset_mkpeephole%': 0
in common.gypi as @bnoordhuis suggested above.targos commentedon Aug 24, 2016
@ofrobots I'm still seeing this error with
'want_separate_host_toolset_mkpeephole%': 0;
ofrobots commentedon Aug 25, 2016
@targo: It seems that the variable definition in
common.gypi
is having no effect. Here's how I "fixed" it: ofrobots@b4ad793 on my branch. Today was my day off so I didn't have too much time to look into whycommon.gypi
is not having an effect.targos commentedon Aug 25, 2016
OK thanks!
New CI: https://ci.nodejs.org/job/node-test-commit/4759/
158 remaining items