From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 92AE44548D; Tue, 18 Jun 2024 15:36:04 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8F53440E31; Tue, 18 Jun 2024 15:36:04 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id BE19D402B4 for ; Tue, 18 Jun 2024 15:35:58 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1718717758; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=+41LrRzbE7XrpRSRX9KX50ww0oSF5z3LZZSBuhnTKsM=; b=ij7BcpTu50l9LwyRLWki0VMLlwvAy8uBRPp8wnBov+LSNJQI2U+6EzWX3W2LqMiC7U/tLN tAwaPfcJ82hIcaGpn8GUZDqfXX115VB95btL/QERocQ6H1hXx54OIVIBKwwzu3zud1iOs4 3qLGCAVsEfvdE8f+FkMBqitAOevU9S0= Received: from mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-339-RpUSQdG2PjuqmASrXqCYQg-1; Tue, 18 Jun 2024 09:35:47 -0400 X-MC-Unique: RpUSQdG2PjuqmASrXqCYQg-1 Received: from mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id A0FAC1956095; Tue, 18 Jun 2024 13:35:40 +0000 (UTC) Received: from RHTRH0061144 (dhcp-17-72.bos.redhat.com [10.18.17.72]) by mx-prod-int-02.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 0D8FF1955E80; Tue, 18 Jun 2024 13:35:38 +0000 (UTC) From: Aaron Conole To: Patrick Robb Cc: ci@dpdk.org, ahassick@iol.unh.edu, thomas@monjalon.net, alialnu@nvidia.com Subject: Re: [PATCH v2] tools: check for pending test status when parsing emails In-Reply-To: <20240523215945.16468-1-probb@iol.unh.edu> (Patrick Robb's message of "Thu, 23 May 2024 17:59:45 -0400") References: <20240517192222.20555-2-probb@iol.unh.edu> <20240523215945.16468-1-probb@iol.unh.edu> Date: Tue, 18 Jun 2024 09:35:37 -0400 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.15 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Patrick Robb writes: > Today, the community CI infrastructure only uses post-result reporting, > such as "SUCCESS", "FAILED", and "WARNING". These results get reported > only after a test finishes. This creates some confusion about whether a > test might have been started for the series in question. It isn't easy > to tell at-a-glance which tests are currently running for a given patch > or series. > > This patch aims to introduce support for a "PENDING" state in the CI > infrastructure. This allows labs to indicate which tests have started > and are awaiting results. That means test writers should now send a > "PENDING" status for tests as they start, and then update with a > post-test result after. With this change, understanding which tests ran > at-a-glance is something we can achieve. > > This change should have no affect on the actual tests being run. > > Signed-off-by: Patrick Robb > --- Thanks Patrick and Ali - applied.