Failing `modifiers` test on the buildbot for OSX intel builds in `sanitizer` or `debug` mode #116956

New Issue

Open

opened 2024-01-09 19:42:22 +01:00 by Bastien Montagne · 18 comments

Bastien Montagne commented

2024-01-09 19:42:22 +01:00

Owner

System Information
Operating system: OSX (arm64)
Graphics card: N/A

Blender Version
Broken: Current main
Worked: ???

Short description of error

In sanitizer and debug builds the OSX arm64 buildbot always fails on modifiers test:

START CurveTriangulate test.
FAILED CurveTriangulate test with the following: 
Results:
Mesh Comparison : The edge topology is different
Mesh Validation : Valid

Release builds are never showing this issue, nor OSX x86_64 or linux ones.

Exact steps for others to reproduce the error

The error is consistently reproducible on the buildbot (one need to have admin access to it to trigger debug builds though currently).

See e.g. https://builder.blender.org/admin/#/builders/60/builds/1867

**System Information** Operating system: OSX (arm64) Graphics card: N/A **Blender Version** Broken: Current main Worked: ??? **Short description of error** In `sanitizer` and `debug` builds the OSX arm64 buildbot always fails on modifiers test: ``` START CurveTriangulate test. FAILED CurveTriangulate test with the following: Results: Mesh Comparison : The edge topology is different Mesh Validation : Valid ``` Release builds are never showing this issue, nor OSX x86_64 or linux ones. **Exact steps for others to reproduce the error** The error is consistently reproducible on the buildbot (one need to have admin access to it to trigger `debug` builds though currently). See e.g. https://builder.blender.org/admin/#/builders/60/builds/1867

Bastien Montagne added the

labels 2024-01-09 19:42:22 +01:00

Bastien Montagne added the

Platforms, Builds & Tests

labels 2024-01-10 10:23:36 +01:00

Bastien Montagne commented

2024-01-10 10:24:54 +01:00

Author

Owner

Note: Don't have an arm64 Mac at hands right now to test and confirm on a 'normal' workstation, so not confirming the issue for now.

Note: Don't have an arm64 Mac at hands right now to test and confirm on a 'normal' workstation, so not confirming the issue for now.

Pratik Borhade commented

2024-03-05 11:43:28 +01:00

Member

@mont29 hi, modifiers test still failing on debug build? Can you ask someone from studio to check this? Sergey maybe 🙂

@mont29 hi, modifiers test still failing on debug build? Can you ask someone from studio to check this? Sergey maybe 🙂

Bastien Montagne commented

2024-03-05 15:10:50 +01:00

Author

Owner

Yes they do, see https://builder.blender.org/admin/#/builders/60/builds/1889

Not sure who is actual member of MacOS module and would have time to check on this though...

Yes they do, see https://builder.blender.org/admin/#/builders/60/builds/1889 Not sure who is actual member of MacOS module and would have time to check on this though...

Pratik Borhade commented

2024-03-06 04:55:58 +01:00

Member

Thanks.

Module member macOS:

@farsthary @brecht , can you check?

Thanks. > [Module member macOS:](https://projects.blender.org/blender/blender/wiki/Module:%20Platforms,%20Builds,%20Tests%20&%20Devices#:~:text=macOS,Farsthary%20%40brecht) @farsthary @brecht , can you check?

Raul Fernandez Hernandez commented

2024-03-06 15:43:52 +01:00

Member

Note: Don't have an arm64 Mac at hands right now to test and confirm on a 'normal' workstation, so not confirming the issue for now.

I have both x86 and an M1, in order to reproduce it locally will suffice to run "make test"?

> Note: Don't have an arm64 Mac at hands right now to test and confirm on a 'normal' workstation, so not confirming the issue for now. I have both x86 and an M1, in order to reproduce it locally will suffice to run "make test"?

Bastien Montagne commented

2024-03-06 15:54:26 +01:00

Author

Owner

@farsthary yes, assuming you are using a debug build with ASAN enabled.

I would rather recommend running ctest directly from the build directory though, since you can then filter out tests and add more options.

E.g. ctest --output-on-errors -R "modifiers" will only run modifiers tests and give you all the console prints when failing.

@farsthary yes, assuming you are using a debug build with ASAN enabled. I would rather recommend running `ctest` directly from the build directory though, since you can then filter out tests and add more options. E.g. `ctest --output-on-errors -R "modifiers"` will only run `modifiers` tests and give you all the console prints when failing.

Raul Fernandez Hernandez commented

2024-03-06 16:14:36 +01:00

Member

thanks! will report back shortly

thanks! will report back shortly

Raul Fernandez Hernandez commented

2024-03-06 17:32:41 +01:00

Member

Tested on an M1 MBA on release-4.1 , the test that failed where unrelated to modifiers:

99% tests passed, 1 tests failed out of 334
Total Test time (real) = 500.31 sec

The following tests FAILED:
49 - io_wavefront (Subprocess aborted)
Errors while running CTest
make: *** [test] Error 8
➜ blender git:(blender-v4.1-release)

and on main

99% tests passed, 2 tests failed out of 336

Total Test time (real) = 492.51 sec

The following tests FAILED:
50 - io_wavefront (Subprocess aborted)
52 - io_stl (Subprocess aborted)
Errors while running CTest

Tested on an M1 MBA on release-4.1 , the test that failed where unrelated to modifiers: 99% tests passed, 1 tests failed out of 334 Total Test time (real) = 500.31 sec The following tests FAILED: 49 - io_wavefront (Subprocess aborted) Errors while running CTest make: *** [test] Error 8 ➜ blender git:(blender-v4.1-release) and on main 99% tests passed, 2 tests failed out of 336 Total Test time (real) = 492.51 sec The following tests FAILED: 50 - io_wavefront (Subprocess aborted) 52 - io_stl (Subprocess aborted) Errors while running CTest

Raul Fernandez Hernandez commented

2024-03-06 17:33:22 +01:00

Member

will report on my x86 next

will report on my x86 next

Anthony Roberts commented

2024-03-06 17:43:20 +01:00

Member

Do you have a list of which tests in particular are failing from io_wavefront and io_stl? If you run the tests via ctest --output-on-errors -R "io_wavefront", you can find the log file in Testing/Temporary/LastTest.log

I am seeing failures on Windows ARM64 devices in the same tests, and am wondering if it's the same place

Do you have a list of which tests in particular are failing from `io_wavefront` and `io_stl`? If you run the tests via `ctest --output-on-errors -R "io_wavefront"`, you can find the log file in `Testing/Temporary/LastTest.log` I am seeing failures on Windows ARM64 devices in the same tests, and am wondering if it's the same place

Brecht Van Lommel referenced this issue from a commit

2024-03-06 17:58:02 +01:00

Fix #116956: Bake multires crash with simplify subdivision

Brecht Van Lommel closed this issue

2024-03-06 18:03:59 +01:00

Blender Bot added

and removed

labels 2024-03-06 18:04:01 +01:00

Brecht Van Lommel commented

2024-03-06 18:04:27 +01:00

Owner

Sorry, I mentioned the wrong issue number in my commit.

Sorry, I mentioned the wrong issue number in my commit.

Brecht Van Lommel reopened this issue

2024-03-06 18:04:31 +01:00

Blender Bot added

and removed

labels 2024-03-06 18:04:34 +01:00

Raul Fernandez Hernandez commented

2024-03-06 18:42:16 +01:00

Member

Do you have a list of which tests in particular are failing from io_wavefront and io_stl? If you run the tests via ctest --output-on-errors -R "io_wavefront", you can find the log file in Testing/Temporary/LastTest.log

I am seeing failures on Windows ARM64 devices in the same tests, and am wondering if it's the same place

When I run that command I get this:

~/blender-git/blender (blender-v4.1-release) » ctest --output-on-errors -R "io_wavefront"
vane@Vanessas-iMac-Pro
Test project /Users/vane/blender-git/blender
No tests were found!!!

> Do you have a list of which tests in particular are failing from `io_wavefront` and `io_stl`? If you run the tests via `ctest --output-on-errors -R "io_wavefront"`, you can find the log file in `Testing/Temporary/LastTest.log` > > I am seeing failures on Windows ARM64 devices in the same tests, and am wondering if it's the same place When I run that command I get this: > ~/blender-git/blender (blender-v4.1-release) » ctest --output-on-errors -R "io_wavefront" > vane@Vanessas-iMac-Pro > Test project /Users/vane/blender-git/blender > No tests were found!!!

Raul Fernandez Hernandez commented

2024-03-06 18:43:33 +01:00

Member

and on the x86 Mac I get new tests errors:

99% tests passed, 2 tests failed out of 334

Total Test time (real) = 896.65 sec

The following tests FAILED:
49 - io_wavefront (Subprocess aborted)
313 - geo_node_mesh/boolean_boolean_diff (Failed)
Errors while running CTest
make: *** [test] Error 8

And none regarding modifiers

and on the x86 Mac I get new tests errors: 99% tests passed, 2 tests failed out of 334 > Total Test time (real) = 896.65 sec > > The following tests FAILED: > 49 - io_wavefront (Subprocess aborted) > 313 - geo_node_mesh/boolean_boolean_diff (Failed) > Errors while running CTest > make: *** [test] Error 8 And none regarding modifiers

Anthony Roberts commented

2024-03-06 18:47:21 +01:00

Member

@farsthary You need to run it inside your build folder (ie, the one containing CMakeCache.txt)

@farsthary You need to run it inside your build folder (ie, the one containing CMakeCache.txt)

Raul Fernandez Hernandez commented

2024-03-06 23:15:05 +01:00

Member

Do you have a list of which tests in particular are failing from io_wavefront and io_stl? If you run the tests via ctest --output-on-errors -R "io_wavefront", you can find the log file in Testing/Temporary/LastTest.log

I am seeing failures on Windows ARM64 devices in the same tests, and am wondering if it's the same place

For io_wavefront I get this fail result:

> Do you have a list of which tests in particular are failing from `io_wavefront` and `io_stl`? If you run the tests via `ctest --output-on-errors -R "io_wavefront"`, you can find the log file in `Testing/Temporary/LastTest.log` > > I am seeing failures on Windows ARM64 devices in the same tests, and am wondering if it's the same place For io_wavefront I get this fail result:

LastTest.log

4.4 KiB

Raul Fernandez Hernandez commented

2024-03-06 23:22:17 +01:00

Member

And for the "modifier" tests on a MBA M1 I get this log:

And for the "modifier" tests on a MBA M1 I get this log:

LastTest.log

24 KiB

Anthony Roberts commented

2024-03-07 15:24:52 +01:00

Member

Sadly not the same failure as mine, I guess my hunt continues 😄

Sadly not the same failure as mine, I guess my hunt continues 😄

Anthony Roberts commented

2024-03-07 15:57:28 +01:00

Member

Actually scratch that, it's not the same failue for me on io_wavefront, however the exact same assert causes the failure on io_stl for me...

Actually scratch that, it's not the same failue for me on `io_wavefront`, however the exact same assert causes the failure on `io_stl` for me...

io_stl_failure.txt

15 KiB

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

5 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#116956

No description provided.