ctest: bmesh_boolean test fails on x86 #65143

Closed
opened 2019-05-26 10:04:31 +02:00 by Ray molenkamp · 11 comments
Member

System Information
Operating system: Windows X86 + Linux X86
Graphics card: N/A

Broken: Latest Master 32 bit
Worked: Latest Master 64 bit

Short description of error

the bmesh_boolean test fails on both windows and linux on 32 bit builds.

Additional information

The reported memleak doesn't seem to trigger on the x64 builds.

Blender 2.80 (sub 72) (hash f18373a9ab1a built Sun 05/26/2019 12:09 AM)
found bundled python: D:\a\1\build_windows_Full_x86_vc15_Release\bin\Release\2.80\python
Read blend: D:/a/1/s/../lib/tests/modeling/bool_regression.blend
Info: Deleted 1 object(s)
Info: Deleted 1 object(s)
Info: Deleted 1 object(s)
Info: Deleted 1 object(s)
Info: Deleted 1 object(s)
Info: Deleted 1 object(s)
Info: Deleted 1 object(s)
Info: Deleted 1 object(s)
Info: Deleted 1 object(s)
Error: Not freed memory blocks: 3, total unfreed memory 0.002487 MB
D:/a/1/s/../lib/tests/modeling/bool_regression.blend\run_tests:4: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
Traceback (most recent call last):
  File "D:/a/1/s/../lib/tests/modeling/bool_regression.blend\run_tests", line 38, in <module>
SystemExit: 1
Run test: intersect_boolean(operation="UNION") on Cubecube selecting F 0 1 2 3 4 5
Success
Info: Deleted 1 object(s)
Run test: intersect_boolean(operation="INTERSECT") on Cubecube selecting F 0 1 2 3 4 5
Fail Loop Vert Mismatch In Poly Test
Info: Deleted 1 object(s)
Run test: intersect_boolean(operation="DIFFERENCE") on Cubecube selecting F 0 1 2 3 4 5
Fail Loop Vert Mismatch In Poly Test
Info: Deleted 1 object(s)
Run test: intersect(separate_mode="CUT") on Cubecube selecting F 0 1 2 3 4 5
Fail Loop Vert Mismatch In Poly Test
Info: Deleted 1 object(s)
Run test: intersect(separate_mode="ALL") on Cubecube selecting F 0 1 2 3 4 5
Fail Edge Mismatch
Info: Deleted 1 object(s)
Run test: intersect(separate_mode="NONE") on Cubecube selecting F 0 1 2 3 4 5
Fail Loop Vert Mismatch In Poly Test
Info: Deleted 1 object(s)
Run test: intersect(mode="SELECT" separate_mode="NONE") on Cubecube selecting F 0 1 2 3 4 5 6 7 8 9 10 11
Fail Loop Vert Mismatch In Poly Test
Info: Deleted 1 object(s)
Run test: intersect_boolean(operation="UNION") on Cubecone selecting F 6 7 8 9 10
Fail Loop Vert Mismatch In Poly Test
Info: Deleted 1 object(s)
Run test: intersect_boolean(operation="UNION") on Cubecones selecting F 0 1 2 3 4 5
Fail Loop Vert Mismatch In Poly Test
Info: Deleted 1 object(s)
Ran 9 tests, 8 failed
Tests Failed

Exact steps for others to reproduce the error
run the bmesh_boolean test or load bool_regression.blend manually and click run script.

**System Information** Operating system: Windows X86 + Linux X86 Graphics card: N/A Broken: Latest Master 32 bit Worked: Latest Master 64 bit **Short description of error** the bmesh_boolean test fails on both windows and linux on 32 bit builds. **Additional information** The reported memleak doesn't seem to trigger on the x64 builds. ``` Blender 2.80 (sub 72) (hash f18373a9ab1a built Sun 05/26/2019 12:09 AM) found bundled python: D:\a\1\build_windows_Full_x86_vc15_Release\bin\Release\2.80\python Read blend: D:/a/1/s/../lib/tests/modeling/bool_regression.blend Info: Deleted 1 object(s) Info: Deleted 1 object(s) Info: Deleted 1 object(s) Info: Deleted 1 object(s) Info: Deleted 1 object(s) Info: Deleted 1 object(s) Info: Deleted 1 object(s) Info: Deleted 1 object(s) Info: Deleted 1 object(s) Error: Not freed memory blocks: 3, total unfreed memory 0.002487 MB D:/a/1/s/../lib/tests/modeling/bool_regression.blend\run_tests:4: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses Traceback (most recent call last): File "D:/a/1/s/../lib/tests/modeling/bool_regression.blend\run_tests", line 38, in <module> SystemExit: 1 Run test: intersect_boolean(operation="UNION") on Cubecube selecting F 0 1 2 3 4 5 Success Info: Deleted 1 object(s) Run test: intersect_boolean(operation="INTERSECT") on Cubecube selecting F 0 1 2 3 4 5 Fail Loop Vert Mismatch In Poly Test Info: Deleted 1 object(s) Run test: intersect_boolean(operation="DIFFERENCE") on Cubecube selecting F 0 1 2 3 4 5 Fail Loop Vert Mismatch In Poly Test Info: Deleted 1 object(s) Run test: intersect(separate_mode="CUT") on Cubecube selecting F 0 1 2 3 4 5 Fail Loop Vert Mismatch In Poly Test Info: Deleted 1 object(s) Run test: intersect(separate_mode="ALL") on Cubecube selecting F 0 1 2 3 4 5 Fail Edge Mismatch Info: Deleted 1 object(s) Run test: intersect(separate_mode="NONE") on Cubecube selecting F 0 1 2 3 4 5 Fail Loop Vert Mismatch In Poly Test Info: Deleted 1 object(s) Run test: intersect(mode="SELECT" separate_mode="NONE") on Cubecube selecting F 0 1 2 3 4 5 6 7 8 9 10 11 Fail Loop Vert Mismatch In Poly Test Info: Deleted 1 object(s) Run test: intersect_boolean(operation="UNION") on Cubecone selecting F 6 7 8 9 10 Fail Loop Vert Mismatch In Poly Test Info: Deleted 1 object(s) Run test: intersect_boolean(operation="UNION") on Cubecones selecting F 0 1 2 3 4 5 Fail Loop Vert Mismatch In Poly Test Info: Deleted 1 object(s) Ran 9 tests, 8 failed Tests Failed ``` **Exact steps for others to reproduce the error** run the bmesh_boolean test or load bool_regression.blend manually and click run script.
Author
Member

Added subscriber: @LazyDodo

Added subscriber: @LazyDodo

#56543 was marked as duplicate of this issue

#56543 was marked as duplicate of this issue
Campbell Barton was assigned by Ray molenkamp 2019-05-27 18:14:19 +02:00
Author
Member

Added subscriber: @ideasman42

Added subscriber: @ideasman42
Author
Member

@ideasman42 mind taking a peek here?

@ideasman42 mind taking a peek here?

Added subscriber: @brecht

Added subscriber: @brecht

I don't think a memory leak on x86 is high priority as in must be fixed for the 2.80 release. Still good to fix to make the tests run well.

I don't think a memory leak on x86 is high priority as in must be fixed for the 2.80 release. Still good to fix to make the tests run well.
Author
Member

The actual tests are failing, the memleak is probably just a symptom.

The actual tests are failing, the memleak is probably just a symptom.
Author
Member

I looked a little further into this, the tests are failing because the geometry generated is actually different between x86 and x64 (errors out during CD_MPOLY compare in customdata_compare) the result doesn't look wrong, up to you if you want to keep it at medium.

Given you thought it was just a 3kb mem leak, the medium prio seems rather generous.

I looked a little further into this, the tests are failing because the geometry generated is actually different between x86 and x64 (errors out during CD_MPOLY compare in `customdata_compare`) the result doesn't look wrong, up to you if you want to keep it at medium. Given you thought it was just a 3kb mem leak, the medium prio seems rather generous.

It's medium priority in the sense that it would be good to have all our tests passing, though the actual bug is not that important probably.

It might be an issue with extended precision for floats on 32 bits or something like that, which wouldn't really make it a bug.

I want to drop 32 bit support right after the 2.80 release though, so fixing this a harmless issue for a test is not that important.

It's medium priority in the sense that it would be good to have all our tests passing, though the actual bug is not that important probably. It might be an issue with extended precision for floats on 32 bits or something like that, which wouldn't really make it a bug. I want to drop 32 bit support right after the 2.80 release though, so fixing this a harmless issue for a test is not that important.
Campbell Barton was unassigned by Dalai Felinto 2019-12-23 16:34:17 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Brecht Van Lommel self-assigned this 2020-01-27 11:50:31 +01:00

We dropped 32 bit support, so not going to spend time on this anymore.

We dropped 32 bit support, so not going to spend time on this anymore.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#65143
No description provided.