Opened 5 years ago

Closed 5 years ago

#232 closed bug (wontfix)

--enable-fast causes many tests to fail

Reported by: "Rajeev Thakur" <thakur@…> Owned by:
Priority: major Milestone:
Component: mpich Keywords:
Cc:

Description

Configuring trunk with --enable-fast causes many tests to fail (revealed by
specialtests).

http://www.mcs.anl.gov/research/projects/mpich2/todo/specialtests/FastTest-t
est.log

The tests that fail are:
* some of the collectives
* sendflood
* putfence1
* disconnect_reconnect3
* many Fortran and C++ I/O tests

The exact configure options were:
'--enable-fast' '--with-pm=gforker' '--with-device=ch3' 'F90=gfortran'

Rajeev

Change History (5)

comment:1 Changed 5 years ago by Rajeev Thakur

  • id set to 232

This message has 0 attachment(s)

comment:2 Changed 5 years ago by gropp

This may be a consequence of the performance of Nemesis when oversubscribed - these tests perform a great many communications, and may be spending too much time spinning.

comment:3 Changed 5 years ago by Rajeev Thakur

>  This may be a consequence of the performance of Nemesis when
>  oversubscribed - these tests perform a great many
> communications, and may be spending too much time spinning.
> Ticket URL: https://trac.mcs.anl.gov/projects/mpich2/ticket/232

Yes, I ran some of the collectives manually, and they finished after a long
time. But why don't they fail in the other special tests and the nightly
tests? Many asynchronous I/O tests like iwriteshx also fail. Are they comm.
Intensive?

Rajeev

comment:4 Changed 5 years ago by buntinas

That may be it. I believe that with --enable-fast sched-yield isn't called.

comment:5 Changed 5 years ago by thakur

  • Resolution set to wontfix
  • Status changed from new to closed

OK. Resolving for now.

Note: See TracTickets for help on using tickets.