Your message dated Sun, 8 Sep 2019 23:19:27 +0200 with message-id <caknhny-v0cvwzohy11+dtjg_2a5noj82q54x8jfyfuaigxo...@mail.gmail.com> and subject line Re: Bug#939420: stdx-allocator: FTBFS, test failures. has caused the Debian Bug report #939420, regarding stdx-allocator: FTBFS, test failures. 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.) -- 939420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: stdx-allocator Version: 3.0.1-2 Tags: bullseye, sid stdx-allocator failed to build when binnmu'd for the ldc transition.dh_auto_test -a cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test [0/1] Running all tests. 1/1 stdx-allocator-test FAIL 0.12 s (exit status 1) Ok: 0 Expected Fail: 0 Fail: 1 Unexpected Pass: 0 Skipped: 0 Timeout: 0 The output from the failed tests: 1/1 stdx-allocator-test FAIL 0.12 s (exit status 1) --- command --- /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/stdx-allocator-test --- stderr --- core.exception.AssertError@../source/stdx/allocator/gc_allocator.d(161): Assertion failure ---------------- ??:? _d_assert [0x7fd6ea38763c] gc_allocator.d:161 [0x55b4ecb75f74] gc_allocator.d:0 [0x55b4ecb75fb5] ??:? int core.runtime.runModuleUnitTests().__foreachbody2(object.ModuleInfo*) [0x7fd6ea38e13b] ??:? int rt.minfo.moduleinfos_apply(scope int delegate(immutable(object.ModuleInfo*))).__foreachbody2(ref rt.sections_elf_shared.DSO) [0x7fd6ea3bada1] ??:? int rt.sections_elf_shared.DSO.opApply(scope int delegate(ref rt.sections_elf_shared.DSO)) [0x7fd6ea3bc109] ??:? int rt.minfo.moduleinfos_apply(scope int delegate(immutable(object.ModuleInfo*))) [0x7fd6ea3bad4b] ??:? int object.ModuleInfo.opApply(scope int delegate(object.ModuleInfo*)) [0x7fd6ea3a501e] ??:? runModuleUnitTests [0x7fd6ea38df54] ??:? void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])*).runAll() [0x7fd6ea3b18ca] ??:? _d_run_main [0x7fd6ea3b1717] ??:? __libc_start_main [0x7fd6ea11e09a] ??:? [0x55b4ecb102b9] 1/22 unittests FAILED ------- Full log written to /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-logs/testlog.txt
--- End Message ---
--- Begin Message ---Am Mi., 4. Sept. 2019 um 21:24 Uhr schrieb Peter Michael Green <plugw...@debian.org>: > > Package: stdx-allocator > Version: 3.0.1-2 > Tags: bullseye, sid > > stdx-allocator failed to build when binnmu'd for the ldc transition. > > > dh_auto_test -a > > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja > > test > > [0/1] Running all tests. > > 1/1 stdx-allocator-test FAIL 0.12 s (exit status 1) > > > > Ok: 0 > > Expected Fail: 0 > > Fail: 1 > > Unexpected Pass: 0 > > Skipped: 0 > > Timeout: 0 > > > > [...] This is fixed in version 3.1.0~beta.2-1 now, thank you for reporting the issue! Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/
--- End Message ---
