On 11-04-22 at 07:02pm, Jérémy Lal wrote: > On 22/04/2011 18:14, Jonas Smedegaard wrote: > > notfixed 623449 > > thanks > > > > On 11-04-22 at 04:03pm, Debian Bug Tracking System wrote: > >> * Temporarily allow some tests to fail on armel builds. > >> Closes: bug#623449. > >> * Turn on verbose output when running tests. > > > > I disagree that it fixes bugs in regression tests to ignore > > failures. > > > > Please either elaborate on how this was fixed, or (in the future) > > leave such bugreports open and instead do _experimental_ debugging > > builds. > > I agree on the principle, but here's an example of upstream policy > about failing tests : > "ARM: Set expectations for failing deserializations tests to turn the bot > green" > http://code.google.com/p/v8/source/detail?r=7588 > > and the two tests i disabled are deserializations bugs: > I should have explained that. > I noticed upstream usually does not backport to the branches the fixes > for ARM, too.
Sorry, I do not understand your explanation. It is not that I require you to explain me the details of this (I do not expect to really understand libv8 or node!) but please clarify if this is a) temporarily closing our eyes to brokenness on ARM or b) workaround for wrong tests applied to ARM or c) uncertainty about relevancy of some tests being aplied to ARM or d) something else. If it is a) or c) then I believe it is wrong to disable the tests: We should figure out what causes the tests to fail and leave the bug open. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
