RPC tests with --tracerpc flag does not increase logging output to stdout (on OSX?) #9986

issue pinheadmz opened this issue on March 13, 2017
  1. pinheadmz commented at 10:02 PM on March 13, 2017: member

    I can't figure out why, but on OSX 10.10.5 with python3 version 3.6.0 adding the flag --tracerpc does not increase the log level to stdout (which, am I mistaken? should be the active terminal session right in front of me, right?). Actually, shouldn't I expect to see more output (from other log levels) than this even without --tracerpc? Or is the extra logging info going somewhere else...?

    $ qa/pull-tester/rpc-tests.py bumpfee
    .................................................................................................................................................................................................................
    bumpfee.py:
    Pass: True, Duration: 105 s
    
    TEST | PASSED | DURATION
    
    bumpfee.py | True   | 105 s
    
    ALL | True   | 105 s (accumulated)
    
    Runtime: 105 s
    $ qa/pull-tester/rpc-tests.py bumpfee --tracerpc
    ...................................................................................................................................................................................................................................
    bumpfee.py:
    Pass: True, Duration: 114 s
    
    TEST | PASSED | DURATION
    
    bumpfee.py | True   | 114 s
    
    ALL | True   | 114 s (accumulated)
    
    Runtime: 114 s
    
  2. MarcoFalke commented at 10:45 PM on March 13, 2017: member

    The rationale was that you only want to debug when the test fails: fa427cef130583440779bce9eacfda537c2e6d14

    Anyway, it seems you are only running a single test, so maybe it is easier to just call ./qa/rpc-tests/bumpfee.py --tracerpc directly

    On Mon, Mar 13, 2017 at 11:02 PM, Matthew Zipkin notifications@github.com wrote:

    I can't figure out why, but on OSX 10.10.5 with python3 version 3.6.0 adding the flag --tracerpc does not increase the log level to stdout (which, am I mistaken? should be the active terminal session right in front of me, right?). Actually, shouldn't I expect to see more output (from other log levels) than this even without --tracerpc? Or is the extra logging info going somewhere else...?

    $ qa/pull-tester/rpc-tests.py bumpfee ................................................................................................................................................................................................................. bumpfee.py: Pass: True, Duration: 105 s

    TEST | PASSED | DURATION

    bumpfee.py | True | 105 s

    ALL | True | 105 s (accumulated)

    Runtime: 105 s $ qa/pull-tester/rpc-tests.py bumpfee --tracerpc ................................................................................................................................................................................................................................... bumpfee.py: Pass: True, Duration: 114 s

    TEST | PASSED | DURATION

    bumpfee.py | True | 114 s

    ALL | True | 114 s (accumulated)

    Runtime: 114 s

    — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bitcoin/bitcoin/issues/9986, or mute the thread https://github.com/notifications/unsubscribe-auth/AGGmv8Tb7LgS_U8qjrgM257qpMaY_NWGks5rlb0LgaJpZM4Mb4Bm .

  3. pinheadmz commented at 10:47 PM on March 13, 2017: member

    Oh thank you!

  4. pinheadmz closed this on Mar 13, 2017

  5. MarcoFalke locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-29 03:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me