On 27.12.2017 14:40, Martin Husemann wrote: > On Wed, Dec 27, 2017 at 02:27:14PM +0100, Kamil Rytarowski wrote: >> There were recently changes for golang and signal handling there.. it >> looks to me that they affected stability of this test. > > It is not about stability, it very consistently fails for me. > I've got an impression that this test started to pass by an accident with golang-related changes. It's not fully fixed, at least conscientiously. >> I'm still focused on LLVM bits, so I restrict myself temporarily to >> keeping the number of unexpected failures 0 and keep this clean for releng. > > Same here, but you only ever care about amd64. These are the last > remaining failures on sparc64 (and they only appeared very recentish), > so I'd like to get rid of them (but not paper over, if this is a real > bug). > This test used to be broken in the past, there are various new other problems (like emitting SIGSTOP instead of SIGTRAP). This failure in this particular test is not a new thing, it disappeared on amd64 but not on other ports. This scenario never worked according to my knowledge, therefor I've disabled it now. >> I will work on the ptrace(2) failures when I will be done with LLVM and >> that should be in close time. I have a list of known to me bugs that are >> not included in the ATF testsuite... so this will be a long debugging >> session. > > Looking forward to that. > > Martin > In general, thanks Christos and other developers, we are getting better situation in this field!
Attachment:
signature.asc
Description: OpenPGP digital signature