elichai
commented at 9:21 am on July 30, 2020:
contributor
Right now travis.sh checks if VALGRIND and CTIMETEST are set or not, but in travis.yml we explictly set them to yes so I think it’s more intuitive to check if they’re equal to yes such that setting CTIMETEST=no(or anything other than “yes”) will disable the test.
elichai renamed this:
travis.sh check if variable=yes instead of if var is set
Check if variable=yes instead of if var is set in travis.sh
on Jul 30, 2020
real-or-random
commented at 8:45 am on August 3, 2020:
contributor
I think that’s an improvement but then we should do this for BENCH too.
Change travis.sh to check if variables are equal to yes instead of
not-empty.
Before this, setting `VALGRIND=wat` was considered as true, and to make it
evaluate as false you had to unset the variable `VALGRIND=` but not it
checks if `VALGRIND=yes` and if it's not `yes` then it's evaluated to
false
ef37761fee
elichai force-pushed
on Aug 3, 2020
real-or-random
commented at 10:55 am on August 7, 2020:
contributor
elichai
commented at 11:13 am on August 7, 2020:
contributor
We could, but unlike BIGNUM=no which passes to configure and it will check that it contains something valid, here we only check if it’s yes or not, we don’t check if it’s no or something else.
but maybe it’s still worth it for consistency and readability
real-or-random
commented at 12:09 pm on August 7, 2020:
contributor
but maybe it’s still worth it for consistency and readability
That was my thought.
real-or-random
commented at 11:31 am on September 14, 2020:
contributor
This is a metadata mirror of the GitHub repository
bitcoin-core/secp256k1.
This site is not affiliated with GitHub.
Content is generated from a GitHub metadata backup.
generated: 2024-11-21 22:15 UTC
This site is hosted by @0xB10C More mirrored repositories can be found on mirror.b10c.me