From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id BD502A0096 for ; Wed, 5 Jun 2019 14:05:55 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8BACD1B9E9; Wed, 5 Jun 2019 14:05:55 +0200 (CEST) Received: from mail-ua1-f42.google.com (mail-ua1-f42.google.com [209.85.222.42]) by dpdk.org (Postfix) with ESMTP id 88AB61B9DF for ; Wed, 5 Jun 2019 14:05:54 +0200 (CEST) Received: by mail-ua1-f42.google.com with SMTP id 94so8992903uam.3 for ; Wed, 05 Jun 2019 05:05:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=kyYRn9HuBbBbgxmjj7yF86SBPdghvQdVxAs8N2N3MYY=; b=gzk/g6zrMgVgbB6sqb/7AN0hSOJe6ozLBSWS9m+lbxN9i9fDQ9M3+d50WqfVRQuYIN 4+bVV9FnCov5H1KfRbg++uY7k0ws9u0mo+ErrlfsL2mg0agiVaKpxOumYxMzaYa9kY0B tEkwRr/2xDK7QQ66bCFyDxSiHd83yQWzQlYESS5aQw6oRZ3SDciTb5hmWfbLYRpdszsa hhZvO7aXtNW1/quLknkyvPzxKRRnhLjoeRaSPP4FFwRKmnx/oKY0EVAmp259K0hqsm/X ZeU/AJQTQKKj+lD32bjVRhkj1Anx069HJdFmkoVKNKpGPNrMS6BXIrwI7WjztDSdys/M pheg== X-Gm-Message-State: APjAAAWhFqrz45GGwKsnjrDqeBb7b4Jdv2sxhp6U1q6Wd7kZg83ANVdc sxo7LBzQn/4Qi4AZu2jqaZjv7gRh7cpS6iLG7vK9aiuEMz8= X-Google-Smtp-Source: APXvYqx9W7rucEHd1YPqSTERAGEHCFuAl2UsvBRBAsvh82WR7B2IISoOOAeHhSnevwJ1GGfFTsKxtOu6ghaqWwFgxn8= X-Received: by 2002:ab0:168a:: with SMTP id e10mr5517954uaf.87.1559736353613; Wed, 05 Jun 2019 05:05:53 -0700 (PDT) MIME-Version: 1.0 From: David Marchand Date: Wed, 5 Jun 2019 14:05:42 +0200 Message-ID: To: dev Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] aesni mb on Centos KO for three weeks X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" I noticed build errors on patches I sent yesterday: http://mails.dpdk.org/archives/test-report/2019-June/084633.html I went and looked at the test-report mailing list. The failures on master builds started on May 14th: http://mails.dpdk.org/archives/test-report/2019-May/082432.html But still, the test was reported as successfull. The status got properly reported starting May 28th: http://mails.dpdk.org/archives/test-report/2019-May/083421.html Looking at patchwork this day, I can see that it changed between http://patchwork.dpdk.org/patch/53721/ and http://patchwork.dpdk.org/patch/53722/ So I suppose someone noticed that the meson build failures were not properly reported and fixed it, but the error still remained. So, we have this error for 3 weeks, is there someone looking at fixing it please? I did not manage to build the ipsec_mb thing on my rhel. Not sure what is wrong, but I don't want to waste more time on it. As a sidenote, we don't have Intel build reports on the patches since this morning, around http://mails.dpdk.org/archives/test-report/2019-June/084647.html Has it been disabled intentionnally? -- David Marchand