CTest 'script_load_addons' fails #39450
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#39450
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Using CMake, run this from the build dir.
script_load_addons_fail.txt
Attached the log.
There are some addons which need to propery register and unregister by the looks of it.
If its not obvious how to fix you could contact the addon authors, otherwise its probably fine to apply changes directly.
Changed status to: 'Open'
Added subscriber: @ideasman42
Added subscriber: @mont29
Those are mostly contrib addons, in fact…
This issue was referenced by blender/blender-addons-contrib@2bcc13357b
Changed status from 'Open' to: 'Resolved'
Closed by commit blender/blender-addons-contrib@2bcc13357b.
Note there are still a few odd failure reports when running this test, though they do not make it fail. I could not get rid of them... :/