postgres.git / summary / log / commit / refs

commit    0c400445dbe316d67d19f79fdd096f0b77458b86
Author:   Andres Freund <andres@anarazel.de>
Date:     Thu Sep 22 00:15:54 2022 +0000
First released in: 16.0, 15.0

    ci: windows: set error mode to not include SEM_NOGPFAULTERRORBOX
    
    Cirrus defaults to SetErrorMode(SEM_NOGPFAULTERRORBOX | ...). That prevents
    crash reporting from working unless binaries do SetErrorMode()
    themselves. Furthermore, it appears that either python or, more likely, the C
    runtime has a bug where SEM_NOGPFAULTERRORBOX can very occasionally *trigger*
    a crash on process exit - which is hard to debug, given that it explicitly
    prevents crash dumps from working...
    
    Discussion: https://postgr.es/m/20220909235836.lz3igxtkcjb5w7zb%40awork3.anarazel.de
    Backpatch: 15-, where CI was added


 .cirrus.yml | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/.cirrus.yml b/.cirrus.yml
index df91b893537..fe8da021eda 100644
--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -386,6 +386,15 @@ task:
     # currently have a tool for that...
     CIRRUS_ESCAPING_PROCESSES: 1
 
+    # Cirrus defaults to SetErrorMode(SEM_NOGPFAULTERRORBOX | ...). That
+    # prevents crash reporting from working unless binaries do SetErrorMode()
+    # themselves. Furthermore, it appears that either python or, more likely,
+    # the C runtime has a bug where SEM_NOGPFAULTERRORBOX can very
+    # occasionally *trigger* a crash on process exit - which is hard to debug,
+    # given that it explicitly prevents crash dumps from working...
+    # 0x8001 is SEM_FAILCRITICALERRORS | SEM_NOOPENFILEERRORBOX
+    CIRRUS_WINDOWS_ERROR_MODE: 0x8001
+
   only_if: $CIRRUS_CHANGE_MESSAGE !=~ '.*\nci-os-only:.*' || $CIRRUS_CHANGE_MESSAGE =~ '.*\nci-os-only:[^\n]*windows.*'
 
   windows_container:


[parent: 08ddb3c0852d]