Linux bluetooth development
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/action-ci] 08efb9: sync_patchwork: don't let one series abort the who...
Date: Thu, 10 Sep 2026 10:52:35 -0700	[thread overview]
Message-ID: <bluez/action-ci/push/refs/heads/main/436a7d-08efb9@github.com> (raw)

  Branch: refs/heads/main
  Home:   https://github.com/bluez/action-ci
  Commit: 08efb9023d9aacdde8a5cf7b9425877d99ba5661
      https://github.com/bluez/action-ci/commit/08efb9023d9aacdde8a5cf7b9425877d99ba5661
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2026-09-10 (Thu, 10 Sep 2026)

  Changed paths:
    M cleanup_pr.py
    M libs/utils.py
    M sync_patchwork.py

  Log Message:
  -----------
  sync_patchwork: don't let one series abort the whole run

An error while processing a series, such as the mail server rejecting the
notification, aborted the script and every series and pull request queued
after it was left untouched until the next run.

Handle the failures per series and per pull request, log them, and keep
going. The exit code still reports that something went wrong so the run
doesn't turn green silently.

Read the PR list before closing any of them as well, otherwise the
pagination shifts and the entries are skipped, and stop reporting a PR
title without a patchwork id as an error since most of them don't have
one.



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/action-ci/settings/notifications

                 reply	other threads:[~2026-09-10 17:52 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=bluez/action-ci/push/refs/heads/main/436a7d-08efb9@github.com \
    --to=noreply@github.com \
    --cc=linux-bluetooth@vger.kernel.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