[ovs-dev] [PATCH 08/12] python tests: Ignore stderr output

[Guru Shetty]

>
>
>
> So you are saying that running $srcdir/test-unixctl.py on Windows
> produces output in stderr. Why? Is there a bug with Windows port?
>
> *[Paul Boca] *This is the way logging library works on both Windows and
> Linux (https://docs.python.org/2/howto/logging.html -
>
> “If you call the functions *debug()*
> <https://docs.python.org/2/library/logging.html#logging.debug>, *info()*
> <https://docs.python.org/2/library/logging.html#logging.info>,*warning()*
> <https://docs.python.org/2/library/logging.html#logging.warning>,
> *error()* <https://docs.python.org/2/library/logging.html#logging.error>
> and *critical()*
> <https://docs.python.org/2/library/logging.html#logging.critical>, they
> will check to see if no
>
> destination is set; and if one is not set, they will set a destination of
> the console (sys.stderr)”)
>
> but the difference is that on Windows the stderr is appended in a file
> (the same file) and on Linux a stderr instance
>
> is used for every command.
>
>
>
I understand what you are trying to say. My question is a little different.
If I add the following incremental, vlog tests in Linux fail and this is
because something is printed in stderr:

diff --git a/tests/test-unixctl.py b/tests/test-unixctl.py
index 5de51d3..f85de39 100644
--- a/tests/test-unixctl.py
+++ b/tests/test-unixctl.py
@@ -76,6 +76,8 @@ def main():
     ovs.unixctl.command_register("block", "", 0, 0, unixctl_block, None)
     ovs.daemon.daemonize_complete()

+    vlog.err("oink")
+
     vlog.info("Entering run loop.")
     poller = ovs.poller.Poller()
     while not exiting:

So the question is - what is it that gets printed in Windows in stderr?
What specific test fails?