bugDejaGnu - Bugs: bug #17176, tests fail in 1.4.4 release

 
 

bug #17176: tests fail in 1.4.4 release

Submitter:  Brant Langer Gurganus <brantgurga>
Submitted:  Sat 22 Jul 2006 12:04:47 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Works For Me
Privacy:  Public Assigned to:  None
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 10 Mar 2011 11:03:05 PM UTC, comment #2: 

It works here (I just ran the testsuite 100 times for good measure).  If there is a problem with config.guess, then please report that to config-patches@gnu.org.  What system are you running on?  x86 Linux?

Ben Elliston <bje>
Group administrator
Thu 24 Aug 2006 07:48:09 PM UTC, comment #1: 

I have experienced the exact same failures.

The failures for the options.exp and stats.exp tests are due (in my case) to not having mktemp installed in the build environment. Note that I get these errors with 1.4.4 release, not CVS version as in original report. The testsuite/site.exp that is generated contains a spurious warning message from config.guess: "Warning: creating insecure temp directory". This causes an error when runtest sources the site.exp and that is responsible for the failures. Here is an extract from my runtest.log:

Running /usr/src/dejagnu/dejagnu-1.4.4/testsuite/runtest.all/options.exp ...
Loading ../../src/lib/util-defs.exp
Spawning "runtest -v --tool xXx -srcdir /usr/src/dejagnu/dejagnu-1.4.4/testsuite
/runtest.all "
Expect binary is expect
Using /usr/src/dejagnu/dejagnu-1.4.4/runtest.exp as main test driver
Verbose level is 1
Login name is builder
Found /var/src/build/dejagnu/bld/testsuite/site.exp
ERROR: tcl error sourcing /var/src/build/dejagnu/bld/testsuite/site.exp.
invalid command name "Warning:"
    while executing
"Warning: creating insecure temp directory"
    (file "/var/src/build/dejagnu/bld/testsuite/site.exp" line 2)

Concerning the first 4 failures in tunit.exp, they seem unrelated. After installing mktemp, I can run the complete testsuite flawlessly 9 times back-to-back in a for-loop. Then immediately after, run it another 9 times and maybe it will fail once or twice. I would say after running the testsuite more than 50 times that it fails about 5-10% of the time on those 4 tests, apparently randomly. The only consistent pattern I have is that if I run two or three concurrent instances of the testsuite, then the failures are more likely. However there seems to be no connection with system load average and I have plenty of free memory on the system.

BTW, I am using Expect 5.43.0 and Tcl 8.4.{11,13} in multiple environments.

Anonymous
Sat 22 Jul 2006 12:04:47 PM UTC, original submission:  

For me, the following tests fail in the 1.4.4 release:

Running ./testsuite/libdejagnu/tunit.exp ...
FAIL: Pass message
FAIL: Fail message
FAIL: Untested message
FAIL: Unresolved message
Running ./testsuite/runtest.all/libs.exp ...

I tried seeing if the CVS copy had this fixed, but even more tests fail there:

Running ./testsuite/libdejagnu/tunit.exp ...
FAIL: Pass message
FAIL: Fail message
FAIL: Untested message
FAIL: Unresolved message
Running ./testsuite/runtest.all/libs.exp ...
Running ./testsuite/runtest.all/options.exp ...
FAIL: Loading library files
FAIL: Bad argument
FAIL: Bad tool name
FAIL: Display help
FAIL: --version
FAIL: --target option
FAIL: --host option
FAIL: --all option
FAIL: --objdir option
FAIL: --tool option
FAIL: --debug option
FAIL: --D0 option
Running ./testsuite/runtest.all/stats-sub.exp ...
Running ./testsuite/runtest.all/stats.exp ...
FAIL: pass
FAIL: fail
FAIL: xpass
FAIL: xfail
FAIL: kpass
FAIL: kfail
FAIL: untested
FAIL: unresolved
FAIL: unsupported

Brant Langer Gurganus <brantgurga>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by bje (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2011-03-11 bje Open/ClosedOpen Closed
    2011-03-10 bje StatusNone Works For Me

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code