Trac May 2014

trac@lists.einsteintoolkit.org

2 participants
138 discussions

[Einstein Toolkit] #394: Testsuite log file should contain more information
by Einstein Toolkit 12 Dec '16

12 Dec '16

#394: Testsuite log file should contain more information -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: testsuites | -------------------------+-------------------------------------------------- It is useful to look at the testsuite log file for information about how the tests were run. For example, which compiler was used, and with what compiler options. We need to balance this against providing information which will always change, making diffs hard to read. The most extreme case would be to output all make variables. Maybe better would be to output CC, CFLAGS, CXX, etc. Another option would be to parse these and say "intel compiler", "gcc", "pgi" etc. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/394> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #1622: Cannot log in to Blue Waters
by Einstein Toolkit 06 Oct '16

06 Oct '16

#1622: Cannot log in to Blue Waters ------------------------+--------------------------------------------------- Reporter: eschnett | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: Component: SimFactory | Version: development version Keywords: | ------------------------+--------------------------------------------------- With the new gsissh mechanism in Simfactory, I receive the error below when I try to log in. {{{ $ ./bin/sim --verbose login bluewaters Info: Simfactory command: ./bin/../simfactory/lib/sim.py "--verbose" "login" "bluewaters" Info: Version 2356M Info: The Simulation Factory: Manage Cactus simulations Info: defs: /Users/eschnett/Cvanilla/simfactory/etc/defs.ini Info: defs.local: /Users/eschnett/Cvanilla/simfactory/etc/defs.local.ini Info: Executing command: login Info: Logging into remote machine bluewaters Info: executing command: /bin/bash -c '{ :; } && { { mkdir -p /Users/eschnett/Cvanilla/.globus && : >> /Users/eschnett/Cvanilla/.globus/proxy-tfca-ncsa && chmod go-rwx /Users/eschnett/Cvanilla/.globus/proxy-tfca-ncsa && export X509_USER_PROXY=/Users/eschnett/Cvanilla/.globus/proxy-tfca-ncsa && : mkdir -p /Users/eschnett/Cvanilla/.globus/certificates-tfca-ncsa && : export X509_CERT_DIR=/Users/eschnett/Cvanilla/.globus/certificates-tfca- ncsa && { { grid-proxy-info -issuer -file /Users/eschnett/Cvanilla/.globus/proxy-tfca- ncsa 2>/dev/null | grep "^/C=US/O=National Center for Supercomputing Applications/" >/dev/null 2>&1 && test $(grid-proxy-info -timeleft -file /Users/eschnett/Cvanilla/.globus /proxy-tfca-ncsa 2>/dev/null) -gt 0 2>/dev/null } || { { grid-proxy-destroy 2>/dev/null || true; } && myproxy-logon -p 7512 -s tfca.ncsa.illinois.edu -T -l eschnett -o /Users/eschnett/Cvanilla/.globus/proxy-tfca-ncsa } } && { globus-update-certificate-dir >/dev/null 2>&1 || true; }; } && gsissh -o UserKnownHostsFile=/Users/eschnett/Cvanilla/simfactory/etc/ssh_known_hosts -t eschnett(a)h2ologin.ncsa.illinois.edu '\''cd /u/sciteam/eschnett/Cvanilla || echo "Could not change to directory /u/sciteam/eschnett/Cvanilla"; $SHELL -l'\''; }' Enter MyProxy pass phrase: Failed to receive credentials. Failed writing buffer to BIO Failed unpacking proxy certificate from buffer Error accepting delegated credentials: Failed writing buffer to BIO Failed unpacking proxy certificate from buffer Error while executing command "/bin/bash -c '{ :; } && { { mkdir -p /Users/eschnett/Cvanilla/.globus && : >> /Users/eschnett/Cvanilla/.globus/proxy-tfca-ncsa && chmod go-rwx /Users/eschnett/Cvanilla/.globus/proxy-tfca-ncsa && export X509_USER_PROXY=/Users/eschnett/Cvanilla/.globus/proxy-tfca-ncsa && : mkdir -p /Users/eschnett/Cvanilla/.globus/certificates-tfca-ncsa && : export X509_CERT_DIR=/Users/eschnett/Cvanilla/.globus/certificates-tfca- ncsa && { { grid-proxy-info -issuer -file /Users/eschnett/Cvanilla/.globus/proxy-tfca- ncsa 2>/dev/null | grep "^/C=US/O=National Center for Supercomputing Applications/" >/dev/null 2>&1 && test $(grid-proxy-info -timeleft -file /Users/eschnett/Cvanilla/.globus /proxy-tfca-ncsa 2>/dev/null) -gt 0 2>/dev/null } || { { grid-proxy-destroy 2>/dev/null || true; } && myproxy-logon -p 7512 -s tfca.ncsa.illinois.edu -T -l eschnett -o /Users/eschnett/Cvanilla/.globus/proxy-tfca-ncsa } } && { globus-update-certificate-dir >/dev/null 2>&1 || true; }; } && gsissh -o UserKnownHostsFile=/Users/eschnett/Cvanilla/simfactory/etc/ssh_known_hosts -t eschnett(a)h2ologin.ncsa.illinois.edu '\''cd /u/sciteam/eschnett/Cvanilla || echo "Could not change to directory /u/sciteam/eschnett/Cvanilla"; $SHELL -l'\''; }'": Command returned exit status 1 eschnett@Redshift:~/Cvanilla (16:40:03) $ ./bin/sim login bluewaters Enter MyProxy pass phrase: Failed to receive credentials. Failed writing buffer to BIO Failed unpacking proxy certificate from buffer Error accepting delegated credentials: Failed writing buffer to BIO Failed unpacking proxy certificate from buffer }}} -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1622> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #1623: using ENV in parfiles is not documented
by Einstein Toolkit 25 Jun '16

25 Jun '16

#1623: using ENV in parfiles is not documented ---------------------------+------------------------------------------------ Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: documentation | ---------------------------+------------------------------------------------ the user guide does not explain how to use ENV in parfiles (at least grep ENV doc/UsersGuide/*.tex does not find anything) nor do the peg files in src/piraha/peg contain. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1623> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #382: SimFactory home directory on Kraken is too specific
by Einstein Toolkit 01 Jun '16

01 Jun '16

#382: SimFactory home directory on Kraken is too specific ------------------------+--------------------------------------------------- Reporter: hinder | Owner: mthomas Type: defect | Status: new Priority: major | Milestone: ET_2011_05 Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- The mdb entry for Kraken in SimFactory has 'sourcebasedir' => '/nics/b/home/@USER@', My home directory is '/nics/d/home/@USER@' Either we could leave the source base dir as unset to force the user to set it, or we could automatically detect the location of the user's home directory (better). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/382> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 19

[Einstein Toolkit] #960: Dissipation thorn schedules LOCAL routines after GLOBAL ones
by Einstein Toolkit 27 May '16

27 May '16

#960: Dissipation thorn schedules LOCAL routines after GLOBAL ones ----------------------------------------------+----------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: Dissipation and SphericalSurface | ----------------------------------------------+----------------------------- Dissipation currently contains a schedule item {{{ SCHEDULE setup_epsdis AT cctk_poststep after SphericalSurface_HasBeenSet { LANG: C SYNC: epsdisA_group } "Setup spatially varying dissipation" }}} However SphericalSurface_HasBeenSet is AFTER SphericalSurface_Set which is a GLOBAL routine. Since GLOBAL routines run last in POSTSTEP (which is in EVOL) the AFTER modifier is ignored for all but the last (finest) refinement level. This can lead to the wrong surface shape to be used by the local routines. It might actually make sense to teach the flesh about GLOBAL/LOCAL etc and refuse AFTER/BEFORE statements that span different modes. This of course depends on how much work this is and if we expect the dependency and task based scheduler to be finished soon and if there are legitimate uses for AFTER/BEFORE to span modes. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/960> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #912: Use CACTUS_CONFIGS_DIR in Formaline
by Einstein Toolkit 23 May '16

23 May '16

#912: Use CACTUS_CONFIGS_DIR in Formaline -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- Formaline assumes that configurations are stored in a "configs" subdirectory of $CCTK_HOME. Use $CACTUS_CONFIGS_DIR instead. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/912> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #1595: Is {{{*)}}} allowed as upper boundary for a parameter range?
by Einstein Toolkit 19 May '16

19 May '16

#1595: Is {{{*)}}} allowed as upper boundary for a parameter range? ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: | ----------------------+----------------------------------------------------- I sometimes see these warnings when Cactus starts: {{{ WARNING[L1,P0] (Cactus): Invalid end of real-valued parameter range; range descriptor is "(0.0 : *)" (value is 1) }}} Presumably the warning depends on which thorns are active. This warning looks as if the syntax {{{*)}}} was accepted by the CST when parsing a param.ccl file, but was later not recognized by the flesh when checking a parameter value against this range. (The flesh uses HUGE_VAL as fallback, which happens to be correct in this case.) -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1595> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 40

[Einstein Toolkit] #584: Use of uninitialized value in concatenation
by Einstein Toolkit 07 May '16

07 May '16

#584: Use of uninitialized value in concatenation ------------------------+--------------------------------------------------- Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: Component: SimFactory | Version: Keywords: | ------------------------+--------------------------------------------------- After failing to check out a thornlist (the current einsteintoolkit.th) the automated build and test system re-runs GetComponents with --update. On 27-Sep-2011, this gave the error: {{{ Use of uninitialized value in concatenation (.) or string at ./GetComponents line 2514. }}} This line seems to be {{{ $url = "(".$component{"URL"}.")|(".$component{"AUTH_URL"}.")"; }}} Is the problem that SimFactory doesn't have an AUTH_URL? I'm attaching the log of the testsuite script. I don't know if the error is serious or not, since the checkout has already failed. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/584> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #702: Tests should use IO::out_fileinfo = "none"
by Einstein Toolkit 18 Apr '16

18 Apr '16

#702: Tests should use IO::out_fileinfo = "none" -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Other | Version: Keywords: | -------------------------+-------------------------------------------------- The Cactus User Guide (http://einsteintoolkit.org/documentation/UsersGuide/UsersGuidech9.html#x13-…) recommends that test output files should always be the same, and hence use IO::out_fileinfo = "none". I would like to implement this for the tests in the ET, as it makes comparing test output using standard (non-Cactus testsuite mechanism) diff tools possible. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/702> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 10

[Einstein Toolkit] #1419: Cactus should produce no errors in Valgrind
by Einstein Toolkit 12 Nov '15

12 Nov '15

#1419: Cactus should produce no errors in Valgrind -------------------------+-------------------------------------------------- Reporter: sbrandt | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Cactus_4.3.0 Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- Valgrind is a useful tool for identifying a large number of coding problems. Currently, running Cactus under valgrind produces a large number of spurious errors due to the implementation of the string library. Attempts to use the valgrind suppression mechanism to eliminate them have proven difficult. However, these errors all go away if we simply replace all calls to strdup() with calls to util_Strdup(), a function which is already part of Cactus. Making this replacement shouldn't have any negative impacts, and it would make valgrind more usable. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1419> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

← Newer
1
2
3
4
5
6
7
8
...
14
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac May 2014