clover 数据库的文件大小是否有 2GB 限制？
我们有 3 个 clover 数据库，一个用于客户端测试、集成测试和单元测试。
为了计算总覆盖率，我们将这些数据库合并到一个新的 clover 数据库中： 正如您所看到的，这按预期工作（并且过去 18 个月以来一直如此）
[clover-merge] Clover Version 3.0.3, built on October 26 2010 (build-dev)
[clover-merge] Loaded from: C:\devtools\clover-ant-3.0.2-patch101026\lib\clover.jar
[clover-merge] Clover: Commercial License registered to ...
[clover-merge] Merging database 1 of 3: d:\coverage\java\all\coverage/clienttests\coverage.db
[clover-merge] Merging database 2 of 3: d:\coverage\java\all\coverage/integrationtests\coverage.db
[clover-merge] Merging database 3 of 3: d:\coverage\java\all\coverage/junit\coverage.db
[clover-merge] Writing merged database registry [clover-merge] Merge complete
自上周末以来，我在尝试从合并的coveragedb 文件生成报告时遇到以下问题：
[clover-report] Clover Version 3.0.3, built on October 26 2010 (build-dev)
[clover-report] Loaded from: C:\devtools\clover-ant-3.0.2-patch101026\lib\clover.jar
[clover-report] Clover: Commercial License registered to ...
[clover-report] Loading coverage database from: 'd:\coverage\java\all\clover\cloverDB\coverage.db'
[clover-report] Report generation failed: Clover encountered a problem reading the instrumentation registry "d:\coverage\java\all\clover\cloverDB\coverage.db". This database may have been corrupted. Please regenerate.
我检查了该文件并注意到它的大小是（根据 Windows 资源管理器）：2,08 GB（2.244.583.202 字节），刚刚超过 2GB。 我不知道前周末运行的规模，因为我们不保留覆盖数据库， 但由于过程中没有其他任何变化，我认为 2GB 是这里的问题。
We have 3 clover dbs, one for clienttests, integrationtests and unittests.
For calculating the total coverage, we merge those databases into a new clover db:
As you can see, this works as expected (and as it always did for over 18 months now)
[clover-merge] Clover Version 3.0.3, built on October 26 2010 (build-dev)
[clover-merge] Loaded from: C:\devtools\clover-ant-3.0.2-patch101026\lib\clover.jar
[clover-merge] Clover: Commercial License registered to ...
[clover-merge] Merging database 1 of 3: d:\coverage\java\all\coverage/clienttests\coverage.db
[clover-merge] Merging database 2 of 3: d:\coverage\java\all\coverage/integrationtests\coverage.db
[clover-merge] Merging database 3 of 3: d:\coverage\java\all\coverage/junit\coverage.db
[clover-merge] Writing merged database registry [clover-merge] Merge complete
Since last weekend i get the following problem when trying to generate reports from the merged coveragedb file:
[clover-report] Clover Version 3.0.3, built on October 26 2010 (build-dev)
[clover-report] Loaded from: C:\devtools\clover-ant-3.0.2-patch101026\lib\clover.jar
[clover-report] Clover: Commercial License registered to ...
[clover-report] Loading coverage database from: 'd:\coverage\java\all\clover\cloverDB\coverage.db'
[clover-report] Report generation failed: Clover encountered a problem reading the instrumentation registry "d:\coverage\java\all\clover\cloverDB\coverage.db". This database may have been corrupted. Please regenerate.
I checked the file and noticed, that its size is (according to windows explorer): 2,08 GB (2.244.583.202 bytes), which is just over 2GB.
I do not know the sizes of the previous weekends run, since we do not keep the coverage dbs,
but since nothing else changed in the procedure, i assume that 2GB is the problem here.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论