[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 2/4] qemu-iotests: remove forceful execution success from
From: |
Kevin Wolf |
Subject: |
Re: [PATCH v2 2/4] qemu-iotests: remove forceful execution success from library files |
Date: |
Fri, 11 Oct 2019 13:25:30 +0200 |
User-agent: |
Mutt/1.12.1 (2019-06-15) |
Am 09.10.2019 um 21:47 hat Cleber Rosa geschrieben:
> Should not be necessary on files that are not executed standalone.
>
> Reviewed-by: Eric Blake <address@hidden>
> Signed-off-by: Cleber Rosa <address@hidden>
Looks fine for common.filter and common.rc, nobody ever checks their
return value.
common.config is included like this:
if ! . "$source_iotests/common.config"
then
_init_error "failed to source common.config"
fi
So as long as we keep this, don't we want to make sure that it returns
success?
Of course, we never really want to return an error from common.config,
so instead of keeping the final 'true' statement, we might consider
changing its inclusion to not check for errors. The case that
potentially changes is when common.config doesn't exist or isn't
readable, but this isn't supposed to ever happen anyway.
Kevin
[PATCH v2 2/4] qemu-iotests: remove forceful execution success from library files, Cleber Rosa, 2019/10/09
- Re: [PATCH v2 2/4] qemu-iotests: remove forceful execution success from library files,
Kevin Wolf <=
[PATCH v2 3/4] qemu-iotests: 044: pass is actually a noop, so remove it, Cleber Rosa, 2019/10/09
[PATCH v2 4/4] qemu-iotests: 044: remove inaccurate docstring class description, Cleber Rosa, 2019/10/09