-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue 174 #175
Merged
Merged
Issue 174 #175
Changes from 2 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
e038c89
replicate error in pytest
floesche 259be83
potential fix for #174
floesche 94ec009
Issue 174 ci (#1)
floesche b006dc3
restart CI
floesche 09c7a15
reset to original
floesche 50c552a
move blender
floesche eb96d7e
create symlink
floesche 05a5d6e
modify env
floesche 3b25166
Merge branch 'issue_174' into issue_174_ci2
floesche 196a3cd
Merge pull request #2 from floesche/issue_174_ci2
floesche File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's a good idea to provide some example here. Currently, this will cause an error during doctests because Blender is not installed on the Github worker.
You can either edit
test-package.yml
to install Blender before running pytest, or add the# doctest: +SKIP
directive to exclude this line from the tests (see other such examples throughout the codebase). In theory, the former should be pretty straight forward:wget
the linux distribution, unzip somewhere and add toPATH
. In practice, Github Actions can be a pain in the neck to debug.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, that's a great idea.
I had issue with the current installation with some mesa related libraries and removed
graphviz-dev
andmesa-vulkan-drivers
from mytest-package.yml
. I also added the latest blender-LTS viamoguri/setup-blender@v1
action.I did not see the tests finish, but in at least one of the runs I saw the test from b3d pass. Let me know if this could work for you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the solution to keeping the ubuntu libraries as they were before and installing the blender directly via wget, not relying on an external and potentially unnecessary complex action. The
simplify_mesh_blender
seems to pass more reliably now, the comparison between basic types and numpy types still fails, so the overall tests currently still fail.Let me know if I should change anything else?