BIND 10 #1020: run systest on buildbot

[BIND 10 Development]

#1020: run systest on buildbot
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  jinmei                             |                Status:  assigned
                       Type:  task   |             Milestone:  Next-Sprint-
                   Priority:  major  |  Proposed
                  Component:  build  |            Resolution:
  system                             |             Sensitive:  0
                   Keywords:         |           Sub-Project:  Core
            Defect Severity:  N/A    |  Estimated Difficulty:  4.0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jreed):

 * type:  defect => task


Comment:

 Just a status update: my build framework creates unique directory names
 that are currently too long for the socket length limits.  See ticket
 #360.  I tried to workaround this with shorter symlinks but that failed --
 something in our code replaced the path with the target path. There are
 environment variables and command line switches to choose the msqg and/or
 xfrout socket paths, but those are overridden or ignored due to other
 environment variable settings as used by systest target and the
 run_build.sh. (That is a problem that needs to be fixed!) As a workaround
 I have been patching the systest run? script to choose a different msgq
 socket path.

 So my next step is to change my build framework so I can override the path
 that the builds or installs are done in.

 Changed this from defect to a task.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1020#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development