5
61%
master: 63%

Ran 25 Sep 2025 02:46PM UTC

Files 88

Run time 5s

Badge

Embed ▾

Committed 25 Sep 2025 02:04PM UTC coverage: 61.078% (-0.2%) from 61.228%

Job # 6396408028200960.5

Build Type

Pull #10236

CirrusCI

Committed by

SomberNight

Commit Message

contrib: "set -e" behaves weird in subshells followed by OR. don't use.

This exits as expected:
```
$ cat s1.sh
#!/bin/bash
set -e
(
    echo "a"
    false
    echo "b"
)

$ ./s1.sh
a
```
This does NOT exit, seemingly because of the outer context?!
```
$ cat s2.sh
#!/bin/bash
set -e
(
    echo "a"
    false
    echo "b"
) || echo "c"

$ ./s2.sh
a
b
```

ref https://unix.stackexchange.com/questions/65532/why-does-set-e-not-work-inside-subshells-with-parenthesis-followed-by-an-or

Pull Request Pull Request #10236: contrib: "set -e" behaves weird in subshells followed by OR. don't use.

Run Details

22821 of 37364 relevant lines covered (61.08%)

0.61 hits per line

spesmilo / electrum / 6396408028200960 / 5
61%
master: 63%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 6396408028200960.5

spesmilo / electrum / 6396408028200960 / 5 61% master: 63%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 6396408028200960.5

spesmilo / electrum / 6396408028200960 / 5
61%
master: 63%

README BADGES
x