From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wm1-f47.google.com (mail-wm1-f47.google.com [209.85.128.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 441EA63CA for ; Thu, 28 Dec 2023 04:55:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="lnskY+oU" Received: by mail-wm1-f47.google.com with SMTP id 5b1f17b1804b1-40d5ab2f9f1so19485055e9.3 for ; Wed, 27 Dec 2023 20:55:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703739334; x=1704344134; darn=vger.kernel.org; h=cc:to:mime-version:content-transfer-encoding:fcc:subject:date:from :references:in-reply-to:message-id:from:to:cc:subject:date :message-id:reply-to; bh=7QyaJQzv4xxOMJ6QuOSOFIfWjRAGk5UMXHHcFqttjMs=; b=lnskY+oURjZDElJ0I2yFT6nbHtWSA2GfACTij7D4je3Jr0HlmD8VkT6IArS5RrL/1q 78am3bFjabn7PYCpTFbUEXIbFbK416wmg2DSm3gt4nsc1VS1NWA4336PTu3Go0tLhOam LuWpZAG8jaCbEz7ek4sroEbk2GIRy4OI4hmBFChChYIqSXR0MA5t0SH29Bk8NmGpj4+L u4t7RWcx7bM8Y+XFRucvApR7gmdaWMe9LvvmFHYxRohgnMkIpdRIi6MysSwo4pGxOtQh X1R9EkhiHdKebhccEytF1aBL7s6mJzMGnfRLBmKQkajKWc/D8BH/zkvHU1E/mqKajXTy 5C8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703739334; x=1704344134; h=cc:to:mime-version:content-transfer-encoding:fcc:subject:date:from :references:in-reply-to:message-id:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=7QyaJQzv4xxOMJ6QuOSOFIfWjRAGk5UMXHHcFqttjMs=; b=MT87h55JSflCDywDXWL/Il04z5R9jmDVQqAo/rM9XpDAg7Wulq1hQ1CUVOboobQH6a 81GSlpV9gjisgQAG61X6dTkcIyGR1EymUgzY3KQNUiZ2j+uaDNbz+Lf0lY1JxpwrZG7d V4F2jYDr8DXipJ0O5m5UWNiNy/Rv469b3B6sxEYoYGmEj/FJGhdMkFBpKBhvGT+Htsjf mRdR4cBsE3xiUSge5pt8RwRzD9trW2TKUGfdyKLIxgf79rUgYNFkYe0XZ8nhEQIc3yu9 3Mb/0I8LpAMaN0C5xU8l3XE+eo8MRIEJQ+3xHdtP3B7H+Yexi/8lQPoIHd9Vqof16HVg emMg== X-Gm-Message-State: AOJu0Yx9Lysrx7e6id6d618XmKU/q8d/Yu9DzspFu5dHqAb6LvENqhvA DzKT4veRd3aWBJtPUpYMvIUV/rdoXAU= X-Google-Smtp-Source: AGHT+IHeOlUofEpelwuccUAxumReLhnRs1P2h9mVmbNH6LmiBjv6SdYfQwX2SxrD+fYw6x06mDiMnQ== X-Received: by 2002:a05:600c:5022:b0:40d:5c14:baec with SMTP id n34-20020a05600c502200b0040d5c14baecmr1120502wmr.264.1703739334072; Wed, 27 Dec 2023 20:55:34 -0800 (PST) Received: from [127.0.0.1] ([13.74.141.28]) by smtp.gmail.com with ESMTPSA id n7-20020a05600c4f8700b0040d5daa9092sm4508972wmq.44.2023.12.27.20.55.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Dec 2023 20:55:33 -0800 (PST) Message-ID: In-Reply-To: References: From: "Josh Soref via GitGitGadget" Date: Thu, 28 Dec 2023 04:55:23 +0000 Subject: [PATCH v3 8/9] SubmittingPatches: clarify GitHub artifact format Fcc: Sent Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 To: git@vger.kernel.org Cc: Elijah Newren , =?UTF-8?Q?Ren=C3=A9?= Scharfe , Phillip Wood , Josh Soref , Dragan Simic , Josh Soref , Josh Soref From: Josh Soref GitHub wraps artifacts generated by workflows in a .zip file. Internally, workflows can package anything they like in them. A recently generated failure artifact had the form: windows-artifacts.zip Length Date Time Name --------- ---------- ----- ---- 76001695 12-19-2023 01:35 artifacts.tar.gz 11005650 12-19-2023 01:35 tracked.tar.gz --------- ------- 87007345 2 files Signed-off-by: Josh Soref --- Documentation/SubmittingPatches | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 0665f89f38c..5e2e13b5e09 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -606,7 +606,8 @@ If a branch does not pass all test cases then it will be marked with a red +x+, instead of a green check. In that case, you can click on the failing job and navigate to "ci/run-build-and-tests.sh" and/or "ci/print-test-failures.sh". You can also download "Artifacts" which -are tarred (or zipped) archives with test data relevant for debugging. +are zip archives containing tarred (or zipped) archives with test data +relevant for debugging. Then fix the problem and push your fix to your GitHub fork. This will trigger a new CI build to ensure all tests pass. -- gitgitgadget