Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.rc > #283744 > unrolled thread

Bug#967012: vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern

Started byLucas Nussbaum <lucas@debian.org>
First post2020-08-03 13:30 +0200
Last post2020-08-16 13:00 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.debian.bugs.rc


Contents

  Bug#967012: vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern Lucas Nussbaum <lucas@debian.org> - 2020-08-03 13:30 +0200
    Bug#967012: marked as done (vmem: FTBFS: FAIL: match:  out0.log.match:2 did not match pattern) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-08-16 13:00 +0200

#283744 — Bug#967012: vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern

FromLucas Nussbaum <lucas@debian.org>
Date2020-08-03 13:30 +0200
SubjectBug#967012: vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern
Message-ID<AzGPf-2oN-11@gated-at.bofh.it>
Source: vmem
Version: 1.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[4]: Entering directory '/<<PKGBUILDDIR>>/src/test'
> out_err/TEST0: SETUP (check/debug)
> out_err/TEST0: PASS			[00.025 s]
> out_err_mt/TEST0: SETUP (check/debug)
> out_err_mt/TEST0: PASS			[00.027 s]
> out_err_mt/TEST0: SETUP (check/nondebug)
> out_err_mt/TEST0: PASS			[00.026 s]
> out_err_mt/TEST1: SETUP (check/debug/drd)
> out_err_mt/TEST1: PASS			[00.589 s]
> out_err_mt/TEST1: SETUP (check/nondebug/drd)
> out_err_mt/TEST1: PASS			[00.564 s]
> out_err_mt/TEST2: SETUP (check/debug/helgrind)
> out_err_mt/TEST2: PASS			[00.534 s]
> out_err_mt/TEST2: SETUP (check/nondebug/helgrind)
> out_err_mt/TEST2: PASS			[00.511 s]
> scope/TEST0: SETUP (check/debug)
> [MATCHING FAILED, COMPLETE FILE (out0.log) BELOW]
> ../../debug/libvmem.so.1:
> vmem_aligned_alloc@@LIBVMEM_1.0
> vmem_calloc@@LIBVMEM_1.0
> vmem_check@@LIBVMEM_1.0
> vmem_check_version@@LIBVMEM_1.0
> vmem_create@@LIBVMEM_1.0
> vmem_create_in_region@@LIBVMEM_1.0
> vmem_delete@@LIBVMEM_1.0
> vmem_errormsg@@LIBVMEM_1.0
> vmem_free@@LIBVMEM_1.0
> vmem_malloc@@LIBVMEM_1.0
> vmem_malloc_usable_size@@LIBVMEM_1.0
> vmem_realloc@@LIBVMEM_1.0
> vmem_set_funcs@@LIBVMEM_1.0
> vmem_stats_print@@LIBVMEM_1.0
> vmem_strdup@@LIBVMEM_1.0
> vmem_wcsdup@@LIBVMEM_1.0
> 
> [EOF]
> out0.log.match:1   $(*)
> out0.log:1         ../../debug/libvmem.so.1:
> out0.log.match:2   vmem_aligned_alloc
> out0.log:2         vmem_aligned_alloc@@LIBVMEM_1.0
> FAIL: match: out0.log.match:2 did not match pattern
> RUNTESTS: stopping: scope/TEST0 failed, BUILD=debug
> make[4]: *** [Makefile:158: check] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/vmem_1.8-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

[toc] | [next] | [standalone]


#284824 — Bug#967012: marked as done (vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2020-08-16 13:00 +0200
SubjectBug#967012: marked as done (vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern)
Message-ID<AEoyl-33e-3@gated-at.bofh.it>
In reply to#283744

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sun, 16 Aug 2020 10:50:29 +0000
with message-id <E1k7GFB-000Die-7x@fasolo.debian.org>
and subject line Bug#967012: fixed in vmem 1.8-2
has caused the Debian Bug report #967012,
regarding vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern
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 owner@bugs.debian.org
immediately.)


-- 
967012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967012
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.rc


csiph-web