On Wed, Jan 22, 2020 at 01:40:43PM +0500, ???? ??????? wrote: > ??, 22 ???. 2020 ?. ? 10:49, Willy Tarreau <[email protected]>: > > > On Sun, Jan 19, 2020 at 12:18:00PM +0500, ???? ??????? wrote: > > > hello, > > > > > > sometimes arm64 builds fails, I think it is good chance to introduce > > > regular builds > > > and fix them. > > > > > > also, few small improvements. > > > > > occasionely, I introduced "socat" for linux builds. god knows, I only > wanted socat on osx. > > now we have daily failing openssl-1.0.2: > > https://travis-ci.com/haproxy/haproxy/jobs/278244081 > > should I temporarily mark it as "allowed failure" on travis ? (it will be > fixed in issue #429)
Yes I noticed it and tried to figure what was happening until I figured it was the known issue. I'd prefer to mark it as "allowed failure" if possible so that we keep watching travis's output. Isn't it already the case, given that the icon still says "build|passing" ? Also given that it's a regtest that fails, maybe we should disable them for this target temporarily ? The right thing to do should be to tag this regtest as requiring 1.1.0 but we don't have this level of flexibility yet :-/ Willy
