This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: QMTest Update


"Joseph S. Myers" <jsm28@cam.ac.uk> writes:

| On 12 Jun 2002, Jim Wilson wrote:
| 
| > being forced to wait until testing is done.  Dejagnu runs tests in alphabetical
| > order, making it easy to compare results by hand against a previous run as
| > they come out.
| 
| Dejagnu doesn't run tests in alphabetical order, it runs them in the order
| the tests appear in the directory, which may be alphabetical if the tree
| was checked out just before building but not if it was checked out a few
| years ago and updated with cvs update since then.

More precisely, Dejagnu runs the tests through a main loop which is
copy/pasted all over the directories and ressembling something like:

  set dirlen [expr [string length "$srcdir/$subdir"] + 1];
  foreach file [lsort [find $srcdir/$subdir *.C]] {
      # If we're only testing specific files and this isn't one of them, skip it.
      set tfile [string range $file $dirlen end];
      if ![runtest_file_p $runtests $tfile] then {
	  continue
      }
      verbose "Testing $file"

      # We don't want old-dejagnu.exp to have to know about all the global
      # variables we use.  For now we tell it about CXXFLAGS and LIBS and
      # leave LDFLAGS alone.
      old-dejagnu $GXX_UNDER_TEST "$file" "$tfile" "" "$DEFAULT_CXXFLAGS" "-lstdc+
  }


Note the "lsort" command.

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]