| commit | d287961f25672d94a38dfdd03d1daa7e3d343c3c | |
| author | Alexander Bulekov <alxndr@bu.edu> | |
| Wed, 19 Aug 2020 06:10:56 +0000 (19 02:10 -0400) | ||
| committer | Thomas Huth <thuth@redhat.com> | |
| Wed, 16 Sep 2020 06:41:06 +0000 (16 08:41 +0200) | ||
| tree | 1e47c3930241d6d6b564598484df265be9c6bac9 | treesnapshot (tar.gz zip) |
| parent | 1f04fa3e002e28b96277bf3f09265a4221cdb39b | commitdiff |
fuzz: Change the way we write qtest log to stderr
Telling QTest to log to /dev/fd/2, essentially results in dup(2). This
is fine, if other code isn't logging to stderr. Otherwise, the order of
the logs is mixed due to buffering issues, since two file-descriptors
are used to write to the same file. We can avoid this, since just
specifying "-qtest" sets the log fd to stderr. If we want to disable
qtest logs, we can just add -qtest-log none.
Reviewed-by: Darren Kenny <darren.kenny@oracle.com>
Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
Message-Id: <20200819061110.1320568-2-alxndr@bu.edu>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Telling QTest to log to /dev/fd/2, essentially results in dup(2). This
is fine, if other code isn't logging to stderr. Otherwise, the order of
the logs is mixed due to buffering issues, since two file-descriptors
are used to write to the same file. We can avoid this, since just
specifying "-qtest" sets the log fd to stderr. If we want to disable
qtest logs, we can just add -qtest-log none.
Reviewed-by: Darren Kenny <darren.kenny@oracle.com>
Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
Message-Id: <20200819061110.1320568-2-alxndr@bu.edu>
Signed-off-by: Thomas Huth <thuth@redhat.com>
| tests/qtest/fuzz/fuzz.c | diffblobblamehistory |