Trac January 2018

trac@lists.einsteintoolkit.org

1 participants
75 discussions

[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

[Einstein Toolkit] #2107: Support Darwin 17.4.0
by Einstein Toolkit 26 Jan '18

26 Jan '18

#2107: Support Darwin 17.4.0 ----------------------+----------------------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: unset | Milestone: Component: Cactus | Version: development version Keywords: | ----------------------+----------------------------------------------------- https://bitbucket.org/cactuscode/cactus/pull-requests/44/flesh-support- darwin-1740/diff -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2107> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1995: McLachlan constraint tests fail
by Einstein Toolkit 26 Jan '18

26 Jan '18

#1995: McLachlan constraint tests fail ---------------------------------------------------------------+------------ Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: ET_2016_11 Component: EinsteinToolkit thorn | Version: development version Keywords: McLachlan constraints tests compiler optimization | ---------------------------------------------------------------+------------ Several tests fail on several machines, and the cause seems to be the constraints calculated by McLachlan. Peter is looking into this. We see test failures in the thorns Dissipation and RotatingSymmetry90/180. Indications are that most failures happen with Intel 15, but some are apparently also seen with Intel 16, while others with Intel 16 seem to work fine. Optimization -O1 instead of -O2 seems to prevent the problem, but is not a viable workaround. A simple 'print' statement in the affected (auto-generated) code also makes the problem disappear. Running using one MPI process and one openMP thread reproduces the problem. valgrind does not find anything obvious pointing to memory mess-up. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1995> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 48

[Einstein Toolkit] #2078: thorn vectors fails if vectorizatin is disabled
by Einstein Toolkit 26 Jan '18

26 Jan '18

#2078: thorn vectors fails if vectorizatin is disabled -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: Vectors | -----------------------------------+---------------------------------------- At least in one case (gcc 7.2) thorn Vectors seems to fail with a message that overloading is not allowed in line 671 of vectors.h {{{ explicit constexpr vectype(scalar_t const &a) : v(props::set1(a)) {} }}} if vectorization is disabled (VECTORISE=no). My guess would be that in this case scalar_t and vector_t are the same and a conflict exists (or some other assumption is violated). I'll provide more details once I have a a nicer testcase. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2078> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #2099: Cactus requires Fortran
by Einstein Toolkit 25 Jan '18

25 Jan '18

#2099: Cactus requires Fortran ---------------------+------------------------------------------------------ Reporter: sbrandt | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: | ---------------------+------------------------------------------------------ If you use the old generic.cfg (which has "none" for both F77 and F90) and a thornlist that consists of the flesh only, Cactus will *not* compile. It will complain that CCTK_REAL is undefined. Interestingly, if no definition is provided for F77 and F90 in the optionlist, then the Cactus build system assumes gfortran and compiles. If, however, in addition to not defining F77 and F90 in the cfg, no fortran is actually present (i.e. not installed), then the CCTK_REAL issue returns. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2099> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 18

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac January 2018