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

Build CMSSW_8_0_0 #13332

Closed
davidlange6 opened this issue Feb 17, 2016 · 22 comments
Closed

Build CMSSW_8_0_0 #13332

davidlange6 opened this issue Feb 17, 2016 · 22 comments

Comments

@davidlange6
Copy link
Contributor

Ok- the chance of me having both the HCAL and L1 parts working is really small, but I don't have much to lose.

@cmsbuild
Copy link
Contributor

Request received. I will start to build the release after one of the following approve the issue: @smuzaffar, @Degano, @slava77, @davidlange6. You can do this by writing "+1" in a comment.
You can also ask me to begin to build cmssw-tool-conf first ( Cannot be done for patch releases ). To do this write "build cmssw-tool-conf" in a comment. I will start to build cmssw-tool-conf and then wait for the "+1" to start the build of the release.

@davidlange6
Copy link
Contributor Author

+1

@cmsbuild
Copy link
Contributor

Release created: https://github.com/cms-sw/cmssw/releases/tag/CMSSW_8_0_0. The tag was created on top of branch: https://github.com/cms-sw/cmssw/tree/CMSSW_8_0_X

@cmsbuild
Copy link
Contributor

Queuing Jenkins build for the following architectures: slc7_aarch64_gcc530, slc6_amd64_gcc493, fc22_ppc64le_gcc530, slc6_amd64_gcc530, slc7_amd64_gcc530
You can abort the build by writing "Abort" in a comment. I will delete the release, the cmssw and cmsdist tag, and close the issue. You can't abort the upload once at least one achitecture is being uploaded.
If you are building cmssw-tool-conf first, I will wait for each acrhitecture to finish to start the build of cmssw.

@cmsbuild
Copy link
Contributor

The build has started for slc7_aarch64_gcc530 in moonshot-arm64-14.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/529/console
CMSDIST Branch: IB/CMSSW_8_0_X/gcc530, PKGTOOLS Branch: V00-22-XX

@cmsbuild
Copy link
Contributor

The build has started for slc6_amd64_gcc530 in vocms0302.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/532/console
CMSDIST Branch: IB/CMSSW_8_0_X/gcc530, PKGTOOLS Branch: V00-22-XX

@cmsbuild
Copy link
Contributor

The build has started for slc6_amd64_gcc493 in vocms0301.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/531/console
CMSDIST Branch: IB/CMSSW_8_0_X/stable, PKGTOOLS Branch: V00-22-XX

@cmsbuild
Copy link
Contributor

The build has started for slc7_amd64_gcc530 in cmsbuild08.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/533/console
CMSDIST Branch: IB/CMSSW_8_0_X/gcc530, PKGTOOLS Branch: V00-22-XX

@cmsbuild
Copy link
Contributor

The was an error for slc7_aarch64_gcc530.
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_8_0_0-slc7_aarch64_gcc530/529

@cmsbuild
Copy link
Contributor

The was an error for slc6_amd64_gcc493.
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_8_0_0-slc6_amd64_gcc493/531

@cmsbuild
Copy link
Contributor

The was an error for slc6_amd64_gcc530.
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_8_0_0-slc6_amd64_gcc530/532

@cmsbuild
Copy link
Contributor

The was an error for slc7_amd64_gcc530.
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_8_0_0-slc7_amd64_gcc530/533

@cmsbuild
Copy link
Contributor

The build has started for fc22_ppc64le_gcc530 in power8-02.
You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/534/console
CMSDIST Branch: IB/CMSSW_8_0_X/gcc530, PKGTOOLS Branch: V00-22-XX

@cmsbuild
Copy link
Contributor

The was an error for fc22_ppc64le_gcc530.
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_8_0_0-fc22_ppc64le_gcc530/534

@davidlt
Copy link
Contributor

davidlt commented Feb 18, 2016

Looks to be due to ROOT change done yesterday. TColor constructor is ambiguous. Simply put compiler does not understand which one to use, CMSSW needs to be more explicit.

  /build/cmsbuild/jenkins-workarea/workspace/build-any-ib/w/tmp/BUILDROOT/d4fbf691c2bed54d41ff754d77c7eeb1/opt/cmssw/slc6_amd64_gcc493/cms/cmssw/CMSSW_8_0_X_2016-02-17-1400/src/Fireworks/Core/src/FWColorManager.cc:230:50: error: call of overloaded 'TColor(unsigned int, const float&, const float&, const float&)' is ambiguous
      new TColor(index++,(*it)[0],(*it)[1],(*it)[2]);
                                                  ^
/build/cmsbuild/jenkins-workarea/workspace/build-any-ib/w/tmp/BUILDROOT/d4fbf691c2bed54d41ff754d77c7eeb1/opt/cmssw/slc6_amd64_gcc493/cms/cmssw/CMSSW_8_0_X_2016-02-17-1400/src/Fireworks/Core/src/FWColorManager.cc:230:50: note: candidates are:
In file included from /build/cmsbuild/jenkins-workarea/workspace/build-any-ib/w/tmp/BUILDROOT/d4fbf691c2bed54d41ff754d77c7eeb1/opt/cmssw/slc6_amd64_gcc493/cms/cmssw/CMSSW_8_0_X_2016-02-17-1400/src/Fireworks/Core/src/FWColorManager.cc:17:0:
/build/cmsbuild/jenkins-workarea/workspace/build-any-ib/w/slc6_amd64_gcc493/lcg/root/6.06.00-ikhhed5/include/TColor.h:41:4: note: TColor::TColor(Float_t, Float_t, Float_t, Float_t)
    TColor(Float_t r, Float_t g, Float_t b, Float_t a = 1);
    ^
/build/cmsbuild/jenkins-workarea/workspace/build-any-ib/w/slc6_amd64_gcc493/lcg/root/6.06.00-ikhhed5/include/TColor.h:40:4: note: TColor::TColor(Int_t, Float_t, Float_t, Float_t, const char*, Float_t)
    TColor(Int_t color, Float_t r, Float_t g, Float_t b, const char *name="", Float_t a = 1);
    ^

It's one of latest commits in root branch. Here they added extra constructor: https://root.cern.ch/gitweb?p=root.git;a=commitdiff;h=8ebf9227adcf410134a5733086616ed70de55da3

@davidlt
Copy link
Contributor

davidlt commented Feb 18, 2016

I don't think that you need to revert ROOT change, it's easier and faster to fix those 4 errors in CMSSW.

@davidlange6
Copy link
Contributor Author

Right. Looks like two places to update (we wanted the tool or update for dqm)


From: davidlt [notifications@github.com]
Sent: 18 February 2016 07:22
To: cms-sw/cmssw
Cc: David Lange
Subject: Re: [cmssw] Build CMSSW_8_0_0 (#13332)

Looks to be due to ROOT change done yesterday. TColor constructor is ambiguous. Simply put compiler does not understand which one to use, CMSSW needs to be more explicit.

/build/cmsbuild/jenkins-workarea/workspace/build-any-ib/w/tmp/BUILDROOT/d4fbf691c2bed54d41ff754d77c7eeb1/opt/cmssw/slc6_amd64_gcc493/cms/cmssw/CMSSW_8_0_X_2016-02-17-1400/src/Fireworks/Core/src/FWColorManager.cc:230:50: error: call of overloaded 'TColor(unsigned int, const float&, const float&, const float&)' is ambiguous
new TColor(index++,(_it)[0],(_it)[1],(it)[2]);
^
/build/cmsbuild/jenkins-workarea/workspace/build-any-ib/w/tmp/BUILDROOT/d4fbf691c2bed54d41ff754d77c7eeb1/opt/cmssw/slc6_amd64_gcc493/cms/cmssw/CMSSW_8_0_X_2016-02-17-1400/src/Fireworks/Core/src/FWColorManager.cc:230:50: note: candidates are:
In file included from /build/cmsbuild/jenkins-workarea/workspace/build-any-ib/w/tmp/BUILDROOT/d4fbf691c2bed54d41ff754d77c7eeb1/opt/cmssw/slc6_amd64_gcc493/cms/cmssw/CMSSW_8_0_X_2016-02-17-1400/src/Fireworks/Core/src/FWColorManager.cc:17:0:
/build/cmsbuild/jenkins-workarea/workspace/build-any-ib/w/slc6_amd64_gcc493/lcg/root/6.06.00-ikhhed5/include/TColor.h:41:4: note: TColor::TColor(Float_t, Float_t, Float_t, Float_t)
TColor(Float_t r, Float_t g, Float_t b, Float_t a = 1);
^
/build/cmsbuild/jenkins-workarea/workspace/build-any-ib/w/slc6_amd64_gcc493/lcg/root/6.06.00-ikhhed5/include/TColor.h:40:4: note: TColor::TColor(Int_t, Float_t, Float_t, Float_t, const char
, Float_t)
TColor(Int_t color, Float_t r, Float_t g, Float_t b, const char *name="", Float_t a = 1);
^

It's one of latest commits in root branch. Here they added extra constructor: https://root.cern.ch/gitweb?p=root.git;a=commitdiff;h=8ebf9227adcf410134a5733086616ed70de55da3


Reply to this email directly or view it on GitHubhttps://github.com//issues/13332#issuecomment-185560365.

@davidlange6
Copy link
Contributor Author

abort


From: cmsbuild [notifications@github.com]
Sent: 18 February 2016 06:02
To: cms-sw/cmssw
Cc: David Lange
Subject: Re: [cmssw] Build CMSSW_8_0_0 (#13332)

The was an error for fc22_ppc64le_gcc530.
You can see the log here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_8_0_0-fc22_ppc64le_gcc530/534


Reply to this email directly or view it on GitHubhttps://github.com//issues/13332#issuecomment-185543552.

@cmsbuild
Copy link
Contributor

Deleting CMSSW_8_0_0:

-Release successfully deleted

-cmssw tag CMSSW_8_0_0 successfully deleted.

-I was not able to delete the cmsdist tag REL/CMSSW_8_0_0/slc7_aarch64_gcc530. Probably it had not been created.

-I was not able to delete the cmsdist tag REL/CMSSW_8_0_0/fc22_ppc64le_gcc530. Probably it had not been created.

-I was not able to delete the cmsdist tag REL/CMSSW_8_0_0/slc7_amd64_gcc530. Probably it had not been created.

-I was not able to delete the cmsdist tag REL/CMSSW_8_0_0/slc6_amd64_gcc530. Probably it had not been created.

-I was not able to delete the cmsdist tag REL/CMSSW_8_0_0/slc6_amd64_gcc493. Probably it had not been created.

You must create a new issue to start over the build.

@davidlt
Copy link
Contributor

davidlt commented Feb 18, 2016

I will see if I can come up with PR now.

@davidlt
Copy link
Contributor

davidlt commented Feb 18, 2016

Will make PR in few minutes.

@davidlt
Copy link
Contributor

davidlt commented Feb 18, 2016

Here: #13335

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

No branches or pull requests

3 participants