mediawiki_1.39.2-1_source.changes uploaded successfully to localhost
along with the files:
mediawiki_1.39.2-1.dsc
mediawiki_1.39.2.orig.tar.gz
mediawiki_1.39.2.orig.tar.gz.asc
mediawiki_1.39.2-1.debian.tar.xz
mediawiki_1.39.2-1_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
On Thu, Feb 02, 2023 at 02:23:21PM -0500, Kunal Mehta wrote:
> severity 1028041 normal
> thanks
>
> Hi,
>
> On 1/6/23 13:47, Adrian Bunk wrote:
> > On Fri, Jan 06, 2023 at 08:59:08AM +0100, Paul Gevers wrote:
> > > =====================================================================
> > > FAILED TEST SUMMARY
> > > ---------------------------------------------------------------------
> > > ExcimerProfiler CPU profile [tests/cpu.phpt]
> > > =====================================================================
> > >
> > > Please fix ASAP to not block the php8.2 transition.
> >
> > It built after I gave it back to build on the right buildd,
> > so it's now rebuilt with PHP 8.2.
>
> Thanks.
>
> > The issue might depend on buildd speed, or some weird difference
> > between buildds.
>
> Looking through my email, it's flaked before in the past (#1014801). The
> test in question[1] has the following comment:
>
> // Test aggregateByFunction
> // Typically the parent functions foo() and bar() will have self=0 and
> // inclusive ~= 30. The other 4 functions will have a count of about 30/4 =
> 7.5.
> // The probability of C::member() or baz() having a count of zero is about 1
> in 5600.
>
> Maybe the known flakiness is worse due to something on the mipsel build?
>...
I am not convinced that this is flakiness, my guess (that could be wrong!)
would be tests failing on all except the fastest mipsel buildds.
It is problematic that the test doesn't output what exactly fails.
On the porterbox the test passes initially, but it fails after
-$profiler->setPeriod(0.1);
+$profiler->setPeriod(10);
I do not know whether or not this is the same failure as on the mipsel
buildds.
> -- Kunal
cu
Adrian
Hi Kunal,
On 02-02-2023 20:23, Kunal Mehta wrote:
> I'm lowering the severity because it no longer blocks the 8.2 transition
> (please revert me if I'm wrong on that).
In my opinion flaky builds and flaky tests are bad because they cost
quite some time of people that are not involved in the package. E.g. in
this case Release Team, but imagine a security upload where the build
fails. But you have flaky and flaky. https://bugs.debian.org/844264 is
an interesting read in that regard.
As somebody that maintains infrastructure and does a lot of QA
(ci.debian.net) and is involved in transitions and migrations where I
see a lot of flaky tests, I'm biased. But really, a test that fails more
often than say 1/5 times is RC in my book. I didn't check the ratio of
php-excimer failures.
Paul
Processing commands for control(a)bugs.debian.org:
> severity 1028041 normal
Bug #1028041 [src:php-excimer] php-excimer: FTBFS on mipsel
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1028041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028041
Debian Bug Tracking System
Contact owner(a)bugs.debian.org with problems