[ https://issues.apache.org/jira/browse/CONNECTORS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258237#comment-13258237 ]
Karl Wright edited comment on CONNECTORS-347 at 4/20/12 1:27 PM: ----------------------------------------------------------------- A postgresql run is as follows: {code} testdb=# select dochash,docid from jobqueue; dochash | docid ------------------------------------------+------------------------------------------------------------------------------------- EE6C0ED002CE9303183FEFEF111D6598203F6295 | C:\wip\mcf\trunk\tests\filesystem\test-postgresql-output\testdata E7DE0B8D3F153CECFD3C57B4D83E59073EC4DD60 | C:\wip\mcf\trunk\tests\filesystem\test-postgresql-output\testdata\testdir 181B9C9FB7F62D24461967391B73FF7CB0B14CD9 | C:\wip\mcf\trunk\tests\filesystem\test-postgresql-output\testdata\test2.txt 24081AC0B03B2394F38D3EB78A3BEDB6CCF1D981 | C:\wip\mcf\trunk\tests\filesystem\test-postgresql-output\testdata\test1.txt 5AA0DB8B2B7D267FAD5E3E0E8926996DEFC4C666 | C:\wip\mcf\trunk\tests\filesystem\test-postgresql-output\testdata\testdir\seconddir 4ED8AFCC917B604C1EE4C83458DB9B7265967F40 | C:\wip\mcf\trunk\tests\filesystem\test-postgresql-output\testdata\testdir\test3.txt (6 rows) testdb=# select parentidhash, childidhash from intrinsiclink; parentidhash | childidhash ------------------------------------------+------------------------------------------ EE6C0ED002CE9303183FEFEF111D6598203F6295 | 181B9C9FB7F62D24461967391B73FF7CB0B14CD9 | EE6C0ED002CE9303183FEFEF111D6598203F6295 24081AC0B03B2394F38D3EB78A3BEDB6CCF1D981 | EE6C0ED002CE9303183FEFEF111D6598203F6295 E7DE0B8D3F153CECFD3C57B4D83E59073EC4DD60 | EE6C0ED002CE9303183FEFEF111D6598203F6295 4ED8AFCC917B604C1EE4C83458DB9B7265967F40 | E7DE0B8D3F153CECFD3C57B4D83E59073EC4DD60 5AA0DB8B2B7D267FAD5E3E0E8926996DEFC4C666 | E7DE0B8D3F153CECFD3C57B4D83E59073EC4DD60 7013D738BB77ED47763449997384046B20B77832 | 5AA0DB8B2B7D267FAD5E3E0E8926996DEFC4C666 (7 rows) testdb=# select parentidhash, distance from hopcount; parentidhash | distance ------------------------------------------+---------- EE6C0ED002CE9303183FEFEF111D6598203F6295 | 0 24081AC0B03B2394F38D3EB78A3BEDB6CCF1D981 | 1 181B9C9FB7F62D24461967391B73FF7CB0B14CD9 | 1 E7DE0B8D3F153CECFD3C57B4D83E59073EC4DD60 | 1 5AA0DB8B2B7D267FAD5E3E0E8926996DEFC4C666 | 2 4ED8AFCC917B604C1EE4C83458DB9B7265967F40 | 2 7013D738BB77ED47763449997384046B20B77832 | 3 (7 rows) testdb=# {code} was (Author: kwri...@metacarta.com): A postgresql run is as follows: {code} testdb=# select dochash,docid from jobqueue; dochash | docid ------------------------------------------+------------------------------------- ------------------------------------------------ EE6C0ED002CE9303183FEFEF111D6598203F6295 | C:\wip\mcf\trunk\tests\filesystem\te st-postgresql-output\testdata E7DE0B8D3F153CECFD3C57B4D83E59073EC4DD60 | C:\wip\mcf\trunk\tests\filesystem\te st-postgresql-output\testdata\testdir 181B9C9FB7F62D24461967391B73FF7CB0B14CD9 | C:\wip\mcf\trunk\tests\filesystem\te st-postgresql-output\testdata\test2.txt 24081AC0B03B2394F38D3EB78A3BEDB6CCF1D981 | C:\wip\mcf\trunk\tests\filesystem\te st-postgresql-output\testdata\test1.txt 5AA0DB8B2B7D267FAD5E3E0E8926996DEFC4C666 | C:\wip\mcf\trunk\tests\filesystem\te st-postgresql-output\testdata\testdir\seconddir 4ED8AFCC917B604C1EE4C83458DB9B7265967F40 | C:\wip\mcf\trunk\tests\filesystem\te st-postgresql-output\testdata\testdir\test3.txt (6 rows) testdb=# select parentidhash, childidhash from intrinsiclink; parentidhash | childidhash ------------------------------------------+------------------------------------- ----- EE6C0ED002CE9303183FEFEF111D6598203F6295 | 181B9C9FB7F62D24461967391B73FF7CB0B14CD9 | EE6C0ED002CE9303183FEFEF111D6598203F 6295 24081AC0B03B2394F38D3EB78A3BEDB6CCF1D981 | EE6C0ED002CE9303183FEFEF111D6598203F 6295 E7DE0B8D3F153CECFD3C57B4D83E59073EC4DD60 | EE6C0ED002CE9303183FEFEF111D6598203F 6295 4ED8AFCC917B604C1EE4C83458DB9B7265967F40 | E7DE0B8D3F153CECFD3C57B4D83E59073EC4 DD60 5AA0DB8B2B7D267FAD5E3E0E8926996DEFC4C666 | E7DE0B8D3F153CECFD3C57B4D83E59073EC4 DD60 7013D738BB77ED47763449997384046B20B77832 | 5AA0DB8B2B7D267FAD5E3E0E8926996DEFC4 C666 (7 rows) testdb=# select parentidhash, distance from hopcount; parentidhash | distance ------------------------------------------+---------- EE6C0ED002CE9303183FEFEF111D6598203F6295 | 0 24081AC0B03B2394F38D3EB78A3BEDB6CCF1D981 | 1 181B9C9FB7F62D24461967391B73FF7CB0B14CD9 | 1 E7DE0B8D3F153CECFD3C57B4D83E59073EC4DD60 | 1 5AA0DB8B2B7D267FAD5E3E0E8926996DEFC4C666 | 2 4ED8AFCC917B604C1EE4C83458DB9B7265967F40 | 2 7013D738BB77ED47763449997384046B20B77832 | 3 (7 rows) testdb=# {code} > MySQL HopCount test sometimes fails > ----------------------------------- > > Key: CONNECTORS-347 > URL: https://issues.apache.org/jira/browse/CONNECTORS-347 > Project: ManifoldCF > Issue Type: Bug > Components: Framework core > Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 > Reporter: Karl Wright > Assignee: Karl Wright > Fix For: ManifoldCF 0.6 > > > The HopcountMySQLIT test sometimes fails complaining that it is expecting to > see 6 documents but only sees 4. > {code} > [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: Wrong > number of documents processed - expected 6, saw 4 > [junit] at > org.apache.manifoldcf.filesystem_tests.HopcountMySQLIT.hopcountCheck(HopcountMySQLIT.java:152) > {code} > This does not happen on every run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira