diff options
| author | toofar <toofar@spalge.com> | 2023-07-16 23:30:31 +1200 |
|---|---|---|
| committer | toofar <toofar@spalge.com> | 2023-10-28 08:47:34 +1300 |
| commit | f3e7d64f5f8193c5b164fcac0ec20747f8bdd738 (patch) | |
| tree | 0ee69ee2f5f51c1c53fc1d7c7248599877e206d1 | |
| parent | da6ff429b18186b4db8ff82f3f3019bc320d0a4f (diff) | |
| download | qutebrowser-f3e7d64f5f8193c5b164fcac0ec20747f8bdd738.tar.gz qutebrowser-f3e7d64f5f8193c5b164fcac0ec20747f8bdd738.zip | |
Do raise a smoke test error on debug builds
I don't get it. If you capture the output on a debug build and don't
print it what's the point? And why have --debug args in the workflow if
debug is supposed to be called from a failure in the non debug build? I
feel like I'm missing something here.
Hopefully this lets me actually see some output in CI ...
| -rwxr-xr-x | scripts/dev/build_release.py | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/scripts/dev/build_release.py b/scripts/dev/build_release.py index 6259a72ac..953a2a1be 100755 --- a/scripts/dev/build_release.py +++ b/scripts/dev/build_release.py @@ -238,9 +238,6 @@ def smoke_test(executable: pathlib.Path, debug: bool, qt5: bool) -> None: "", ] - if debug: - print("Not raising smoke test error for debug build") - return raise Exception("\n".join(lines)) # pylint: disable=broad-exception-raised |