Patch 1992 harness: remove propIsMergeable (and 2 more)

Title harness: remove propIsMergeable (and 2 more)
Superseder Nosy List bf
Related Issues
Status accepted Assigned To

Created on 2020-02-16.23:08:21 by bf, last changed 2020-06-20.08:42:10 by bf.

File name Status Uploaded Type Edit Remove
harness_-remove-propismergeable.dpatch bf, 2020-02-16.23:08:21 application/x-darcs-patch
patch-preview.txt bf, 2020-02-16.23:08:21 text/x-darcs-patch
unnamed bf, 2020-02-16.23:08:21 text/plain
See mailing list archives for discussion on individual patches.
msg21845 (view) Author: bf Date: 2020-02-16.23:08:21
A few more patches to the test harness.

3 patches for repository http://darcs.net/screened:

patch a12d103d29765fab991507c7a95eae9953e0c64e
Author: Ben Franksen <ben.franksen@online.de>
Date:   Sun Feb 16 20:20:13 CET 2020
  * harness: remove propIsMergeable
  This test is completely redundant. It merely checks whether flattening a
  Tree of patches crashes. We test this much more thoroughly with the other
  merge tests.

patch 8bdf254c283ee059d5b2d47d984588de9e966859
Author: Ben Franksen <ben.franksen@online.de>
Date:   Sun Feb 16 20:32:47 CET 2020
  * harness: remove a TODO comment
  The legacy Tree based generator cannot be extended with conflict resolution
  patches. This is instead tested with propConsistentReorderings (which is
  equivalent, given the merge-commute law).

patch e815b0588d34b797b1ad4d297fbf3fdba6d8dead
Author: Ben Franksen <ben.franksen@online.de>
Date:   Sun Feb 16 22:22:09 CET 2020
  * renamed D.T.P.Arbitrary.PrimV3X to NamedPrimX
msg21846 (view) Author: bf Date: 2020-02-16.23:10:25
I think these should be uncontroversial.
msg21935 (view) Author: ganesh Date: 2020-02-27.07:12:57
All fine
Date User Action Args
2020-02-16 23:08:21bfcreate
2020-02-16 23:10:25bfsetstatus: needs-screening -> needs-review
messages: + msg21846
2020-02-27 07:12:57ganeshsetstatus: needs-review -> accepted-pending-tests
messages: + msg21935
2020-06-20 08:42:10bfsetstatus: accepted-pending-tests -> accepted