Please stop assuming bad faith in what I write. This isn't the case.
No, I was not assuming bad faith.
I just thought the title was suboptimal.
I have just added the information you requested (namely, that a faster
computer probably avoids the problem). I will not change the title again.
Than
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) co
retitle 1086276 ironic; FTBFS: tests timeout
thanks
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%.
Hi,
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%.
I've therefore lowered severity, and probably will blacklist the unit
test, so it works everywhere
4 matches
Mail list logo
