Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Z zodbtools
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 4
    • Merge requests 4
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • nexedi
  • zodbtools
  • Merge requests
  • !32

Merged
Created Oct 18, 2024 by Kirill Smelkov@kirrOwner

tests: Fix ztestdata-related tests on ZODB4

  • Overview 0
  • Commits 1
  • Changes 4

In bf772ce0 I introduced ztestdata fixture and we added several tests that use this fixture instead of only zext fixture. But contrary to zext I missed to corresponding xfail if underlying ZODB is ZODB4 and does not support access to raw extension bytes. As the result several tests started to fail with ZODB4, because on such ZODB extension is only dumped via heuristic and on best-effort basis and that cannot match original extension data bit to bit exactly:

https://lab.nexedi.com/nexedi/zodbtools/-/blob/36cba871/zodbtools/zodbdump.py#L93-102

One example failure is here:

https://erp5js.nexedi.net/#/test_result_module/20241017-58899E0D/2

-> Fix that by xfailing in both zext and ztestdata fixtures consistently.

Co-authored-by: Jérome Perrin jerome@nexedi.com

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: y/zodb4
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7