Your message dated Tue, 28 Jul 2020 22:38:12 +0200
with message-id <03352a5835f2086832b46ffeadf50da58bb8ee01.ca...@43-1.org>
and subject line Re: Bug#957155: dune-grid: ftbfs with GCC-10
has caused the Debian Bug report #957155,
regarding dune-grid: ftbfs with GCC-10
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
957155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dune-grid
Version: 2.6.0-5
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/dune-grid_2.6.0-5_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
      Start 61: vertexordertest
61/61 Test #61: vertexordertest .......................................   
Passed    0.32 sec

98% tests passed, 1 tests failed out of 61

Total Test time (real) =  47.08 sec

The following tests did not run:
          6 - printgridtest (Skipped)
         11 - amirameshtest (Skipped)
         34 - test-loadbalancing (Skipped)

The following tests FAILED:
         23 - test-geogrid-yaspgrid (Failed)
Errors while running CTest
======================================================================
Name:      printgridtest
FullName:  ./dune/grid/io/file/test/printgridtest
Status:    NOTRUN
Output:
           sh: 1: gnuplot: not found
           GNUplot was not found.

======================================================================
Name:      amirameshtest
FullName:  ./dune/grid/io/file/test/amirameshtest
Status:    NOTRUN
Output:
           This test was skipped because it failed the following CMake 
Conditions:
             AMIRAMESH_FOUND

======================================================================
Name:      test-geogrid-yaspgrid
FullName:  ./dune/grid/test/test-geogrid-yaspgrid
Status:    FAILED
Output:
           Checking grid...
           0061000000000000
           0061000000000000
           Lifetime / consistency check for entities, codim 2
           WARNING! Requested check of first 32 entities, but grid view only 
contains 25 entities
           Lifetime / consistency check for entities, codim 1
           Lifetime / consistency check for entities, codim 0
           WARNING! Requested check of first 32 entities, but grid view only 
contains 16 entities
           Intersection Lifetime / consistency check
           WARNING! Requested check of intersections for first 32 elements, but 
grid view only contains 16 elements
           Lifetime / consistency check for entities, codim 2
           WARNING! Requested check of first 32 entities, but grid view only 
contains 25 entities
           Lifetime / consistency check for entities, codim 1
           Lifetime / consistency check for entities, codim 0
           WARNING! Requested check of first 32 entities, but grid view only 
contains 16 entities
           Intersection Lifetime / consistency check
           WARNING! Requested check of intersections for first 32 elements, but 
grid view only contains 16 elements
           Checking geometry... 
           Checking geometry in father...
           Checking intersections...
           Dune::GridError 
[checkIntersectionIterator:/<<PKGBUILDDIR>>/dune/grid/test/checkintersectionit.hh:518]:
 Could not find inside entity through intersection iterator on outside entity.

======================================================================
Name:      test-loadbalancing
FullName:  ./dune/grid/test/test-loadbalancing
Status:    NOTRUN
Output:
           This test requires ParMetis.
           Note that the emulation layer provided by scotch is not sufficient.

make[1]: *** [/usr/share/dune/dune-debian.mk:21: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
On Mon, 2020-05-25 at 19:04 +0200, Ansgar wrote:
> > The package fails to build in a test rebuild on at least amd64 with
> > gcc-10/g++-10, but succeeds to build with gcc-9/g++-9.
> [...]
> > Name:      test-geogrid-yaspgrid
> > FullName:  ./dune/grid/test/test-geogrid-yaspgrid
> > Status:    FAILED
> > Output:
> [...]
> >            Dune::GridError
> > [checkIntersectionIterator:/<<PKGBUILDDIR>>/dune/grid/test/checkint
> > ersectionit.hh:518]: Could not find inside entity through
> > intersection iterator on outside entity.
> 
> This is not fixed by 2.7.0.  Will look at it later.

With "g++ (= 4:10.1.0-1), g++-10 (= 10.2.0-3)" from current Debian
unstable the package builds successfully on amd64.

Ansgar

--- End Message ---

Reply via email to