@Makyen thanks for the fix ... these constant DNS failures should perhaps not block every build, though I don't know how exactly then we should test them
@tripleee np. Yeah, it would be nice if they didn't cause CI failures out of the blue (i.e. cause a failure as a result of something which isn't the changes made in the commit(s) being tested). I haven't looked at that portion of the code, so can't really say what might be appropriate as an alternative for testing them.
when I wrote that test I was on the fence as to whether it should fail the build; at the time I went with the "better safe than sorry" approach but this is rather sorry too
a reasonable compromise would perhaps be to manually prune them from time to time, but that's cumbersome too
but we are already living with that in the watch list etc so maybe we should just do that
@rene and even without those indications, a promotional post about speech recognition on a question specifically NOT about speech recognition kind of gives it away
that particular combination is less than 50% but still rather significant metasmoke.erwaysoftware.com/… - it would be nice if this rather crude keyword filter could be tightened, per se
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
