emacs-bug-tracker
[Top][All Lists]
Advanced

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

[debbugs-tracker] bug#21812: closed (FAIL: mb-non-UTF8-performance)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#21812: closed (FAIL: mb-non-UTF8-performance)
Date: Thu, 05 Nov 2015 03:22:02 +0000

Your message dated Wed, 4 Nov 2015 19:21:36 -0800
with message-id <address@hidden>
and subject line Re: bug#21826: long-pattern-perf test failing on distribution 
buildsystem
has caused the debbugs.gnu.org bug report #21812,
regarding FAIL: mb-non-UTF8-performance
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
21812: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21812
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: FAIL: mb-non-UTF8-performance Date: Mon, 02 Nov 2015 14:54:12 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
https://build.opensuse.org/package/live_build_log/home:Andreas_Schwab:Factory/grep/f/x86_64

FAIL: mb-non-UTF8-performance
=============================

1
FAIL mb-non-UTF8-performance (exit status: 1)

Andreas.

-- 
Andreas Schwab, SUSE Labs, address@hidden
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."



--- End Message ---
--- Begin Message --- Subject: Re: bug#21826: long-pattern-perf test failing on distribution buildsystem Date: Wed, 4 Nov 2015 19:21:36 -0800
On Wed, Nov 4, 2015 at 8:23 AM, Jaroslav Skarvada <address@hidden> wrote:
> Hi,
>
> I am observing build failures in Fedora build system (Koji) due to
> failing test 'long-pattern-perf' test. I think it's due to variable
> load on the builders, thus the time measurement of the run is not
> reliable. From one run I got:
>
> $base_ms = 20
> $b10x_ms = 550 / 20 = 27
>
> which triggers the failure. For now I disabled the test downstream
> and so far I haven't discovered any other problem

Thanks to you and Andreas for the reports.
I have pushed the attached to make these rare failures less
likely to cause trouble:

Attachment: 0001-tests-mark-performance-related-tests-as-expensive.patch
Description: Text Data


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]