------- Comment #3 from janis at gcc dot gnu dot org 2006-09-12 23:23 -------
I'm starting to figure out how all this works. A quick fix for now might be,
as Benjamin suggested, for libstdc++.exp to only change the timeout value if it
doesn't already exist. That could be done with
if [target_info exists gcc,timeout] {
lappend options "timeout=[target_info gcc,timeout]"
} else {
lappend options "timeout=600"
}
If someone here knows how to specify a timeout value in RUNTESTFLAGS or to set
it from .dejagnurc, please let me know.
If other people agree with Steve that it would be useful to be able to change
the timeout value for individual tests, let me know and I'll look into that.
It sounds as if it would get messy to have it be an actual time; perhaps a
multiplier for the normal timeout would be better.
--
janis at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |janis at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28870
