Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Corentin Henry
    @little-dude
    hi, I'm having trouble to get started with deckard:
    (env) ~/r/deckard ❯❯❯ ./knotd_master_run.sh                                                             
    INFO: Tests require Knot compiled with ./configure --enable-recvmmsg=no
    make: Entering directory '/home/corentih/rust/deckard'
    make[1]: Entering directory '/home/corentih/rust/deckard/contrib/libswrap/obj'
    make[2]: Entering directory '/home/corentih/rust/deckard/contrib/libswrap/obj'
    make[3]: Entering directory '/home/corentih/rust/deckard/contrib/libswrap/obj'
    make[3]: Leaving directory '/home/corentih/rust/deckard/contrib/libswrap/obj'
    [100%] Built target socket_wrapper
    make[2]: Leaving directory '/home/corentih/rust/deckard/contrib/libswrap/obj'
    make[1]: Leaving directory '/home/corentih/rust/deckard/contrib/libswrap/obj'
    loadpath: /home/corentih/rust/deckard/pydnstest
    confpath: /home/corentih/rust/deckard/sets/knotd/master/iter_ns.rpl
    [ FAIL ] sets/knotd/master/iter_ns.rpl
    /augeas/files/home/corentih/rust/deckard/sets/knotd/master/iter_ns.rpl/error: parse_failed
    Traceback (most recent call last):
      File "/home/corentih/rust/deckard/pydnstest/test.py", line 25, in run
        test_callback(name, args, config)
      File "/home/corentih/rust/deckard/deckard.py", line 293, in process_file
        case, cfg_text = scenario.parse_file(os.path.realpath(path))
      File "/home/corentih/rust/deckard/pydnstest/scenario.py", line 1032, in parse_file
        confpath=path, lens='Deckard', loadpath=os.path.dirname(__file__))
      File "/home/corentih/rust/deckard/pydnstest/augwrap.py", line 78, in __init__
        raise RuntimeError(err_msg)
    RuntimeError: /augeas/files/home/corentih/rust/deckard/sets/knotd/master/iter_ns.rpl/error: parse_failed
    make: *** [Makefile:50: sets/knotd/master/iter_ns.out] Error 1
    make: Leaving directory '/home/corentih/rust/deckard'
    do you have any idea what this error means?
    I have a fresh python3 virtualenv:
    cffi==1.11.2
    deckard==3.0
    dnspython==1.15.0
    Jinja2==2.10
    MarkupSafe==1.0
    pycparser==2.18
    python-augeas==1.0.3
    PyYAML==3.12
    Petr Špaček
    @pspacek
    I will have a look.
    This is interesting, on my system I have python3-augeas-0.5.0-8.fc26.noarch and it seems to work.
    The C library on my system is augeas-libs-1.8.1-1.fc26.x86_64
    Oh wait, you are trying to run sets/knotd/master!
    I fear that we did not touch sets/knotd/master in last year so it was forgotten and untested when we rewrote parser. Can you try sets/resolver?
    @little-dude ^^^
    Petr Špaček
    @pspacek
    Now I can see that sets/knotd do not work even on my system. We forgot to update them to the new format. Please take inspiration how it should look like from sets/resolver or documentation.
    Corentin Henry
    @little-dude
    @pspacek sorry I closed the gitter tab. I'm not used to gitter yet :)
    thanks for the answer
    mmh kresd does not seem to be part of the knot package on archlinux unfortunately
    ah but there's an aur package.
    Petr Špaček
    @pspacek
    Knot Resolver and Knot DNS are two separate software packages.
    Corentin Henry
    @little-dude
    btw the reason I'm looking at deckard is that I'd like to run deckard tests for trust-dns: bluejekyll/trust-dns#219
    Petr Špaček
    @pspacek
    Sorry for the confusing names. When guys started Knot DNS they had no idea that they will start writting a resolver some day.
    Corentin Henry
    @little-dude
    got it
    Petr Špaček
    @pspacek
    Oh, I haven't heard of TRust-DNS yet.
    Corentin Henry
    @little-dude
    ah nice, tests are running for kresd
    Petr Špaček
    @pspacek
    Anyway, "If TRust-DNS implements an interpreter for the scripts, then it can reuse these tests." does not sound right to me. Deckard allows you to run different software under it so you just configure Deckard to run different binary with particular parameters and that should be it.
    (Theoretically, devil is in the details.)
    I mean - reimplementing parser and logic is A LOT work, trust me - we are doing that right now :-)
    Corentin Henry
    @little-dude
    yeah, this is misleading
    not knowing deckard, this confused me
    are tests supposed to pass for kresd ? At least one is failing for me:
    [ FAIL ] sets/resolver/iter_minim_ns.rpl
    'utf-8' codec can't decode byte 0x80 in position 1533: invalid start byte
    Traceback (most recent call last):
      File "/home/corentih/rust/deckard/pydnstest/test.py", line 25, in run
        test_callback(name, args, config)
      File "/home/corentih/rust/deckard/deckard.py", line 310, in process_file
        prog_under_test_ip)
      File "/home/corentih/rust/deckard/deckard.py", line 353, in run_testcase
        for line in logf:
      File "/home/corentih/rust/deckard/env/lib/python3.6/codecs.py", line 321, in decode
        (result, consumed) = self._buffer_decode(data, self.errors, final)
    UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 1533: invalid start byte
    Petr Špaček
    @pspacek
    They will pass on kresd master. I suppose that you have some older version.
    (Tests are developing along with kresd.)
    Corentin Henry
    @little-dude
    1.2.3
    Petr Špaček
    @pspacek
    Yeah, that is half a year old.
    Corentin Henry
    @little-dude
    most tests are for resolvers, right? the only server tests are under sets/knotd/{master,slave}
    Petr Špaček
    @pspacek
    Yes, that's because we do not have enough hands. We would welcome tests for authoritatives as well.
    Corentin Henry
    @little-dude
    I see, I might be able to help then (:
    although to be honest, I'm a newbie with DNS. I'm currently going through the "DNS & Bind" book
    Petr Špaček
    @pspacek
    Then have fun! :-)
    Corentin Henry
    @little-dude
    thanks!
    Petr Špaček
    @pspacek
    I'm going off-line for today but please do not hesitate to contact me or open issues in the Deckard Gitlab whenever you encounter a problem in Deckard.
    See you later!
    Corentin Henry
    @little-dude
    I will, see you!
    and thanks :)
    ah for the knot test
    the SCENARIO_END was missing
    I'll make a PR
    Corentin Henry
    @little-dude
    well I found my first bug thanks to deckard: bluejekyll/trust-dns#314
    Petr Špaček
    @pspacek
    @little-dude Thank you for merge request proposal/bug hunting! We will have a look how to reconfigure our Gitlab so you can make forks as needed.
    Petr Špaček
    @pspacek
    @little-dude You should be able to create your fork now.