[PATCH 7/8] SubmittingPatches: clarify GitHub artifact format
- From
Josh Soref via GitGitGadget <gitgitgadget@gmail.com>
- Date
- Dec 19, 2023, 08:41 UTC
- Message-ID
- <cdab65a425944e9d10f6aa6be378162cd5450c81.1702975320.git.gitgitgadget@gmail.com>
- In-Reply-To
- <pull.1623.git.1702975319.gitgitgadget@gmail.com>
From: Josh Soref <jsoref@gmail.com>
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 <jsoref@gmail.com> --- Documentation/SubmittingPatches | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 8e19c7f82e4..b4fa52ae348 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -606,7 +606,8 @@ branches here: `https://github.com/<Your GitHub handle>/git/actions/workflows/ma If a branch did not pass all test cases then it is marked with a red +x+. 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 +can also download "Artifacts" which 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
-- gitgitgadget