#242: build fails after running out of disk space
------------------------+---------------------------------------------------
Reporter: eschnett | Owner: mthomas
Type: defect | Status: new
Priority: major | Milestone:
Component: SimFactory | Version:
Keywords: |
------------------------+---------------------------------------------------
After running out of disk space (and then removing 16 GByte), building
fails on numrel09:
$ ./bin/sim build
DEBUG: Simfactory command: ./bin/../simfactory/lib/sim.py "build"
DEBUG: Version exported
The Simulation Factory: Manage Cactus simulations
Info: defs: /home/eschnett/EinsteinToolkit-hg-
vanilla/simfactory/etc/defs.ini
Info: defs.local: /home/eschnett/EinsteinToolkit-hg-
vanilla/simfactory/etc/defs.local.ini
Info: Executing command: build
Using configuration: sim
Info: Cactus Directory: /home/eschnett/EinsteinToolkit-hg-vanilla
Traceback (most recent call last):
File "./bin/../simfactory/lib/sim.py", line 142, in <module>
main()
File "./bin/../simfactory/lib/sim.py", line 139, in main
CommandDispatch()
File "./bin/../simfactory/lib/sim.py", line 106, in CommandDispatch
module.main()
File "/home/eschnett/EinsteinToolkit-hg-vanilla/simfactory/lib/sim-
build.py", line 420, in main
CommandDispatch()
File "/home/eschnett/EinsteinToolkit-hg-vanilla/simfactory/lib/sim-
build.py", line 347, in CommandDispatch
exec("command_%s()" % command)
File "<string>", line 1, in <module>
File "/home/eschnett/EinsteinToolkit-hg-vanilla/simfactory/lib/sim-
build.py", line 391, in command_build
PrepConfiguration(config)
File "/home/eschnett/EinsteinToolkit-hg-vanilla/simfactory/lib/sim-
build.py", line 58, in PrepConfiguration
prop.init(propertiesFile)
File "/home/eschnett/EinsteinToolkit-hg-
vanilla/simfactory/lib/restartlib.py", line 101, in init
self.ImportProperties()
File "/home/eschnett/EinsteinToolkit-hg-
vanilla/simfactory/lib/restartlib.py", line 107, in ImportProperties
for key in section.keys():
AttributeError: 'NoneType' object has no attribute 'keys'
This looks as if some internal information about the build has become
corrupt, maybe because of a partially written file.
This may be a rare case not worth handling elegantly. However -- what
should I do now?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/242>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#313: Reorder CUDA specific makefile rules
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
The rules to build CUDA source files are very similar to those for C and
C++, and different from those for the Fortrans. I suggest to reorder these
makefile rules to make the code easier to understand.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/313>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#268: The CUDA flags need to be documented
-------------------------+--------------------------------------------------
Reporter: knarf | Owner: jtao
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
The new CUDA flags in the flesh (r4684) need to be documented.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/268>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#232: GetComponents has a zero return code even when all components were not
checked out
---------------------------+------------------------------------------------
Reporter: hinder | Owner: eric9
Type: defect | Status: new
Priority: major | Milestone:
Component: GetComponents | Version:
Keywords: |
---------------------------+------------------------------------------------
When I run GetComponents, I frequently run into what I can only assume are
transient network errors of the following form:
Checking out module: CactusNumerical/Cartoon2D
from repository:
http://svn.cactuscode.org/arrangements/CactusNumerical/Cartoon2D/trunk
into: ./arrangements
svn: REPORT of '/arrangements/CactusNumerical/Cartoon2D/!svn/vcc/default':
Could not read response body: connection was closed by server.
(http://svn.cactuscode.org)
It used to be the case that GetComponents would return a nonzero exit code
in this case so that my automated script can detect this and try again.
Now GetComponents says:
163 components checked out.
0 components updated.
Unable to process CactusNumerical/Cartoon2D
Unable to process EinsteinInitialData/Exact
Unable to process EinsteinInitialData/TwoPunctures
Time Elapsed: 270 minutes, 51 seconds
and returns a zero exit code. This is preventing nightly build and test
from running.
I am using the version of GetComponents from
http://svn.cactuscode.org/Utilities/trunk/Scripts/GetComponents
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/232>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#216: Thorns in ExternalLibraries should abort if the old "extras" mechanism has
been selected
-------------------------------+--------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: ExternalLibraries |
-------------------------------+--------------------------------------------
The old way of specifying the location of external libraries, from
Cactus/lib/make/extras, for example setting HDF5 = yes, is not compatible
with the new mechanism where you must simply include the appropriate thorn
from ExternalThorns. Using both can be confusing.
I propose modifying the thorns in ExternalLibraries to check if the old
mechanism has been selected, and to abort with an explanatory error
message telling the user not to set, e.g. HDF5 = yes, if they are using
ExternalLibraries/HDF5.
I am attaching a completely untested patch for the HDF5 thorn which
implements something like this. The code to determine if the user
selected HDF5 = yes was taken from the extras directory.
Comments? If this is appropriate, it can be adapted to all the thorns in
ExternalLibraries.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/216>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#302: Multipole HDF5 file truncation with multiple variables
-----------------------+----------------------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: Other | Version:
Keywords: Multipole |
-----------------------+----------------------------------------------------
Previously a "first_time" variable was used to determine if truncation
should happen. When decomposing multiple variables, this logic is
incorrect. We now store the first_time information per output file.
I have tested the patch.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/302>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#225: Patch: Create prototypes for all scheduled functions
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
The attached patch makes the CST stage create prototypes for all scheduled
functions into a new file cctk_ScheduleFunctions.h, which is included into
cctk.h.
This is done only for C (and C++) since Fortran prototypes cannot be
declared at file scope.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/225>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#311: TimerReport: Allow user to disable scheduled function timer table
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: TimerReport |
-------------------------+--------------------------------------------------
Now that TimerReport has several options for outputting timer data, the
old-style table of schedule timers on standard output is often no longer
needed, and takes up a lot of space in standard output. The attached
patch provides a boolean parameter,
TimerReport::output_schedule_timers=yes/no, defaulting to "yes" to
maintain the current default behaviour. Users who want to use the "top
timers" output instead now have the option to disable the scheduled
function timer table.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/311>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#279: Compiling with Mac OS and Intel compiler leads to missing library warning
--------------------+-------------------------------------------------------
Reporter: hinder | Type: defect
Status: new | Priority: minor
Milestone: | Component: Cactus
Version: | Keywords:
--------------------+-------------------------------------------------------
When I compile Cactus with the Intel compiler on Mac OS I get the
following warning at link time:
ld: warning: directory '/opt/intel/Compiler/11.1/084/bin/lib' following
-L not found
I traced this to the known_architectures/darwin file which guesses the
location of the library directory relative to the output of $(which
ifort). I think now that newer compilers have 32 bit and 64 bit versions
under different directories, the directory layout has changed and the
guess is now wrong. The warning appears to be harmless, but it is
annoying. The attached patch checks to see if the first guess directory
exists, and if it doesn't, it looks one level higher up. On my system
this guess is correct and the warning message is eliminated. I looked at
the corresponding logic in the linux file but maybe the directory layout
is different on Linux.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/279>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit