6396408028200960
61%
master: 63%

Ran 25 Sep 2025 02:17PM UTC

Jobs 5

Files 88

Run time 1min

Badge

Embed ▾

Committed 25 Sep 2025 02:04PM UTC coverage: 61.311%. Remained the same

Build # 6396408028200960

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

22839 of 37251 relevant lines covered (61.31%)

3.06 hits per line

Uncovered Existing Lines

Lines	Coverage	∆	File
8	63.14	-0.5%	electrum/util.py

Jobs

ID	Job ID	Ran	Files	Coverage
1	6396408028200960.1	25 Sep 2025 02:17PM UTC	88	61.23
2	6396408028200960.2	25 Sep 2025 02:17PM UTC	88	61.23
3	6396408028200960.3	25 Sep 2025 02:17PM UTC	88	61.23
4	6396408028200960.4	25 Sep 2025 02:19PM UTC	88	61.08
5	6396408028200960.5	25 Sep 2025 02:46PM UTC	88	61.08

spesmilo / electrum / 6396408028200960
61%
master: 63%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Uncovered Existing Lines

Jobs

Source Files on build 6396408028200960

spesmilo / electrum / 6396408028200960 61% master: 63%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Uncovered Existing Lines

Jobs

Source Files on build 6396408028200960

spesmilo / electrum / 6396408028200960
61%
master: 63%

README BADGES
x