Trac December 2010

trac@lists.einsteintoolkit.org

1 participants
102 discussions

Re: [ET Trac] [Einstein Toolkit] #40: cleanup Library builds
by Einstein Toolkit 30 Dec '10

30 Dec '10

#40: cleanup Library builds --------------------------+------------------------------------------------- Reporter: knarf | Owner: eschnett Type: enhancement | Status: closed Priority: minor | Milestone: Component: Cactus | Version: Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by eschnett): * status: accepted => closed * resolution: => fixed Comment: Done. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/40#comment:6> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #179: libxml has to be updated
by Einstein Toolkit 30 Dec '10

30 Dec '10

#179: libxml has to be updated --------------------+------------------------------------------------------- Reporter: knarf | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | --------------------+------------------------------------------------------- libxml has to be updated, because of a security problem - should also be done for last released version. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4008 -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/179> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #171: Doesn't work when Python is installed as /usr/local/bin/python
by Einstein Toolkit 30 Dec '10

30 Dec '10

#171: Doesn't work when Python is installed as /usr/local/bin/python ------------------------+--------------------------------------------------- Reporter: eschnett | Owner: mthomas Type: defect | Status: new Priority: blocker | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- SimFactory doesn't seem to work when Python is installed as /usr/local/bin/python. This is the case e.g. on VIP at the RZG. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/171> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #178: New command that runs non-interactively
by Einstein Toolkit 29 Dec '10

29 Dec '10

#178: New command that runs non-interactively -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: mthomas Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- SimFactory should offer a command that is halfway in between "submit" and run". This command should start a simulation immediately, but should run it in the background while redirecting stdout and stderr to the usual locations in the simulation's output directory. Technically, this command would be on the same level as "submit", while "run" would reside at a lower level. For example, "run" would expect an active simulation (and would not activate a simulation), while this new command would activate the simulation. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/178> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #72: GetComponents misplace ML_BSSN_Test repo
by Einstein Toolkit 28 Dec '10

28 Dec '10

#72: GetComponents misplace ML_BSSN_Test repo ---------------------+------------------------------------------------------ Reporter: bmundim | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Other | Version: Keywords: | ---------------------+------------------------------------------------------ Hi, I just ran the following to get my thornlist updated: ./GetComponents --root ET_2010_11 -a -u einsteintoolkit.th and despite GetComponents returning successful: 0 components checked out successfully. 164 components updated successfully. it checked out ML_BSSN_Test again and misplaced it at the same level as the $ROOT directory: ls einsteintoolkit.th ET_2010_11 GetComponents ML_BSSN_Test Thanks, Bruno. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/72> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #138: GetComponents should use "git pull --rebase" for updating
by Einstein Toolkit 28 Dec '10

28 Dec '10

#138: GetComponents should use "git pull --rebase" for updating ---------------------------+------------------------------------------------ Reporter: eschnett | Owner: ian.hinder@… Type: defect | Status: new Priority: major | Milestone: Component: GetComponents | Version: Keywords: | ---------------------------+------------------------------------------------ To update a git repository, one should issue the following commands in this order: git stash git pull --rebase git stash apply If this is not done, the update either fails, or generates many additional patches to handle merge conflicts. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/138> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #139: Existing symbolic links not deleted
by Einstein Toolkit 28 Dec '10

28 Dec '10

#139: Existing symbolic links not deleted ---------------------------+------------------------------------------------ Reporter: eschnett | Owner: eric9 Type: defect | Status: new Priority: major | Milestone: Component: GetComponents | Version: Keywords: | ---------------------------+------------------------------------------------ I had a case where a git repository did not exist any more, but the symbolic links pointing into the git repository were still there. GetComponents then checked out the repository, and then got confused -- it created links inside the repository (which it is not supposed to modify!) pointing nowhere. I think ln should be called as "ln -nsf", or the link (if it exists) should be deleted before the new link is created. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/139> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #148: Eliminate git clone --depth 1 or provide a work around it
by Einstein Toolkit 28 Dec '10

28 Dec '10

#148: Eliminate git clone --depth 1 or provide a work around it -------------------------------------+-------------------------------------- Reporter: bmundim | Owner: eric9 Type: enhancement | Status: new Priority: major | Milestone: Component: GetComponents | Version: Keywords: git clone shallow depth | -------------------------------------+-------------------------------------- Eliminate the following statement (and the ones using $shallow) in GetComponents my $shallow = ' --depth 1'; or provide an alternative solution. The user should have the option for *not* creating a shallow clone of his/her git repositories. Thanks, Bruno. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/148> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #174: Remove cd semaphore from GetComponents
by Einstein Toolkit 28 Dec '10

28 Dec '10

#174: Remove cd semaphore from GetComponents ---------------------------+------------------------------------------------ Reporter: eschnett | Owner: eric9 Type: defect | Status: new Priority: major | Milestone: Component: GetComponents | Version: Keywords: | ---------------------------+------------------------------------------------ GetComponents uses a semaphore that decides which task can cd into a subdirectory. This limits parallelism, since in essence only one task can cd into (and presumably thus access) a repository. Furthermore, using semaphores is a tedious and complex way to handle parallelism. I suggest to remove the semaphore, and instead not use cd within GetComponents at all. Instead, run_command should take care of this. For example, instead of if ($PARALLEL) {$cd_sem->down()} chdir("$orig_dir/$ROOT/repos/$git_repo"); my $err = run_command("git checkout --track -b $branch origin/$branch"); chdir("$orig_dir"); if ($PARALLEL) {$cd_sem->up()} I would write my $err = run_command("cd $orig_dir/$ROOT/repos/$git_repo && git checkout --track -b $branch origin/$branch"); which is four lines shorter, doesn't use semaphores, and doesn't have to handle semaphores and "cd'ing back" in error clean-up code. I've omitted the error clean-up code in the above; indeed in the example i'm looking at, this cleanup code neither releases the semaphore nor cds back into the original directory. Using cd this way may also avoid all problems where thorns are accidentally checked out into the wrong directory. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/174> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #168: Document "direct" version of sim submit
by Einstein Toolkit 24 Dec '10

24 Dec '10

#168: Document "direct" version of sim submit ------------------------+--------------------------------------------------- Reporter: eschnett | Owner: mthomas Type: defect | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- "sim submit" can be called in a direct manner, e.g. as sim submit PARFILE WALLTIME PROCESSORS ... The exact way in which the arguments have to given needs to be document, in particular also in the output of "sim help". -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/168> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

← Newer
1
...
5
6
7
8
9
10
11
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac December 2010