{"thread":{"id":"1006","subject":"git testsuite failures","startedAt":"2005-06-22T19:18:35Z","lastAt":"2005-06-23T00:59:17Z","messageCount":3,"participants":["David S. Miller","Jon Seymour","Linus Torvalds"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"5121","messageId":"20050622.121835.78708158.davem@davemloft.net","threadId":"1006","inReplyTo":null,"subject":"git testsuite failures","fromName":"David S. Miller","fromEmail":"davem@davemloft.net","sentAt":"2005-06-22T19:18:35Z","receivedAt":"2005-06-22T19:18:35Z","isPatch":false,"sender":{"key":"davem@davemloft.net","avatar":null},"body":"\nThere are test cases failing in the testsuite over the\npast few days, is this expected?\n\n*** t6001-rev-list-merge-order.sh ***\n ...\n* FAIL 3: simple merge order check_output simple-merge-order git-rev-list --merge-order --show-breaks HEAD\n* FAIL 4: two diamonds merge order (g6) check_output two-diamonds-merge-order-g6 git-rev-list --merge-order --show-breaks g4\n ...\n* FAIL 8: cross-epoch, head at l5, prune at l1 check_output cross-epoch-head-at-l5-prune-at-l1 git-rev-list --merge-order l5 ^l1\n* FAIL 9: duplicated head arguments check_output duplicated-head-arguments git-rev-list --merge-order l5 l5 ^l1\n ...\n* FAIL 20: max-count 10 - merge order check_output max-count-10-merge-order git-rev-list --merge-order --show-breaks --max-count=10 l5\n ...\n* FAIL 23: --max-age=c3, --merge-order check_output max-age-c3-merge-order git-rev-list --merge-order --max-age=51148811 l5\n ...\n"},{"id":"5141","messageId":"2cfc403205062217546434c869@mail.gmail.com","threadId":"1006","inReplyTo":"20050622.121835.78708158.davem@davemloft.net","subject":"Re: git testsuite failures","fromName":"Jon Seymour","fromEmail":"jon.seymour@gmail.com","sentAt":"2005-06-23T00:54:01Z","receivedAt":"2005-06-23T00:54:01Z","isPatch":false,"sender":{"key":"jon.seymour@gmail.com","avatar":"https://avatars.githubusercontent.com/u/207131?v=4"},"body":"I posted a fix for this yesterday. The break was caused by a change in\nbehaviour of parse_commit that the --merge-order stuff was dependent\non. Now that parse_commit is sane, the --merge-order stuff needs to be\nmade sane too.\n\nThe fix was in this patch.\n\n[PATCH 1/1] Fix --merge-order unit test breaks introduced by\n6c88be169881c9223532796bd225e79afaa115e1\n\njon.\n"},{"id":"5142","messageId":"Pine.LNX.4.58.0506221757440.11175@ppc970.osdl.org","threadId":"1006","inReplyTo":"20050622.121835.78708158.davem@davemloft.net","subject":"Re: git testsuite failures","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2005-06-23T00:59:17Z","receivedAt":"2005-06-23T00:59:17Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Wed, 22 Jun 2005, David S. Miller wrote:\n> \n> There are test cases failing in the testsuite over the\n> past few days, is this expected?\n\nFixed now. It was the parent ordering cleanup that broke an assumption\nabout parents being in reverse order in the rev-list \"epoch\" code. I\nchecked in the fix from Jon,\n\n\t\tLinus\n"}]}