From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/netcdf/
Date: Wed, 29 May 2024 23:46:54 +0000 (UTC) [thread overview]
Message-ID: <1717026367.7aa3a581c47230c4df31588134acd090b67cc984.sam@gentoo> (raw)
commit: 7aa3a581c47230c4df31588134acd090b67cc984
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Wed May 29 23:34:59 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed May 29 23:46:07 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7aa3a581
sci-libs/netcdf: fix bad bash scripting leading to failed tests
If USE=-mpi, a file in src_test is NOT sedded to fix a bug in the file,
because the file does not exist. But this condition was incorrectly
coded.
In bash:
```
cmd1 && cmd2 || cmd3
```
is a code smell. If either of the first two commands fails, the third
command is run -- in this case, die. In other words, the first two
commands were *supposed* to be "only run cmd2 if it makes sense to".
Instead, if it "doesn't make sense to" run cmd2, the die was triggered.
A more general solution is to spec the build format to require all
commands to pass without manually `die`ing (leading to the use of &&
ceasing in general), but that is not how portage works. Either way, the
solution is using `if` as intended.
ref. https://mywiki.wooledge.org/BashGuide/TestsAndConditionals
Closes: https://bugs.gentoo.org/933136
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
sci-libs/netcdf/netcdf-4.9.2-r1.ebuild | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/sci-libs/netcdf/netcdf-4.9.2-r1.ebuild b/sci-libs/netcdf/netcdf-4.9.2-r1.ebuild
index 458001188497..a751713a52c2 100644
--- a/sci-libs/netcdf/netcdf-4.9.2-r1.ebuild
+++ b/sci-libs/netcdf/netcdf-4.9.2-r1.ebuild
@@ -89,8 +89,9 @@ src_configure() {
}
src_test() {
- [[ -f "${BUILD_DIR}/nc_test4/run_par_test.sh" ]] && \
- sed -e 's/mpiexec/mpiexec --use-hwthread-cpus/g' -i "${BUILD_DIR}/nc_test4/run_par_test.sh" || die
+ if [[ -f "${BUILD_DIR}/nc_test4/run_par_test.sh" ]]; then
+ sed -e 's/mpiexec/mpiexec --use-hwthread-cpus/g' -i "${BUILD_DIR}/nc_test4/run_par_test.sh" || die
+ fi
cmake_src_test
}
next reply other threads:[~2024-05-29 23:46 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 23:46 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-18 22:21 [gentoo-commits] repo/gentoo:master commit in: sci-libs/netcdf/ Jakov Smolić
2024-10-19 17:33 Michał Górny
2024-07-27 7:07 Arthur Zamarin
2024-05-30 4:36 Ionen Wolkens
2024-04-02 11:29 Sam James
2023-03-31 11:42 Arthur Zamarin
2023-03-31 11:42 Arthur Zamarin
2023-03-16 17:41 Arthur Zamarin
2023-03-15 10:50 Sam James
2023-03-15 5:53 Sam James
2023-03-15 5:45 Sam James
2023-03-05 4:13 Sam James
2022-06-13 7:12 Agostino Sarubbo
2022-06-13 7:07 Agostino Sarubbo
2022-06-11 5:02 Sam James
2022-06-08 5:25 Sam James
2022-05-11 8:02 Agostino Sarubbo
2022-05-10 13:47 Agostino Sarubbo
2022-01-11 21:37 Jakov Smolić
2022-01-11 21:37 Jakov Smolić
2021-12-28 22:00 Sam James
2021-12-28 22:00 Sam James
2021-08-14 23:15 Marek Szuba
2021-02-25 19:07 Sam James
2021-02-25 8:56 Sam James
2021-02-25 8:56 Sam James
2021-02-25 8:50 Sam James
2021-02-22 18:57 Sam James
2021-02-19 20:12 Thomas Deutschmann
2021-01-17 13:37 Pacho Ramos
2021-01-17 13:37 Pacho Ramos
2020-12-28 16:11 David Seifert
2019-09-14 6:52 Matt Turner
2018-10-13 15:49 Sergei Trofimovich
2018-10-05 17:11 Mikle Kolyada
2018-10-05 12:25 Thomas Deutschmann
2018-09-30 10:10 Pacho Ramos
2018-05-16 22:57 Aaron Bauman
2018-04-24 16:19 Matthias Maier
2018-04-24 15:58 Matthias Maier
2017-08-27 14:03 Sergei Trofimovich
2017-07-15 10:25 Sergei Trofimovich
2017-07-15 10:10 Sergei Trofimovich
2016-12-28 11:25 Pacho Ramos
2016-12-28 11:25 Pacho Ramos
2016-12-28 11:25 Pacho Ramos
2016-01-25 9:52 David Seifert
2016-01-23 20:05 David Seifert
2016-01-20 8:20 Justin Lecher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1717026367.7aa3a581c47230c4df31588134acd090b67cc984.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox