[Bug 32087] New: External environment variables interfere with cmd runtest, causing it to issue false errors

http://bugs.winehq.org/show_bug.cgi?id=32087

Bug #: 32087
           Summary: External environment variables interfere with cmd
                    runtest, causing it to issue false errors
           Product: Wine
           Version: 1.5.15
          Platform: x86-64
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: cmd
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
    Classification: Unclassified

Created attachment 42301
  --> http://bugs.winehq.org/attachment.cgi?id=42301
Examples of failed and successful 'make test' output

Runtest ('make test') in programs/cmd/tests fails for me (see attachment for
test output).  The likely cause is due to the command 'set BA' in the 'Testing
set' section of test_builtins.cmd.  When cmd is given this command, it echoes
all environment variables that begin with BA as well as the desired output
BAZ=bazbaz, which throws the test output out of sync with the expected output. 
I am able to fix the problem by unsetting such variables (e.g. BASH_ENV) before
running 'make test'.  The cmd documentation states that importing variables
into cmd from the shell environment is a desired feature, thus I would
recommend that the cmd test suite selectively unset or unexport environment
variables prior to running the test (but please do not unset critical ones like
DISPLAY).

This problem may be related to bug # 31889.