BIND 10 #1878: lettuce tests should be more fail safe about runtime environment
BIND 10 Development
do-not-reply at isc.org
Tue Apr 17 05:31:08 UTC 2012
#1878: lettuce tests should be more fail safe about runtime environment
-------------------------------------+-------------------------------------
Reporter: | Owner: UnAssigned
jinmei | Status: new
Type: | Milestone: Next-Sprint-
defect | Proposed
Priority: | Resolution:
medium | Sensitive: 0
Component: build | Sub-Project: Core
system | Estimated Difficulty: 0
Keywords: | Total Hours: 0
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
okay, so my revised suggestion is to introduce a "run" script:
{{{
% run-lettuce.sh [-I] [feature...]
}}}
If -I is specified, it means the installed environment; otherwise
the in-tree environment should be used and the necessary environment
variables are set internally. In either case it sets the special
LETTUCE_SETUP_COMPLETED environment variable. some terrain script
checks whether this variable is set or not. So simply running
'lettuce' will fail with a warning.
feature... is an optional space-separated list of features. If
explicitly specified, only the specified tests will be run; by default
all features will be run.
'make lettuce' executes this script without any options.
--
Ticket URL: <http://bind10.isc.org/ticket/1878#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list