[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Osmium packages



I have removed those tests in master now. They don't really say much anyway.
Will be in the next release.

Jochen

On So, Jul 12, 2015 at 05:31:59 +0200, Sebastiaan Couwenberg wrote:
> Date: Sun, 12 Jul 2015 17:31:59 +0200
> From: Sebastiaan Couwenberg <sebastic@xs4all.nl>
> To: debian-gis@lists.debian.org
> Subject: Re: Osmium packages
> 
> On 07/12/2015 05:06 PM, Jochen Topf wrote:
> > On Fri, Jul 10, 2015 at 09:19:05PM +0200, Sebastiaan Couwenberg wrote:
> >> On 07/04/2015 02:12 PM, Jochen Topf wrote:
> >>> I have just released new upstream versions of libosmium, pyosmium, and
> >>> osmium-tool. I have fixed the reproducible-build-issues upstream and the
> >>> bug that showed up in the 32bit pyosmium test is also fixed.
> >>
> >> Unfortunately the new mmap test is causing the libosmium builds to fail
> >> on kFreeBSD, do you have any ideas how to fix them?
> > 
> > Not without getting some more information about the problem. Is there more
> > information than this? https://buildd.debian.org/status/package.php?p=libosmium
> > 
> > This just tells me that a test failed. But no details. ctest is called with
> > -V already, but it doesn't print any output where exactly the test fails.
> > 
> > Somebody with access to a FreeBSD system could probably quickly find out whats
> > wrong. Probably just a small difference between Linux and FreeBSD in the way
> > mmap(2) works.
> 
> I figured as much, but I don't see clear difference between the FreeBSD
> & Linux mmap(2) behavior.
> 
> http://manpages.debian.org/cgi-bin/man.cgi?query=mmap&sektion=2
> http://www.freebsd.org/cgi/man.cgi?query=mmap&sektion=2
> 
> Running the test manually on a Debian GNU/kFreeBSD 64bit VM I get:
> 
> $ ./build/test/util_test_memory_mapping
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> util_test_memory_mapping is a Catch v1.0 b53 host application.
> Run with -? for options
> 
> -------------------------------------------------------------------------------
> anonymous mapping
>   memory mapping a huge area should fail
> -------------------------------------------------------------------------------
> /tmp/libosmium/test/t/util/test_memory_mapping.cpp:15
> ...............................................................................
> 
> /tmp/libosmium/test/t/util/test_memory_mapping.cpp:49: FAILED:
>   REQUIRE_THROWS_AS( osmium::util::MemoryMapping mapping(huge) )
> because no exception was thrown where one was expected:
> 
> -------------------------------------------------------------------------------
> typed anonymous mapping
>   memory mapping a huge area should fail
> -------------------------------------------------------------------------------
> /tmp/libosmium/test/t/util/test_memory_mapping.cpp:216
> ...............................................................................
> 
> /tmp/libosmium/test/t/util/test_memory_mapping.cpp:235: FAILED:
>   REQUIRE_THROWS_AS( osmium::util::TypedMemoryMapping<uint32_t>
> mapping(huge) )
> because no exception was thrown where one was expected:
> 
> ===============================================================================
> test cases:  5 |  3 passed | 2 failed
> assertions: 78 | 76 passed | 2 failed
> 
> 
> That's pretty much the same as what you see in buildlog.
> 
> How can I better troubleshoot this failure?
> 
> Kind Regards,
> 
> Bas
> 
> -- 
>  GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-gis-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] 55A2886F.40602@xs4all.nl">https://lists.debian.org/[🔎] 55A2886F.40602@xs4all.nl
> 

-- 
Jochen Topf  jochen@remote.org  http://www.jochentopf.com/  +49-351-31778688


Reply to: