On Fri, Nov/10/2006 11:11:39PM, MTT wrote: > #132: Print BIG WARNING in client if MTTDatabase fails to submit properly > --------------------------+------------------------------------------------- > Reporter: jsquyres | Owner: emallove > Type: defect | Status: new > Priority: blocker | Milestone: v1.1 > Component: Client side | Version: trunk > Resolution: | Keywords: > --------------------------+------------------------------------------------- > Old description: > > > Add some intelligence in submit.php so that it knows when an insert into > > the database has failed. > > > > Somehow convey back to the client that one or more inserts has failed so > > that the client can print out a '''BIG HAIRY WARNING''' that the results > > did not get successfully insertted. When this happens, automatically > > drop a database debug file containing all the data (so that it isn't > > lost) and include its filename in the '''BIG HAIRY WARNING.''' This file > > can then be analyzed later for a post mortem, etc. Be sure that this > > file is ''always'' dropped when there's a database insert error, > > regardless of what the INI file setting is for dropping database debug > > files. > > > > Bonus points will be awarded if submit.php can communicate back to the > > client ''which'' results failed to submit, but that's not a huge deal > > (we'll be able to do this better in 2.0). > > > > The '''BIG HAIRY WARNING''' should probably be output by the client both > > when it happens and at the very end of the run so that if all you see in > > the morning is the end of the MTT run on the screen, the warning is there > > and the user don't have to search through the output just to know if > > their data submitted properly or not. > > New description: > > Add some intelligence in submit.php so that it knows when an insert into > the database has failed. > > Somehow convey back to the client that one or more inserts has failed so > that the client can print out a '''BIG HAIRY WARNING''' that the results > did not get successfully insertted. When this happens, automatically drop > a database debug file containing all the data (so that it isn't lost) and > include its filename in the '''BIG HAIRY WARNING.''' This file can then > be analyzed later for a post mortem, etc. Be sure that this file is > ''always'' dropped when there's a database insert error, regardless of > what the INI file setting is for dropping database debug files. > > Bonus points will be awarded if submit.php can communicate back to the > client ''which'' results failed to submit, but that's not a huge deal > (we'll be able to do this better in 2.0). > > The '''BIG HAIRY WARNING''' should probably be output by the client both > when it happens and at the very end of the run so that if all you see in > the morning is the end of the MTT run on the screen, the warning is there > and the user don't have to search through the output just to know if their > data submitted properly or not.
I'm used grepping on the --debug output from client/mtt, which means e.g., I will now see double the number of POSTGRES ERRORs. Isn't that confusing? At the *end* of the mtt run, I'd much prefer to just say, e.g., "34 SQL errors occured". If they want to see the actual SQL error messages from submit.php, users can do: $ client/mtt --debug ... | tee debug && grep -i POSTGRES debug If submit.php?debug is used, the exact submission entry that caused the error(s) can be traced. > > The should be done on the trunk and the release branch; the code will > likely be at least slightly different between the two, but quite similar. > > -- > Ticket URL: <http://svn.open-mpi.org/trac/mtt/ticket/132> > MTT <http://www.open-mpi.org/> > Issue tracking for the MPI Testing Tool. -- -Ethan
