Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ubuntu1204-clang341 has been disabled in CI #685

Closed
MylesBorins opened this issue Apr 18, 2017 · 8 comments
Closed

ubuntu1204-clang341 has been disabled in CI #685

MylesBorins opened this issue Apr 18, 2017 · 8 comments

Comments

@MylesBorins
Copy link
Contributor

Can we get this to skip so we don't have red builds?

@MylesBorins
Copy link
Contributor Author

ping... this is quite annoying... seems like it is failign on v7 too

@gibfahn
Copy link
Member

gibfahn commented Apr 24, 2017

I can add something to the combination filter to skip, but do we know why it's failing on 4/6/7 but not master?

Example of failing build: https://ci.nodejs.org/job/node-test-commit-linux/nodes=ubuntu1204-clang341-64/9384/console

/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/cstddef:51:11: 
error: no member named 'max_align_t' in the global namespace
  using ::max_align_t;
        ~~^

EDIT: Some comments by @bnoordhuis and @MylesBorins which suggest this isn't a new thing, nodejs/node#12392 (comment) nodejs/node#12412 (comment) nodejs/node#12104 (comment)

@targos
Copy link
Member

targos commented Apr 24, 2017

I think this is because of the upgrade to gcc 4.9: #650
It doesn't fail on master because this particular build is skipped.

@gibfahn
Copy link
Member

gibfahn commented Apr 24, 2017

Lots of people running into this elsewhere:
catchorg/Catch2#334
https://askubuntu.com/questions/523613/upgrade-to-gcc-4-9-broke-clang
http://stackoverflow.com/questions/23462950/clang-only-compiles-c11-program-using-boostformat-when-std-c11-option-i

Suggested fixes are "use libc++ instead of libstdc++" and "upgrade to clang 3.5". Not sure why it's intermittent, but it may be to do with ccache.

Given this, are there any objections to changing the existing master skip to include Node 4/6/7?

# clang is only supported in Node versions 7 and lower
MAJOR_VERSION=`cat src/node_version.h |grep "#define NODE_MAJOR_VERSION" | awk '{ print $3}'`
RUN_TESTS="RUN"
echo $SMARTOS_VERSION
if [[ "$nodes" =~ clang && ${MAJOR_VERSION} -gt "7" ]]; then # change to -gt "4"
  RUN_TESTS="DONT_RUN"
fi

Alternatively we could just remove ubuntu1204-clang341-64 from node-test-commit-linux.

@MylesBorins MylesBorins changed the title v4 and v6 fail on ubuntu1204-clang341 v4, v6, v7 fail on ubuntu1204-clang341 May 3, 2017
@MylesBorins MylesBorins changed the title v4, v6, v7 fail on ubuntu1204-clang341 ubuntu1204-clang341 has been disabled in CI May 3, 2017
@MylesBorins
Copy link
Contributor Author

MylesBorins commented May 3, 2017

I have confirmed that the ubuntu1204-clang341 executor is skipped on master and failing on all release lines. I am disabling it from the main CI for now.

I'm unsure who originally set it up, but I've changed this issue to track the progress of adding this executor back to CI

/cc @nodejs/ctc @nodejs/build

@bnoordhuis
Copy link
Member

For posterity: it was added (by Rod?) in response to nodejs/node#8323.

@jbergstroem
Copy link
Member

I updated GCC on the box as a response to @targos on newer V8 requirements too. Then there's this.

@bnoordhuis
Copy link
Member

I'll close this out, the buildbot has been removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants