On 26/01/10 at 21:51 +0100, Ludovic Brenta wrote: > Lucas Nussbaum writes: > > severity 562342 serious > > thanks > > On 26/01/10 at 20:36 +0100, Ludovic Brenta wrote: > >> This is clearly a problem with the network configuration of the machine > >> doing the tests. I will close the bug when I fully understand what part > >> of the configuration triggers the test failures; in the mean time, > >> lowering the severity to minor. Note that polyorb being a package for > >> *distributed* applications, a network configuration that allows > >> communications between partitions is a requirement. > > > > I don't see how a network configuration problem could affect the success > > of the build, since you are not allowed to rely on the network being > > available for the built to succeed. > > The build succeeds; only the test suite fails. Are you suggesting we > not run the test suite? That would only hinder our ability to find > genuine bugs like e.g. #561156. > > If someone can tell me what part of the network configuration causes the > tests to fail, we could try to detect the condition and run the test > suite if and only if the configuration permits. I think that would be > the best solution.
What about testing with the network down to find which is the affected test, and disable that test? -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
