Hi Santiago,
On 10/30/24 16:06, Santiago Vila wrote:
retitle 1086276 ironic; FTBFS: tests timeout
thanks
Please don't. This is not an acceptable change in the title: you've
deleted some important information that I added to the title, which is
that in some cases, with a faster (less busy) computer, it works.
Please revert your title change, and also I'd appreciate not doing BTS
ping-pong which is a loss of time for both you and me. Ultimately, it's
up to the maintainer to decide, because this helps organize and
prioritize Debian work.
El 30/10/24 a las 15:33, Thomas Goirand escribió:
What you're seeing here is only a fail on slow computers, as the unit
test reaches timeout. I know it because other OpenStack services had
the issue, and as you can see, it stops at 93.49%.
By writing such thing in the title we convey
the message that it's the user's fault for using a "slow" computer
to build packages, and I think that's not ok.
Please stop assuming bad faith in what I write. This isn't the case.
While I very much appreciate your bug reports (they have a lot of value,
they help me increasing package quality, etc.), it'd be nice if you
could quit thinking I have bad intentions, or that I'm not willing to
fix bugs. So far, I did address all issues, every times. And never put
the blame on Debian users.
[...] probably will blacklist the unit test, so it works everywhere.
Please do so.
Or maybe double the timeout. This package used to take 10 minutes to build
in trixie in my framework. The timeout should not be a lot shorter than
that.
That's what I intend to do upstream first, yes. I already engaged
discussion with them about it.
Cheers,
Thomas Goirand (zigo)
