Trac

trac@lists.einsteintoolkit.org

8708 discussions

[Einstein Toolkit] #2116: simfactory --remote does not detect incorrect options
by Einstein Toolkit 02 Feb '18

02 Feb '18

#2116: simfactory --remote does not detect incorrect options ------------------------+--------------------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: major | Milestone: Component: SimFactory | Version: development version Keywords: | ------------------------+--------------------------------------------------- simfactory --remote passes the command that one wants to execute to a remote machine. However while doing so, simfactory parses and re-builds the command line. In the process of building the command line it will *only* rebuild those that it recognizes and silently ignore the others. Ie: {{{ simfactory/bin/sim --remote bluewaters list-simulations --simfactory-does- not-check-options }}} will succeed while the same command executed locally will fail. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2116> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 0

[Einstein Toolkit] #2114: Carpet/Carpet/test/64k2.par test fails on Jenkins test machine
by Einstein Toolkit 02 Feb '18

02 Feb '18

#2114: Carpet/Carpet/test/64k2.par test fails on Jenkins test machine --------------------+------------------------------------------------------- Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: minor | Milestone: Component: Carpet | Version: development version Keywords: | --------------------+------------------------------------------------------- The test Carpet/Carpet/test/64k2.par exits with nonzero and reports: {{{ INFO (Carpet): There are 0 3-dimensional grid arrays in 0 groups INFO (Carpet): (The number of variables counts all time levels) ERROR from host 7ce14e5707a0 process 0 while executing schedule bin (none), routine (no thorn)::(no routine) in thorn CarpetLib, file /home/jenkins/workspace/EinsteinToolkitGeneric/configs/sim/build/CarpetLib/mem.cc:113: -> Failed to allocate 12884901888 bytes (12884.902 MB) of memory for type CCTK_REAL8. 312 bytes (0.000 MB) are currently allocated in 39 objects ERROR from host 7ce14e5707a0 process 0 while executing schedule bin (none), routine (no thorn)::(no routine) in thorn CarpetLib, file /home/jenkins/workspace/EinsteinToolkitGeneric/configs/sim/build/CarpetLib/mem.cc:113: -> Failed to allocate 12884901888 bytes (12884.902 MB) of memory for type CCTK_REAL8. 312 bytes (0.000 MB) are currently allocated in 39 objects cactus_sim: /home/jenkins/workspace/EinsteinToolkitGeneric/configs/sim/build/Carpet/helpers.cc:275: int Carpet::Abort(const cGH*, int): Assertion `0' failed. Rank 0 with PID 4507 received signal 6 Writing backtrace to 64k2/backtrace.0.txt Aborted (core dumped) }}} Note that this has probably been happening for a very long time. The test system just doesn't detect the problem (see #2113). I'm not 100% sure what this test is supposed to do. It has Carpet::enable_no_storage = yes, so it shouldn't be trying to allocate memory. The test machine has 4 GB of RAM. This could be increased, but we probably don't want to have a test in the ET that requires so much memory. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2114> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #2113: Test system ignores exit code of Cactus
by Einstein Toolkit 02 Feb '18

02 Feb '18

#2113: Test system ignores exit code of Cactus --------------------+------------------------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Cactus | Version: development version Keywords: | --------------------+------------------------------------------------------- When a test is running, and Cactus fails with a nonzero exit code, the test system populates a data structure to indicate that the test has failed: {{{ RunTestUtils.pl:1618, RunTest(): $testdata->{"$thorn FAILED"} .= "$parfile "; $testdata->{"NFAILED"}++; }}} but the test is later regarded as successful. Probably the function CompareTestFiles ignores the fail code set by RunTest. In the case where the test has data file to compare with, this usually is exhibited as a failure, as the new files will probably not be created. But in the case where there are no data files to compare with, the system doesn't expect to find any, and the test succeeds. CompareTestFiles probably needs to be modified to take into account the failed run, or maybe it should never be called in the first place. The test Carpet/Carpet/test/64k2.par currently shows this problem; it reports that it is unable to allocate 12 GB of RAM, and exits like this: {{{ ------------------------------------------------------------------------ Test Carpet: 64k2 "Carpet/Carpet/test/64k2.par" Issuing rm -f output-0000-active && ln -s . output-0000-active && mkdir -p SIMFACTORY && TESTSUITE_PARFILE=/home/jenkins/workspace/simulations/EinsteinToolkit_f297f2e499015361358e5acfe294e024673292e3_1/output-0000/arrangements/Carpet/Carpet/test/64k2.par /home/jenkins/workspace/EinsteinToolkit/../simulations/EinsteinToolkit_f297f2e499015361358e5acfe294e024673292e3_1/output-0000/SIMFACTORY/RunScript Cactus exited with error code 134 Please check the logfile /home/jenkins/workspace/simulations/EinsteinToolkit_f297f2e499015361358e5acfe294e024673292e3_1/output-0000/TEST/sim/Carpet/64k2.log No files created in test directory Success: 0 files identical ------------------------------------------------------------------------ }}} The test is then considered as successful in the final output. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2113> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #2077: include RNSID in ET
by Einstein Toolkit 02 Feb '18

02 Feb '18

#2077: include RNSID in ET -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: Hydro_RNSID | -----------------------------------+---------------------------------------- Pull request is here: https://bitbucket.org/einsteintoolkit/einsteininitialdata/pull-requests/3 /new-initial-data-thorn-for-grhydro/diff It generate ID for rotating star either with uniform rotational profile or describe by differentialy rotating j-law. testsuite par file provided and tested example of usage parfile in par subdirectory as perl script that generate par file with resolution dx=0.75 suited for workstation tests. Hydro_RNSID/par/speed.rpar generate par file usefull to peform speed test two stand alone utility are generate at compile time to [RNS] generate initial models (to be imported in Cactus) amd to read [RNS_read] the generated initial model -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2077> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #1911: Hydro_InitExcision sphere_pugh_ppm test fails
by Einstein Toolkit 31 Jan '18

31 Jan '18

#1911: Hydro_InitExcision sphere_pugh_ppm test fails ---------------------------+------------------------------------------------ Reporter: barry.wardell | Owner: Type: defect | Status: new Priority: unset | Milestone: Component: Other | Version: development version Keywords: | ---------------------------+------------------------------------------------ The Hydro_InitExcision sphere_pugh_ppm test fails for me when run on 1 process on an Ubuntu 16.04 machine. The diffs are attached. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1911> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 16

[Einstein Toolkit] #2111: Can't compile the ET on the NDS test machine
by Einstein Toolkit 30 Jan '18

30 Jan '18

#2111: Can't compile the ET on the NDS test machine ---------------------+------------------------------------------------------ Reporter: sbrandt | Owner: Type: defect | Status: new Priority: blocker | Milestone: ET_2018_02 Component: Other | Version: development version Keywords: | ---------------------+------------------------------------------------------ g++: internal compiler error: Killed (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions. /home/jovyan/Cactus/configs/sim/config-data/make.config.rules:278: recipe for target 'ML_BSSN_EvolutionInterior.cc.o' failed $ g++ --version g++ (Ubuntu 5.4.0-6ubuntu1~16.04.5) 5.4.0 20160609 Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2111> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #2096: SphericalHarmonicRecon and SphericalHarmonicReconGen tests fail on Jenkins build machine
by Einstein Toolkit 29 Jan '18

29 Jan '18

#2096: SphericalHarmonicRecon and SphericalHarmonicReconGen tests fail on Jenkins build machine -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: ET_2018_02 Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- (Adapted from http://lists.einsteintoolkit.org/pipermail/users/2017-July/005671.html) The following three tests fail on the Jenkins build machine: SphericalHarmonicRecon.regression_test/2procs SphericalHarmonicReconGen.SpEC-dat-test/2procs SphericalHarmonicReconGen.SpEC-h5-test/2procs These tests all pass on one process but fail on two processes, using the ubuntu.cfg optionlist. They all seem to pass on multiple processes on all other machines, including my laptop with gcc. The first, SphericalHarmonicRecon.regression_test, fails like this: {{{ WARNING level 0 from host 7ce14e5707a0 process 0 while executing schedule bin NullEvol_Initial, routine NullEvolve::NullEvol_InitialSlice in thorn NullEvolve, file NullEvol_InitialSlice.F90:42: -> Error }}} The second, SphericalHarmonicReconGen.SpEC-dat-test, fails like this: {{{ NewsB_scri.L02Mm01.asc: substantial differences significant differences on 1 (out of 2) lines maximum absolute difference in column 1 is 963 maximum absolute difference in column 2 is 0.000185770963653907 maximum absolute difference in column 3 is 0.000142466608463344 maximum relative difference in column 1 is 1 maximum relative difference in column 2 is 1 maximum relative difference in column 3 is 1 ... }}} The third, SphericalHarmonicReconGen.SpEC-h5-test, fails like this: {{{ NewsB_scri.L02Mm01.asc: substantial differences significant differences on 1 (out of 2) lines maximum absolute difference in column 1 is 963 maximum absolute difference in column 2 is 0.000185770963653907 maximum absolute difference in column 3 is 0.000142466608463344 maximum relative difference in column 1 is 1 maximum relative difference in column 2 is 1 maximum relative difference in column 3 is 1 ... }}} I suspect the second and third failures have the same cause. These tests don't seem to fail on any other machines. See the discussion thread http://lists.einsteintoolkit.org/pipermail/users/2017-July/thread.html#5671 for more information. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2096> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 21

[Einstein Toolkit] #2027: testsuite page is not avaiable on website
by Einstein Toolkit 29 Jan '18

29 Jan '18

#2027: testsuite page is not avaiable on website -------------------------------------+-------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit website | Version: development version Keywords: | -------------------------------------+-------------------------------------- The testsuite overview page http://einsteintoolkit.org/release-info/parse_testsuite_results.php does not currently work (since the website changed). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2027> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #2110: bash_utils find_lib error check
by Einstein Toolkit 27 Jan '18

27 Jan '18

#2110: bash_utils find_lib error check -------------------------+-------------------------------------------------- Reporter: hinder | Owner: hinder Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- I recently ran into a problem where the package location returned by pkg- config was wrong due to a messed-up system installation. The find_lib function in bash_utils.sh could check that the library location it returns actually exists. That would have made it much easier to track down this problem. Is there ever any situation where it is valid for find_lib to return a path which doesn't exist? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2110> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #2102: Regenerate all Kranc thorns
by Einstein Toolkit 27 Jan '18

27 Jan '18

#2102: Regenerate all Kranc thorns -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: task | Status: new Priority: major | Milestone: ET_2018_02 Component: EinsteinToolkit thorn | Version: development version Keywords: ReleaseProcess | -----------------------------------+---------------------------------------- All the Kranc-generated thorns should be regenerated: * McLachlan * EinsteinExact * WeylScal4 -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2102> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac