Skip to content

improve exhaustiveness check by attempting each guard as the consequent #3148

improve exhaustiveness check by attempting each guard as the consequent

improve exhaustiveness check by attempting each guard as the consequent #3148

Triggered via pull request March 3, 2025 22:32
Status Failure
Total duration 25m 11s
Artifacts 23

ci.yml

on: pull_request
Matrix: build
Matrix: build-push-image
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 25 warnings
test (test-lib, issues, ubuntu-22.04, false)
Process completed with exit code 1.
test (test-lib, issues, macos-14, false)
Process completed with exit code 1.
test (test-lib, issues, windows-2019, false)
Process completed with exit code 1.
config
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
config
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
config
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
config
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
config
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
config
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (ubuntu-22.04, 9.6.5, 3.10.3.0, true)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (ubuntu-20.04, 9.4.8, false)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
build (ubuntu-20.04, 9.4.8, false)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (ubuntu-22.04, 9.8.2, 3.10.3.0, true)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (ubuntu-22.04, 9.4.8, 3.10.3.0, true)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (macos-14, 9.4.8, true)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (windows-2019, 9.4.8, true)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (macos-13, 9.4.8, true)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
test (test-lib, constraint-guards, windows-2019, false)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test (test-lib, mono-binds, windows-2019, false)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test (test-lib, parser, windows-2019, false)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test (test-lib, examples, windows-2019, false)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test (test-lib, docstrings, windows-2019, false)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test (test-lib, ffi, windows-2019, false)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test (test-lib, renamer, windows-2019, false)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test (test-lib, enum, windows-2019, false)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test (test-lib, regression, windows-2019, false)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test (test-lib, issues, windows-2019, false)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
test (test-lib, suiteb, windows-2019, false)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Artifacts

Produced during runtime
Name Size
Windows MSI installer (GHC 9.4.8)
59.7 MB
cryptol-3.2.0.99-macos-13-X64 (GHC 9.4.8)
23.7 MB
cryptol-3.2.0.99-macos-13-X64-with-solvers (GHC 9.4.8)
55.1 MB
cryptol-3.2.0.99-macos-14-ARM64 (GHC 9.4.8)
63.2 MB
cryptol-3.2.0.99-macos-14-ARM64-with-solvers (GHC 9.4.8)
91.2 MB
cryptol-3.2.0.99-ubuntu-20.04-X64 (GHC 9.4.8)
43.7 MB
cryptol-3.2.0.99-ubuntu-20.04-X64-with-solvers (GHC 9.4.8)
81.9 MB
cryptol-3.2.0.99-ubuntu-22.04-X64 (GHC 9.4.8)
43.7 MB
cryptol-3.2.0.99-ubuntu-22.04-X64 (GHC 9.6.5)
42.7 MB
cryptol-3.2.0.99-ubuntu-22.04-X64 (GHC 9.8.2)
42.8 MB
cryptol-3.2.0.99-ubuntu-22.04-X64-with-solvers (GHC 9.4.8)
83 MB
cryptol-3.2.0.99-ubuntu-22.04-X64-with-solvers (GHC 9.6.5)
82.1 MB
cryptol-3.2.0.99-ubuntu-22.04-X64-with-solvers (GHC 9.8.2)
82.2 MB
cryptol-3.2.0.99-windows-2019-X64 (GHC 9.4.8)
60.2 MB
cryptol-3.2.0.99-windows-2019-X64-with-solvers (GHC 9.4.8)
98 MB
macos-13-bin
64 MB
macos-13-dist-bin
53.5 MB
macos-14-bin
83.2 MB
macos-14-dist-bin
91.3 MB
ubuntu-22.04-bin
89.9 MB
ubuntu-22.04-dist-bin
81.6 MB
windows-2019-bin
92.9 MB
windows-2019-dist-bin
96.5 MB