diff mbox series

b4 send - missing patch in lore

Message ID c967f103-f6e5-4f2c-829a-b9e806f9075c@suse.com (mailing list archive)
State New
Headers show
Series b4 send - missing patch in lore | expand

Commit Message

Andrea Cervesato April 11, 2025, 9:12 a.m. UTC
Hi,

I used the "b4 send" command to send a patch-series via sendmail, but 
the below patch has been skipped by the ML service (lore/patchwork).
It never happened to me and this is the only patch-series with this problem.

As you can see here, everything is fine according to b4 send command:

Converted the branch to 5 messages
---
To: ltp@lists.linux.it
Cc: Andrea Cervesato <andrea.cervesato@suse.com>
---
   [PATCH v4 0/4] Support for Patchwork CI
   [PATCH v4 1/4] ci: install dependences for patchwork-ci script
   [PATCH v4 2/4] ci: add patchwork-ci script
   [PATCH v4 3/4] ci: add ci-patchwork-trigger workflow
   [PATCH v4 4/4] ci: apply patchwork series in ci-docker-build workflow
---
Ready to:
   - send the above messages to actual listed recipients
   - with envelope-from: Andrea Cervesato <andrea.cervesato@suse.de>
   - via SMTP server imap.suse.de
   - tag and reroll the series to the next revision

Press Enter to proceed or Ctrl-C to abort
Connecting to imap.suse.de:587
---
   [PATCH v4 0/4] Support for Patchwork CI
   [PATCH v4 1/4] ci: install dependences for patchwork-ci script
   [PATCH v4 2/4] ci: add patchwork-ci script
   [PATCH v4 3/4] ci: add ci-patchwork-trigger workflow
   [PATCH v4 4/4] ci: apply patchwork series in ci-docker-build workflow
---
Sent 5 messages
Tagging sent/20250410-patchwork_ci-7dc4ae02c40d-v4
Recording series message-id in cover letter tracking
Created new revision v5
Updating cover letter with templated changelog entries.
Invoking git-filter-repo to update the cover letter.
New history written in 0.06 seconds...
Completely finished after 0.12 seconds.

Also cover letter shows the patch 3/4 in the list, but, still, in 
lore/patchwork the patch 3/4 is not available:
https://patchwork.ozlabs.org/project/ltp/list/?series=452273
https://lore.kernel.org/ltp/20250411-patchwork_ci-v4-0-7f3c5ba298a1@suse.com/T/#t
I can confirm that smtp server has never had any issue so far and many 
people are using it on a daily basis.

Did you experienced something similar before?

Best regards,
Andrea Cervesato

-------- Forwarded Message --------
Subject:     [PATCH v4 3/4] ci: add ci-patchwork-trigger workflow
Date:     Fri, 11 Apr 2025 10:01:58 +0200
From:     Andrea Cervesato <andrea.cervesato@suse.de>
To:     ltp@lists.linux.it
CC:     Andrea Cervesato <andrea.cervesato@suse.com>


From: Andrea Cervesato <andrea.cervesato@suse.com>

Add ci-patchwork-trigger workflow that is meant to run every 30 minutes,
checking for new untested LTP patches in the Mailing List and running
the ci-docker-build workflow on them.

Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
---
.github/workflows/ci-patchwork-trigger.yml | 63 
++++++++++++++++++++++++++++++
1 file changed, 63 insertions(+)
diff mbox series

Patch

diff --git a/.github/workflows/ci-patchwork-trigger.yml 
b/.github/workflows/ci-patchwork-trigger.yml
new file mode 100644
index 
0000000000000000000000000000000000000000..ff8e5606f17327f461e9aeec803fbffaac1b1a8f
--- /dev/null
+++ b/.github/workflows/ci-patchwork-trigger.yml
@@ -0,0 +1,63 @@ 
+# Copyright (c) 2025 Andrea Cervesato <andrea.cervesato@suse.com>
+
+name: "Patchwork checker"
+on:
+ push:
+ schedule:
+ - cron: '*/30 * * * *'
+
+env:
+ PATCHWORK_CI_FILE: patchwork-ci-output.txt
+
+jobs:
+ checker:
+ runs-on: ubuntu-latest
+ steps:
+ - name: Git checkout
+ uses: actions/checkout@v1
+
+ - name: Verify new patches
+ id: verify
+ run: |
+ ./ci/patchwork-ci.sh verify > "$PATCHWORK_CI_FILE"
+ cat "$PATCHWORK_CI_FILE"
+
+ - name: Run tests
+ if: success()
+ uses: actions/github-script@v7
+ with:
+ script: |
+ const fs = require('fs');
+
+ const output = fs.readFileSync(process.env.PATCHWORK_CI_FILE, 'utf8');
+ if (output.length === 0) {
+ console.log("'patchwork-ci.sh verify' output is empty");
+ return;
+ }
+
+ const lines = output.split('\n');
+ if (lines.length === 0) {
+ console.log("No new patch-series found");
+ return;
+ }
+
+ for (const data of lines) {
+ const [series_id, series_mbox] = data.split('|');
+ if (series_id.length === 0 || series_mbox.length === 0) {
+ console.log("Malformed data: ${data}");
+ continue;
+ }
+
+ const response = await github.rest.actions.createWorkflowDispatch({
+ owner: context.repo.owner,
+ repo: context.repo.repo,
+ ref: context.ref,
+ workflow_id: 'ci-docker-build.yml',
+ inputs: {
+ SERIES_ID: series_id,
+ SERIES_MBOX: series_mbox,
+ }
+ });
+
+ console.log(response);
+ }