Skip to content

cling PR 169 #745

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

Closed
wants to merge 5 commits into from
Closed

cling PR 169 #745

wants to merge 5 commits into from

Conversation

Axel-Naumann
Copy link
Member

@phsft-bot
Copy link

Starting build on gcc49/centos7, native/mac1012, gcc49/slc6, gcc62/slc6, native/ubuntu14 with flags -Dvc=OFF -Dimt=ON -Dccache=ON
How to customize builds

@bellenot
Copy link
Member

bellenot commented Jul 6, 2017

According to this Appveyor build, this doesn't look to fix any test (not even CodeGeneration/Statics.C):

  Failing Tests (11):
      Cling :: CodeGeneration/Statics.C
      Cling :: CodeGeneration/Symbols.C
      Cling :: CodeGeneration/TLSVars.C
      Cling :: CodeUnloading/PCH/VTablesClingPCH.C
      Cling :: Driver/Gnu.C
      Cling :: Lookup/data.C
      Cling :: Lookup/func.C
      Cling :: NullDeref/MethodCalls.C
      Cling :: Prompt/OutputRedirect.C
      Cling :: Prompt/ValuePrinter/Regression.C
      Cling :: Utils/Transform.C
  
    Expected Passes    : 109
    Expected Failures  : 12
    Unsupported Tests  : 1
    Unexpected Failures: 11

@marsupial
Copy link
Contributor

Appveyor is also saying it is generating a warning which it should not be doing.
What does it do/say when applied locally?
I just tried locally with ELF & Release and it passed...

@marsupial
Copy link
Contributor

And prior Appveyor builds show CodeGeneration/Statics.C was just crashing, so it does fix something.

@bellenot
Copy link
Member

bellenot commented Jul 6, 2017

Sorry @marsupial, I overlooked at the log, I just saw the same tests failing before and after...

@bellenot
Copy link
Member

bellenot commented Jul 6, 2017

BTW, the indentation in this PR is not consistent (sometimes two spaces, sometimes four...)

@marsupial
Copy link
Contributor

I assume you are talking about EmuTLS.cpp?
The original is from compiler-rt, which poached it from gcc.
Keeping the indentation at 4 makes it easier to re-integrate when updates occur.

BTW, could you look at root-project/cling#174

@bellenot
Copy link
Member

bellenot commented Jul 7, 2017

OK, I understand, it makes sense, thanks for the explanation. And see my comment on the PR-174

@vgvassilev
Copy link
Member

vgvassilev commented Jul 13, 2017

Does 177 supersede this one? Shall we close it?

@marsupial
Copy link
Contributor

This is a subset, but crashes OS X & linux too (see test/CodeGeneration/TLSVars.C) so might be worth dealing with on its own as it can easily be taken out of 177.

177 is huge and contains everything necessary for Windows to pass.
(As far as i know https://ci.appveyor.com/project/bellenot/cling/build/1.0.312)

@vgvassilev
Copy link
Member

@phsft-bot build!

@phsft-bot
Copy link

Starting build on centos7/gcc49, mac1012/native, slc6/gcc49, slc6/gcc62, ubuntu14/native with flags -Dvc=OFF -Dimt=ON -Dccache=ON
How to customize builds

@vgvassilev
Copy link
Member

@phsft-bot build with flags -Dclingtest=On

@phsft-bot
Copy link

Starting build on centos7/gcc49, mac1012/native, slc6/gcc49, slc6/gcc62, slc6/gcc62, ubuntu14/native, ubuntu14/native, windows10/vc15 with flags -Dvc=OFF -Dimt=ON -Dccache=ON -Dclingtest=On
How to customize builds

@phsft-bot
Copy link

Build failed on slc6/gcc62.
See console output.

Failing tests:

@phsft-bot
Copy link

Build failed on slc6/gcc49.
See console output.

Failing tests:

@phsft-bot
Copy link

Build failed on ubuntu14/native.
See console output.

Failing tests:

@phsft-bot
Copy link

Build failed on mac1012/native.
See console output.

Warnings:

  • /cvmfs/sft.cern.ch/lcg/releases/R/3.2.5-c8cca/x86_64-mac1012-clang81-opt/lib/R/include/R.h:40:10: warning: non-portable path to file '<RConfig.h>'; specified path differs in case from file name on disk [-Wnonportable-include-path]
  • /cvmfs/sft.cern.ch/lcg/releases/R/3.2.5-c8cca/x86_64-mac1012-clang81-opt/lib/R/include/R_ext/RS.h:29:10: warning: non-portable path to file '<RConfig.h>'; specified path differs in case from file name on disk [-Wnonportable-include-path]
  • /cvmfs/sft.cern.ch/lcg/releases/R/3.2.5-c8cca/x86_64-mac1012-clang81-opt/lib/R/include/Rinternals.h:60:11: warning: non-portable path to file '<RConfig.h>'; specified path differs in case from file name on disk [-Wnonportable-include-path]
  • /cvmfs/sft.cern.ch/lcg/releases/R/3.2.5-c8cca/x86_64-mac1012-clang81-opt/lib/R/library/Rcpp/include/Rcpp/r/headers.h:57:10: warning: non-portable path to file '<RVersion.h>'; specified path differs in case from file name on disk [-Wnonportable-include-path]
  • /cvmfs/sft.cern.ch/lcg/releases/R/3.2.5-c8cca/x86_64-mac1012-clang81-opt/lib/R/include/R_ext/Visibility.h:29:10: warning: non-portable path to file '<RConfig.h>'; specified path differs in case from file name on disk [-Wnonportable-include-path]
  • /cvmfs/sft.cern.ch/lcg/releases/R/3.2.5-c8cca/x86_64-mac1012-clang81-opt/lib/R/include/R.h:40:10: warning: non-portable path to file '<RConfig.h>'; specified path differs in case from file name on disk [-Wnonportable-include-path]
  • /cvmfs/sft.cern.ch/lcg/releases/R/3.2.5-c8cca/x86_64-mac1012-clang81-opt/lib/R/include/R_ext/RS.h:29:10: warning: non-portable path to file '<RConfig.h>'; specified path differs in case from file name on disk [-Wnonportable-include-path]
  • /cvmfs/sft.cern.ch/lcg/releases/R/3.2.5-c8cca/x86_64-mac1012-clang81-opt/lib/R/include/Rinternals.h:60:11: warning: non-portable path to file '<RConfig.h>'; specified path differs in case from file name on disk [-Wnonportable-include-path]
  • /cvmfs/sft.cern.ch/lcg/releases/R/3.2.5-c8cca/x86_64-mac1012-clang81-opt/lib/R/library/Rcpp/include/Rcpp/r/headers.h:57:10: warning: non-portable path to file '<RVersion.h>'; specified path differs in case from file name on disk [-Wnonportable-include-path]
  • /cvmfs/sft.cern.ch/lcg/releases/R/3.2.5-c8cca/x86_64-mac1012-clang81-opt/lib/R/include/R_ext/Visibility.h:29:10: warning: non-portable path to file '<RConfig.h>'; specified path differs in case from file name on disk [-Wnonportable-include-path]

And 10 more

Failing tests:

@phsft-bot
Copy link

Build failed on centos7/gcc49.
See console output.

Failing tests:

@phsft-bot
Copy link

Build failed on slc6/gcc62.
See console output.

Failing tests:

@phsft-bot
Copy link

Build failed on ubuntu14/native.
See console output.

Failing tests:

@Axel-Naumann
Copy link
Member Author

@phsft-bot build with flags -Dclingtest=On now that I've fixed the cling tests.

@phsft-bot
Copy link

Starting build on centos7/gcc49, mac1012/native, slc6/gcc49, slc6/gcc62, slc6/gcc62, ubuntu14/native, ubuntu14/native, windows10/vc15 with flags -Dvc=OFF -Dimt=ON -Dccache=ON -Dclingtest=On
How to customize builds

@phsft-bot
Copy link

Build failed on windows10/vc15.
See console output.

@etejedor
Copy link
Collaborator

@bellenot is it understood why the windows build fails here? It this WIP?

@oshadura
Copy link
Contributor

@phsft-bot build with flags -Dclingtest=On

@phsft-bot
Copy link

Starting build on centos7/gcc49, mac1013/native, slc6/gcc49, slc6/gcc62, slc6/gcc62, ubuntu16/native, ubuntu16/native, windows10/vc15 with flags -Dvc=OFF -Dimt=ON -Dccache=ON -Dclingtest=On
How to customize builds

@phsft-bot
Copy link

Build failed on slc6/gcc49.
See console output.

Failing tests:

@phsft-bot
Copy link

Build failed on slc6/gcc62.
See console output.

Failing tests:

@phsft-bot
Copy link

Build failed on centos7/gcc49.
See console output.

Failing tests:

@phsft-bot
Copy link

Build failed on slc6/gcc62.
See console output.

Failing tests:

@phsft-bot
Copy link

Build failed on ubuntu16/native.
See console output.

Failing tests:

@phsft-bot
Copy link

Build failed on mac1013/native.
See console output.

Failing tests:

@etejedor
Copy link
Collaborator

@bellenot do we need to rescue this PR or it is obsolete?

1 similar comment
@etejedor
Copy link
Collaborator

@bellenot do we need to rescue this PR or it is obsolete?

@lmoneta
Copy link
Member

lmoneta commented Jan 29, 2019

@bellenot do we declare it obsolete ?

@bellenot
Copy link
Member

@moneta I would keep it for the time being (it is not clear what has been taken and what not...)

@eguiraud eguiraud added the stale label Mar 10, 2020
@bellenot bellenot closed this Mar 10, 2020
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

Successfully merging this pull request may close these issues.

9 participants