Custom Query (4284 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1 - 3 of 4284)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2670 wontfix "A deadlock might be detected" failure on NetBSD naokikambe naokikambe
Description

Fix this build farm failure. http://git.bind10.isc.org/~tester/builder//BIND10/20130129033301-NetBSD4-i386-GCC/logs/unittests.out

From a part of stack traces as following, the dead lock seems to occur between setting up msgq and starting msgq.

======================================================================
ERROR: test_openclose_mccs (__main__.TestStatsHttpd)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jreed/builder/work/BIND10/20130129033301-NetBSD4-i386-GCC/build/src/bin/stats/tests/b10-stats-httpd_test.py", line 604, in setUp
    self.base = BaseModules()
  File "/home/jreed/builder/work/BIND10/20130129033301-NetBSD4-i386-GCC/build/src/bin/stats/tests/test_utils.py", line 534, in __init__
    self.msgq.run()
  File "/home/jreed/builder/work/BIND10/20130129033301-NetBSD4-i386-GCC/build/src/bin/stats/tests/test_utils.py", line 88, in run
    self.server._thread.start()
  File "/usr/pkg/lib/python3.1/threading.py", line 481, in start
    self._started.wait()
  File "/usr/pkg/lib/python3.1/threading.py", line 389, in wait
    self._cond.wait(timeout)
  File "/usr/pkg/lib/python3.1/threading.py", line 229, in wait
    waiter.acquire()
  File "/home/jreed/builder/work/BIND10/20130129033301-NetBSD4-i386-GCC/build/src/bin/stats/tests/test_utils.py", line 52, in sig_handler
    self.fail_handler("A deadlock might be detected")
AssertionError: A deadlock might be detected

======================================================================
ERROR: test_running (__main__.TestStatsHttpd)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jreed/builder/work/BIND10/20130129033301-NetBSD4-i386-GCC/build/src/bin/stats/tests/b10-stats-httpd_test.py", line 604, in setUp
    self.base = BaseModules()
  File "/home/jreed/builder/work/BIND10/20130129033301-NetBSD4-i386-GCC/build/src/bin/stats/tests/test_utils.py", line 533, in __init__
    self.msgq = ThreadingServerManager(MockMsgq)
  File "/home/jreed/builder/work/BIND10/20130129033301-NetBSD4-i386-GCC/build/src/bin/stats/tests/test_utils.py", line 81, in __init__
    self.server = server(*args, **kwargs)
  File "/home/jreed/builder/work/BIND10/20130129033301-NetBSD4-i386-GCC/build/src/bin/stats/tests/test_utils.py", line 110, in __init__
    result = self.msgq.setup()
  File "/home/jreed/builder/work/BIND10/20130129033301-NetBSD4-i386-GCC/build/src/bin/msgq/msgq.py", line 292, in setup
    self.setup_listener()
  File "/home/jreed/builder/work/BIND10/20130129033301-NetBSD4-i386-GCC/build/src/bin/msgq/msgq.py", line 263, in setup_listener
    raise e
  File "/home/jreed/builder/work/BIND10/20130129033301-NetBSD4-i386-GCC/build/src/bin/msgq/msgq.py", line 254, in setup_listener
    self.listen_socket.bind(self.socket_file)
  File "/home/jreed/builder/work/BIND10/20130129033301-NetBSD4-i386-GCC/build/src/bin/stats/tests/test_utils.py", line 52, in sig_handler
    self.fail_handler("A deadlock might be detected")
AssertionError: A deadlock might be detected

#1755 wontfix "ANY_SUB" query in sqlite3_accessor needs to be updated jinmei
Description

See https://lists.isc.org/pipermail/bind10-dev/2012-March/003167.html

In short:

  • we need to revise the query so '%' will be placed last (and so we'll probably have to use rname instead of name)
  • let the caller append the '%'

I also wonder whether this can correctly detect the following case: Zone has b.example.com.

*.example.com.

Query a.b.example.com must result in NXDOMAIN, not wildcard match. It's nicer if we can confirm that too. .

#204 invalid "Class" should be in the zone information, not the RR information in the SQL schema shane
Description

As pointed out in the first Y2 Face to Face meeting, the CLASS information is the same for all records in a zone, so should be in the zone not the RR.

Probably should be done after ticket #203, or at the same time.

1 2 3 4 5 6 7 8 9 10 11
Note: See TracQuery for help on using queries.