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/rocm-smi] rawhide: A build analysis prompt
Date: Wed, 05 Aug 2026 13:45:16 GMT	[thread overview]
Message-ID: <178593751673.1.3835953125819102565.rpms-rocm-smi-e634c4438ace@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/rocm-smi
            Branch : rawhide
            Commit : e634c4438ace3a2956435765b7b05f8e02b3f8ca
            Author : Tom Rix <Tom.Rix@amd.com>
            Date   : 2026-08-05T06:44:43-07:00
            Stats  : +76/-0 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/rocm-smi/c/e634c4438ace3a2956435765b7b05f8e02b3f8ca?branch=rawhide

            Log:
            A build analysis prompt

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..3099e9b
--- /dev/null
+++ b/prompts/build.xml
@@ -0,0 +1,76 @@
+<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-name>
+
+  the package name can be deduced from the spec file and srpm file in parent directory
+
+</package-name>
+
+<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 <command-line-parameter> --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>
+
+<command-line-parameter>
+
+  There may or may not be extra parameters
+  <examples>
+    <example>
+      --with test
+    </example>
+    <example>
+      --with preview
+    </example>
+  </examples>
+  
+</command-line-parameter>
+
+

                 reply	other threads:[~2026-08-05 13:45 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=178593751673.1.3835953125819102565.rpms-rocm-smi-e634c4438ace@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