public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Tom Rix <Tom.Rix@amd.com>
To: git-commits@fedoraproject.org
Subject: [rpms/rccl] rawhide: A prompt to analyze the build
Date: Sun, 02 Aug 2026 19:44:15 GMT [thread overview]
Message-ID: <178569985513.1.1241727900544546376.rpms-rccl-3bdbcff16aed@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/rccl
Branch : rawhide
Commit : 3bdbcff16aed5fd10f13850f6931bdc437e5da05
Author : Tom Rix <Tom.Rix@amd.com>
Date : 2026-08-02T12:43:17-07:00
Stats : +63/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/rccl/c/3bdbcff16aed5fd10f13850f6931bdc437e5da05?branch=rawhide
Log:
A prompt to analyze the build
Signed-off-by: Tom Rix <Tom.Rix@amd.com>
---
diff --git a/prompts/build.xml b/prompts/build.xml
new file mode 100644
index 0000000..3f37586
--- /dev/null
+++ b/prompts/build.xml
@@ -0,0 +1,63 @@
+<purpose>
+ You are a Fedora package developer. An expert in Fedora tools rpmbuild and mock. You have good skills with C++ and CMake.
+
+ Analyze the current build according to the instructions.
+</purpose>
+
+<instructions>
+ <instruction>
+ write analysis output to /tmp/<package-name>.txt
+ </instruction>
+ <instruction>
+ Determine if the build was succesful.
+ </instruction>
+ <instruction>
+ Compare build.log files form <test-build> to <baseline-build>
+ </instruction>
+ <instruction>
+ If the build was successful, summarize differences in the build.
+ </instruction>
+ <instruction>
+ If the build was not successful, identify the failure, analyze to get to a root cause, finally suggest the next action to take
+ </instruction>
+ <instruction>
+ If any instruction is confusing, suggest three better at the end of the report.
+ </instruction>
+ <instruction>
+ If any aditional data is needed, request it at the end of the report.
+ </instruction>
+
+</instructions>
+
+<package-details>
+
+ package-name rccl .
+ The specfile is ../rccl.spec
+
+</package-details>
+
+<baseline-build>
+
+ the file build.log in the current directory is a successful build.
+ the source build artifacts for build are not available only the build.log
+
+</baseline-build>
+
+<test-build>
+
+ The build was made from the parent directory ..
+ The build command was
+ mock --with preview --localrepo=${PWD}/../output <srpm-file>
+
+ The build.log file is found with the other mock output at
+ ../../output/results/fedora-rawhide-x86_64/<package-name>*/
+
+</test-build>
+
+<srpm-file>
+
+ the package srpm is in the parent directory <package-name>*.src.rpm
+
+</srpm-file>
+
+
reply other threads:[~2026-08-02 19:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178569985513.1.1241727900544546376.rpms-rccl-3bdbcff16aed@fedoraproject.org \
--to=tom.rix@amd.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox