[SCM] PostGIS branch master updated. 3.7.0beta1-173-g7bc10724ea

[git at osgeo.org]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "PostGIS".

The branch, master has been updated
       via  7bc10724ea488d17b005ef88d7135c9ce34d0558 (commit)
       via  ef9b2e37ec65d84844d9cc8d6e4ee62cb9d056ac (commit)
      from  7684171f72b40191e6c7eea82a72a7aa0d83cbc2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 7bc10724ea488d17b005ef88d7135c9ce34d0558
Merge: 7684171f72 ef9b2e37ec
Author: Darafei Praliaskouski <komzpa at gmail.com>
Date:   Sun Aug 2 00:51:16 2026 -0700

    Merge pull request 'ci: stop ignoring failures in the s390x big-endian step' (!649) from Komzpa/postgis:ci/s390x-stop-ignoring-failures-20260801 into master
    
    The s390x step carries `failure: ignore`, so big-endian failures cannot fail a pipeline. The
    mute's stated reason was to keep it non-blocking "while the first big-endian findings are still
    being triaged".
    
    Over the 200 most recent pipelines this step completed four times and passed all four. There are
    no findings under triage, so the justification has expired and the mute now only hides whatever
    comes next. This removes it, and replaces the stale comment with what the measurement actually
    says.
    
    The `when:` gating is untouched: s390x still runs on push, tag and cron rather than on every pull
    request, because QEMU plus the geospatial dependency closure is expensive. What changes is only
    that a failure there now fails the workflow, like every other step.
    
    Reviewed-on: https://gitea.osgeo.org/postgis/postgis/pulls/649


commit ef9b2e37ec65d84844d9cc8d6e4ee62cb9d056ac
Author: Darafei Praliaskouski <me at komzpa.net>
Date:   Sat Aug 1 14:13:28 2026 +0400

    ci: stop ignoring failures in the s390x big-endian step
    
    The mute was conditional from the start -- keep it non-blocking "while the
    first big-endian findings are still being triaged" -- and the condition has
    expired without anyone noticing.
    
    Over the 200 most recent pipelines the step completed four times and passed all
    four. Zero failures, so nothing is under triage. A mute whose stated reason has
    no instances left is not protecting anyone; it just means the project's only
    big-endian coverage cannot report a regression.
    
    The gating is untouched: this still runs on master pushes, tags and cron rather
    than on every pull request, because QEMU plus the geospatial dependency closure
    is expensive and that trade-off is still right.
    
    Worth knowing when judging this: four completions in 2.8 days is the whole of
    our big-endian signal, because the step is gated to master pushes and merge
    bursts cancel those. Unmuting makes each of those four count; it does not make
    them more frequent.

diff --git a/.woodpecker/portability.yml b/.woodpecker/portability.yml
index 19e14eb401..6b0eced045 100644
--- a/.woodpecker/portability.yml
+++ b/.woodpecker/portability.yml
@@ -167,15 +167,18 @@ steps:
   s390x-big-endian-qemu:
     image: s390x/debian at sha256:4b236f9aafe8a6201c6dca29ce78c28e1eb1e314ecedc2cd2c545f9e49d060e3
     pull: true
-    failure: ignore
     # s390x is the only realistic big-endian coverage. It is intentionally not
     # run on every pull request: QEMU plus the geospatial dependency closure is
     # expensive, so master pushes, tags, and scheduled runs keep the signal
     # without making every contributor wait for full emulation. Pull requests
     # that change this workflow also run it so image and startup changes prove
-    # themselves before merge. Keep it non-blocking while the first big-endian
-    # findings are still being triaged; Woodpecker will show the failed step
-    # without failing the whole workflow.
+    # themselves before merge.
+    #
+    # It used to carry `failure: ignore`, kept "while the first big-endian
+    # findings are still being triaged". Over the 200 most recent pipelines this
+    # step completed four times and passed all four; there were no findings under
+    # triage, so the mute had nothing left to justify it and a failure here now
+    # fails the workflow like any other.
     when:
       - event: [push, tag, cron]
         branch: master

-----------------------------------------------------------------------

Summary of changes:
 .woodpecker/portability.yml | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
PostGIS