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 0E74FA0C3F for ; Thu, 15 Apr 2021 22:38:38 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D368516247A; Thu, 15 Apr 2021 22:38:37 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 6C64C162479 for ; Thu, 15 Apr 2021 22:38:36 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1618519115; 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=UBBDqZ37/vkNFvkvaJPUZ48DtT0o94DTYeUCWkoSNbc=; b=PE5ker+CElWwL+d/2SlS3QDaT96LjfptwKKbQLz3zzBDOQx0Ccb1CPYE0njWA5RBhd7FQX etJg9mPVU1Tb1BD8K+fefVVlQgkXlxSzoVghlK/ivvKZsSzuB7DKfjqGfT5or8EhXrfkvF 3HLVE2ZlyBN+HrpEIZd4OiIjMtPgUms= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-482-I_NHbUWOOWm2X2WyBS7cOQ-1; Thu, 15 Apr 2021 16:38:31 -0400 X-MC-Unique: I_NHbUWOOWm2X2WyBS7cOQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 9AAB01854E20; Thu, 15 Apr 2021 20:38:30 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (ovpn-115-147.rdu2.redhat.com [10.10.115.147]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 39FF819727; Thu, 15 Apr 2021 20:38:30 +0000 (UTC) From: Aaron Conole To: Owen Hilyard Cc: ci@dpdk.org In-Reply-To: <20201204194512.14666-1-ohilyard@iol.unh.edu> References: <20201204194512.14666-1-ohilyard@iol.unh.edu> Date: Thu, 15 Apr 2021 16:38:29 -0400 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=aconole@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Subject: Re: [dpdk-ci] [PATCH] ci: added patch parser for patch files 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 Sender: "ci" Owen Hilyard writes: > This commit contains a script, patch_parser.py, and a config file, > patch_parser.cfg. These are tooling that the UNH CI team has been > testing in order to reduce the number of tests that need to be run > per patch. This resulted from our push to increase the number of > functional tests running in the CI. While working on expanding test > coverage, we found that DTS could easily take over 6 hours to run, so > we decided to begin work on tagging patches and then only running the > required tests. > > The script works by taking in an address for the config file and then > a list of patch files, which it will parse and then produce a list of > tags for that list of patches based on the config file. The config file > is designed to work as a mapping for a base path to a set of tags. It > also contains an ordered list of priorities for tags so that this may > also be used by hierarchical tools rather than modular ones. > > The intention of the UNH team with giving this tooling to the wider > DPDK community is to have people more familiar with the internal > functionality of DPDK provide most of the tagging. This would allow > UNH to have a better turn around time for testing by eliminating > unnecessary tests, while still increasing the number of tests in the > CI. > > The different patch tags are currently defined as such: > > core: > Core DPDK functionality. Examples include kernel modules and > librte_eal. This tag should be used sparingly as it is intended > to signal to automated test suites that it is necessary to > run most of the tests for DPDK and as such will consume CI > resources for a long period of time. > > driver: > For NIC drivers and other hardware interface code. This should be > used as a generic tag with each driver getting it's own tag. > > application: > Used in a similar manner to "driver". This tag is intended for > code used in only in applications that DPDK provides, such as > testpmd or helloworld. This tag should be accompanied by a tag > which denotes which application specifically has been changed. > > documentation: > This is intended to be used as a tag for paths which only contain > documentation, such as "doc/". It's intended use is as a way to > trigger the automatic re-building of the documentation website. > > Signed-off-by: Owen Hilyard > --- Applied to dpdk-ci.git Thanks!