As you probably saw on the Cactus Users' mailing list, we are moving certain thorns between repositories today, and we are switching the Cactus repositories from cvs to svn. While the thorns themselves (with a few exceptions) should not change at all, this change will require testing, and you can help us:
- Wait for Frank's email that things are ready for testing - Frank will describe the new repository structure
- Test checking out and building from new thorn locations - both anonymous and read/write access - test this for many architectures (both workstations and the big LONI/TeraGrid systems) - Look over CactusCode and EinsteinToolkit web sites - update download instructions and all thorn lists - use GetComponents instead of GetCactus - look at Utilities as well
- Run test suites, compare output before and after - Begin running a few production simulations as well
If you are helping, please keep in touch via frequent emails to the public mailing lists.
-erik
Hi,
On Mon, Apr 19, 2010 at 10:57:32AM -0500, Erik Schnetter wrote:
- Wait for Frank's email that things are ready for testing
- Frank will describe the new repository structure
All the thorn repositories moved. Everyone should have read permissions. Write permissions and commit messages will need some more time. There will be separate emails about that.
I prepared a (long) thornlist (in the new format) for the repositories before and after the move. You can use this as template to check out things. You can find them here:
https://svn.cactuscode.org/scratch/
Remember: use GetComponents for those thorn lists. You can get it from here: https://svn.cactuscode.org/Utilities/trunk/Scripts/GetComponents
What can already now be done is to check - does anonymous checkout work for everyone? - can you checkout all thorns? - update your personal thorn list and try to rebuild -> please do that in a fresh directory to - be sure everything is new - not overwrite anything on your side
If everyone does this it will also give the server a pretty good stress-test - which means it might be slower than 'usual' because of this.
You can also use the following links for a rough overview of the new repository structure:
https://svn.cactuscode.org/ https://svn.einsteintoolkit.org/
Frank
I got the following error message when retrieving GetComponents:
$ wget https://svn.cactuscode.org/Utilities/trunk/Scripts/GetComponents --2010-04-19 14:59:58-- https://svn.cactuscode.org/Utilities/trunk/Scripts/GetComponents Resolving svn.cactuscode.org... 130.39.21.22 Connecting to svn.cactuscode.org|130.39.21.22|:443... connected. ERROR: cannot verify svn.cactuscode.org's certificate, issued by `/DC=edu/DC=lsu/CN=Louisiana State University Issuing CA 1': Unable to locally verify the issuer's authority. To connect to svn.cactuscode.org insecurely, use `--no-check-certificate'. Unable to establish SSL connection.
With --no-check-certificate flag, it works fine but prints a warning message about the certification. How do we avoid this certification issue otherwise?
Thanks, Bruno.
Frank Loeffler wrote:
Hi,
On Mon, Apr 19, 2010 at 10:57:32AM -0500, Erik Schnetter wrote:
- Wait for Frank's email that things are ready for testing
- Frank will describe the new repository structure
All the thorn repositories moved. Everyone should have read permissions. Write permissions and commit messages will need some more time. There will be separate emails about that.
I prepared a (long) thornlist (in the new format) for the repositories before and after the move. You can use this as template to check out things. You can find them here:
https://svn.cactuscode.org/scratch/
Remember: use GetComponents for those thorn lists. You can get it from here: https://svn.cactuscode.org/Utilities/trunk/Scripts/GetComponents
What can already now be done is to check
- does anonymous checkout work for everyone?
- can you checkout all thorns?
- update your personal thorn list and try to rebuild -> please do that in a fresh directory to
- be sure everything is new
- not overwrite anything on your side
If everyone does this it will also give the server a pretty good stress-test - which means it might be slower than 'usual' because of this.
You can also use the following links for a rough overview of the new repository structure:
https://svn.cactuscode.org/ https://svn.einsteintoolkit.org/
Frank
Users mailing list Users@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/users
On Mon, Apr 19, 2010 at 03:08:31PM -0400, Bruno Coutinho Mundim wrote:
I got the following error message when retrieving GetComponents:
$ wget https://svn.cactuscode.org/Utilities/trunk/Scripts/GetComponents --2010-04-19 14:59:58-- https://svn.cactuscode.org/Utilities/trunk/Scripts/GetComponents Resolving svn.cactuscode.org... 130.39.21.22 Connecting to svn.cactuscode.org|130.39.21.22|:443... connected. ERROR: cannot verify svn.cactuscode.org's certificate, issued by `/DC=edu/DC=lsu/CN=Louisiana State University Issuing CA 1': Unable to locally verify the issuer's authority. To connect to svn.cactuscode.org insecurely, use `--no-check-certificate'. Unable to establish SSL connection.
When was that? I corrected that within the last hour or so.
Frank
We've been distributing the GetComponents (and GetCactus) tool from CVS via the web page
http://www.cactuscode.org/download/GetComponents
Can we keep this location with the move to SVN (for one thing, it shortens a long URL).
On Apr 19, 2010, at 7:21 PM, Frank Loeffler wrote:
On Mon, Apr 19, 2010 at 03:08:31PM -0400, Bruno Coutinho Mundim wrote:
I got the following error message when retrieving GetComponents:
$ wget https://svn.cactuscode.org/Utilities/trunk/Scripts/GetComponents --2010-04-19 14:59:58-- https://svn.cactuscode.org/Utilities/trunk/Scripts/GetComponents Resolving svn.cactuscode.org... 130.39.21.22 Connecting to svn.cactuscode.org|130.39.21.22|:443... connected. ERROR: cannot verify svn.cactuscode.org's certificate, issued by `/DC=edu/DC=lsu/CN=Louisiana State University Issuing CA 1': Unable to locally verify the issuer's authority. To connect to svn.cactuscode.org insecurely, use `--no-check-certificate'. Unable to establish SSL connection.
When was that? I corrected that within the last hour or so.
Frank
Users mailing list Users@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/users
On Mon, Apr 19, 2010 at 07:40:48PM -0400, Allen Gabrielle wrote:
http://www.cactuscode.org/download/GetComponents
Can we keep this location with the move to SVN (for one thing, it shortens a long URL).
We can certainly think about setting something up which updates this from the original place in svn.
Frank
That was 5 hours ago. Somehow my message didn't go through the users list... Now it works fine.
Thanks, Bruno.
Frank Loeffler wrote:
On Mon, Apr 19, 2010 at 03:08:31PM -0400, Bruno Coutinho Mundim wrote:
I got the following error message when retrieving GetComponents:
$ wget https://svn.cactuscode.org/Utilities/trunk/Scripts/GetComponents --2010-04-19 14:59:58-- https://svn.cactuscode.org/Utilities/trunk/Scripts/GetComponents Resolving svn.cactuscode.org... 130.39.21.22 Connecting to svn.cactuscode.org|130.39.21.22|:443... connected. ERROR: cannot verify svn.cactuscode.org's certificate, issued by `/DC=edu/DC=lsu/CN=Louisiana State University Issuing CA 1': Unable to locally verify the issuer's authority. To connect to svn.cactuscode.org insecurely, use `--no-check-certificate'. Unable to establish SSL connection.
When was that? I corrected that within the last hour or so.
Frank
Hello Frank,
What can already now be done is to check
- does anonymous checkout work for everyone?
- can you checkout all thorns?
I can check out the thorn, but the flesh does not check out properly.
I downloaded a fresh copy of GetComponents
wget --no-check-certificate https://svn.cactuscode.org/Utilities/trunk/Scripts/GetComponents -O GetComponents
where the no-check-certificate is necessary because wget cannot check the LSU certificate then download the all_new.th thornlist with wget.
I then do a
./GetComponents --root AllNew all_new.th
which claims to download the flesh:
----------------------------------------------------------------- Updating module: Cactus from repository: https://svn.cactuscode.org/flesh/trunk located in: AllNew under: . ... 280 components checked out successfully. 0 components updated successfully.
Time Elapsed: 14 minutes, 22 seconds
But the Cactus tree does not seem to contain the flesh:
[rhaas3@phys44230 rhaas3]$ cd AllNew/ [rhaas3@phys44230 AllNew]$ ls arrangements git-repos par simfactory utils
Yours, Roland
Hi,
On Mon, Apr 19, 2010 at 05:08:59PM -0400, Roland Haas wrote:
where the no-check-certificate is necessary because wget cannot check the LSU certificate then download the all_new.th thornlist with wget.
This is fixed now.
./GetComponents --root AllNew all_new.th
But the Cactus tree does not seem to contain the flesh:
Please try again. We had some temporary problems with the server. I just tried it successfully.
thanks for the reports, Frank
users@lists.einsteintoolkit.org
-
Allen Gabrielle -
Bruno Coutinho Mundim -
Erik Schnetter -
Frank Loeffler -
Roland Haas