From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0FDA433EA for ; Sun, 24 Apr 2022 20:50:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1650833402; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=RIflC2lW8bEg+Sb4P57/jwYLsbWJyONRvwc5HqmbYZ0=; b=Ule4xOrEyvJtXtSiN5q4jbj/uwJC885OB1S1kSNH6FJ1NytK0LsHNK46itaiGNztmDP7uy 7g24SRkENoR390Y1I1Cc79AbJszUvd21NONWFm3EZr+VhFuifWzjTsTDc4tQWQHOI6E7Sb QzmCkfsAsMp0pct4SZ2mwKSL+QNbqy8= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-540-ss1tNjbXN9eGvSYnEuk9Yg-1; Sun, 24 Apr 2022 16:50:00 -0400 X-MC-Unique: ss1tNjbXN9eGvSYnEuk9Yg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 6D50F811E78 for ; Sun, 24 Apr 2022 20:50:00 +0000 (UTC) Received: from [172.64.3.113] (unknown [10.30.33.184]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5F5A040C1421; Sun, 24 Apr 2022 20:50:00 +0000 (UTC) Precedence: bulk X-Mailing-List: llvm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 From: CKI Project To: llvm@lists.linux.dev Subject: =?utf-8?b?4pyF?= PASS: Test report for kernel 5.18.0-rc3 (mainline.kernel.org-clang, 5206548f) Date: Sun, 24 Apr 2022 20:50:00 -0000 Message-ID: X-Gitlab-Pipeline-ID: 523417950 X-Gitlab-Url: https://gitlab.com X-Gitlab-Path: =?utf-8?q?/redhat/red-hat-ci-tools/kernel/cki-internal-pipeli?= =?utf-8?q?nes/cki-trusted-contributors/pipelines/523417950?= X-DataWarehouse-Checkout-IID: 39957 X-Scanned-By: MIMEDefang 2.84 on 10.11.54.2 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=cki-project@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Check out this report and any autotriaged failures in our web dashboard: https://datawarehouse.cki-project.org/kcidb/checkouts/39957 Hello, We ran automated tests on a recent commit from this kernel tree: Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvald= s/linux.git Commit: 5206548f6e67 - Merge tag 'powerpc-5.18-3' of git://git.= kernel.org/pub/scm/linux/kernel/git/powerpc/linux The results of these automated tests are provided below. Overall result: PASSED Merge: OK Compile: OK Selftests compile: FAILED Tests: OK Targeted tests: NO All kernel binaries, config files, and logs are available for download here= : https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre= fix=3Ddatawarehouse-public/2022/04/24/523417950 Please reply to this email if you have any questions about the tests that w= e ran or if you have any suggestions on how to make future tests more effecti= ve. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ___________________________________________________________________________= ___ Compile testing --------------- We compiled the kernel for 5 architectures: aarch64: make options: make LLVM=3D1 -j24 INSTALL_MOD_STRIP=3D1 targz-pkg ppc64le: make options: make CC=3Dclang LLVM_IAS=3D0 -j24 INSTALL_MOD_STRIP=3D1= targz-pkg s390x: make options: make CC=3Dclang LLVM_IAS=3D0 -j24 INSTALL_MOD_STRIP=3D1= targz-pkg x86_64: make options: make LLVM=3D1 -j24 INSTALL_MOD_STRIP=3D1 targz-pkg x86_64: make options: make LLVM=3D1 -j24 INSTALL_MOD_STRIP=3D1 targz-pkg We built the following selftests: x86_64: net: OK bpf: fail seccomp: OK lkdtm: OK install and packaging: OK You can find the full log (build-selftests.log) in the artifact storage abo= ve. Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: =E2=9A=A1 Internal infrastructure issues prevented one or more tests (m= arked with =E2=9A=A1=E2=9A=A1=E2=9A=A1) from running on this architecture. This is not the fault of the kernel that was tested. ppc64le: =E2=9A=A1 Internal infrastructure issues prevented one or more tests (m= arked with =E2=9A=A1=E2=9A=A1=E2=9A=A1) from running on this architecture. This is not the fault of the kernel that was tested. s390x: =E2=9A=A1 Internal infrastructure issues prevented one or more tests (m= arked with =E2=9A=A1=E2=9A=A1=E2=9A=A1) from running on this architecture. This is not the fault of the kernel that was tested. x86_64 (debug): =E2=9A=A1 Internal infrastructure issues prevented one or more tests (m= arked with =E2=9A=A1=E2=9A=A1=E2=9A=A1) from running on this architecture. This is not the fault of the kernel that was tested. x86_64: =E2=9A=A1 Internal infrastructure issues prevented one or more tests (m= arked with =E2=9A=A1=E2=9A=A1=E2=9A=A1) from running on this architecture. This is not the fault of the kernel that was tested. Test sources: https://gitlab.com/cki-project/kernel-tests =F0=9F=92=9A Pull requests are welcome for new tests or improvements to= existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with =E2=9A=A1= =E2=9A=A1=E2=9A=A1. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with =F0=9F=9A=A7. S= uch tests are executed but their results are not taken into account. Tests are waived whe= n their results are not reliable enough, e.g. when they're just introduced or= are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with =E2=8F=B1. Targeted tests -------------- Test runs for patches always include a set of base tests, plus some tests chosen based on the file paths modified by the patch. The latter are called "targeted tests". If no targeted tests are run, that means no patch-specific tests are available. Please, consider contributing a targeted test for related patches to increase test coverage. See https://docs.engineering.redhat.com/x/_wEZB for more details.