-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
CondCore/CondDB/test/testConnectionPool.cpp accessing obsolete squid service #18246
Comments
A new Issue was created by @DrDaveD . @davidlange6, @Dr15Jones, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign db
… On Apr 6, 2017, at 6:28 PM, cmsbuild ***@***.***> wrote:
A new Issue was created by @DrDaveD .
@davidlange6, @Dr15Jones, @smuzaffar can you please review it and eventually sign/assign? Thanks.
cms-bot commands are listed here cms-sw/cmssw#13029
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
New categories assigned: db @ggovi you have been requested to review this Pull request/Issue and eventually sign? Thanks |
@ggovi Please look at this with high priority. The t0.pac interface will soon be decomissioned and I assume all tests running this code will start breaking. |
Thanks, @ggovi. Do you know if this test is run only on the latest code? Or is it also run on old code? Clearly it has to be run only at CERN since a CERN configuration is hard-coded. |
I found this test in 80X, 90X and 91X ( not in 71X ). Any other release cycle to check? |
It's good to hear that it doesn't go back to very old code. I just hope that people aren't using it for older released versions in those release cycles, but instead are only using it with the latest integration builds. |
+1 |
This issue is fully signed and ready to be closed. |
CondCore/CondDB/test/testConnectionPool.cpp has a hardcoded frontier configuration, proxyconfigurl=http://cmst0frontier.cern.ch/t0.pac, and that is now obsolete and will soon be decomissioned. The new proxyconfigurl is http://grid-wpad/wpad.dat, but more importantly, why is that connect string hardcoded there at all? It should be using the local configuration from site-local-config.xml like everything else.
Please look at this at high priority, or these tests will start failing soon.
The text was updated successfully, but these errors were encountered: