I got stuck debugging a bioconda-utils build failure and was surprised that passing --loglevel debug had no impact on the log level of the subcommand conda-build that was run.
To me this appears to be a clear omission that ought to be fixed by passing log level through to relevant, if not all, subcommands that are called by bioconda-utils build.
I got stuck debugging a
bioconda-utils buildfailure and was surprised that passing--loglevel debughad no impact on the log level of the subcommandconda-buildthat was run.To me this appears to be a clear omission that ought to be fixed by passing log level through to relevant, if not all, subcommands that are called by
bioconda-utils build.I think one could add it here to the
argsfor example: https://github.com/bioconda/bioconda-utils/blob/a5882cc87c0e451483d19f8bba701496cc058883/bioconda_utils/build.py#L150-L155See https://matrix.to/#/!MhHkICgthNLZeLiygG:gitter.im/$WeOBUkiNJp1cTuQXp7mOPmZWFqFmO4w5TETB-flZu0k?via=gitter.im&via=matrix.org&via=one.ems.host for context