|
From: | Jacob Bachmeyer |
Subject: | Re: WARNING: Couldn't find the global config file. |
Date: | Fri, 04 Dec 2020 20:46:25 -0600 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.22) Gecko/20090807 MultiZilla/1.8.3.4e SeaMonkey/1.1.17 Mnenhy/0.7.6.0 |
Rob Savoye wrote:
On 12/3/20 10:05 PM, Jacob Bachmeyer wrote:My guess is that this was somehow related to the testing labs at Cygnus long ago, but I will consider this change for 1.7 and will probably do it if I do not find a reason to keep the warning.Yep. In the beginning, there were tons of problems with people setting up a cross-testing system. The global config file contains the host information of the remote system, and how to access it. People kept wondering why testing wasn't working, hence the warning to create the file. I have a global config file of course, so never see this warning. :-)
It seems that the global init file ($libdir/site.exp by default) mostly obsoletes this use for reading $DEJAGNU, although both will continue to be supported for obvious reasons.
Is the global config file also expected to select remote testing or could the warning be replaced with an error when a remote target is specified but not defined when we are about to start running tests? In the latter case, we could include a hint in the error message to remind the user to check if a global config file should be used and/or to check the site configuration files.
This also suggests that DejaGnu should start tracking which configuration and init files have been loaded, or at least ensure that verbose messages are produced for every file loaded.
-- Jacob
[Prev in Thread] | Current Thread | [Next in Thread] |