darcs

Patch 452 resolve issue332: ask if test fails

Title resolve issue332: ask if test fails
Superseder Nosy List kerneis
Related Issues
Status obsoleted Assigned To
Milestone

Created on 2010-11-08.16:56:26 by kerneis, last changed 2010-11-08.17:12:59 by kerneis. Tracked on DarcsWatch.

Files
File name Status Uploaded Type Edit Remove
resolve-issue332_-ask-if-test-fails.dpatch kerneis, 2010-11-08.16:56:25 text/x-darcs-patch
unnamed kerneis, 2010-11-08.16:56:25
See mailing list archives for discussion on individual patches.
Messages
msg12942 (view) Author: kerneis Date: 2010-11-08.16:56:25
Hi,

this is another attempt to solve issue332, thanks to an idea of Peter
Rockai.

It removes calls to testTentative from finalizeRepositoryChanges and
changes testTentative and testRecorded to return the exit code of the
test.

Each command which accepts the --test (or --no-test) flag is now
responsible for running the test.  When run in interactive mode, if the
test fails, these commands ask the user to confirm the abort.  When run
in non-interactive mode, the old behaviour is kept.

This patch also contains a fix to the darcs testsuite to handle the new
confirmation.

Calls to finalizeRepositoryChanges in Repository.hs (more precisely
those performed by copyPackedRepository and copyNotPackedRepository)
have not been modified because I believe no test is ever run when a full
copy of repository is done.  The same goes for commands like optimize,
etc.

Best,
Gabriel

1 patch for repository http://darcs.net:

Sun Nov  7 20:19:55 CET 2010  Gabriel Kerneis <kerneis@pps.jussieu.fr>
  * resolve issue332: ask if test fails
Attachments
msg12945 (view) Author: kerneis Date: 2010-11-08.17:12:59
Duplicate of patch454 (sent twice).
History
Date User Action Args
2010-11-08 16:56:26kerneiscreate
2010-11-08 17:08:05darcswatchsetdarcswatchurl: http://darcswatch.nomeata.de/repo_http:__darcs.net_.html#bundle-9de38ad50f86a6dde7150774cc38aee02a9ce180
2010-11-08 17:12:59kerneissetstatus: needs-screening -> obsoleted
messages: + msg12945