Blender Benchmark crashes on Linux Debian (stable, Buster) #76571
Labels
No Label
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Information from Developers
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
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: infrastructure/blender-open-data#76571
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Benchmark runs through, but crashes at the end.
Blender Benchmark Error ID: 86108f6b99bb4c9ea5a7ca1fe2ee34ef
Added subscriber: @MarkusBawidamann-4
Added subscriber: @fsiddi
Changed status from 'Needs Triage' to: 'Needs User Info'
The error returned by the server is
benchmark failed: Did not receive Benchmark JSON Data.Are you able to consistently reproduce this behavior in your system?
Yes, I can. I have run the benchmark already 5 times and it always ends the same way. I can run it again in case there has been a code update.
Can you confirm that your platform is Linux? Which distro?
I'll keep the task open, but can't look into it further for the time being.
Yes, it is Debian Linux (Version 10, Buster, Stable)
Kernel is:
4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux
It's a shame you guys have no resources to work on Blender Benchmark right now, I see so much potential for it, being a commercially independent (and OS independent too) Benchmark to compare CPUs and GPUs with a real world work load (not this fake synthetic geekbench nonsense). I'm working on creating a much larger chart (not just the top best CPUs and GPUs like your website) that shows more CPUs and GPUs compared to each other. On your site, all the normal crunching devices are not showing, while the top spots are hogged by CPUs and GPUs which most people can't afford in their dreams. I'm going to parse the open data set for that.
Hi Markus, indeed you are free to use the dataset to achieve what you like. You are also welcome to check out the code and provide an initial design that would allow to query and compare specs.
Added subscriber: @rjg
@MarkusBawidamann-4 Is this still an issue with the current Blender Benchmark version?
Changed status from 'Needs User Info' to: 'Archived'
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thanks again for the report. If the problem persists please open a new report with the required information.
No, I just did not get a chance to run this again. I'm pretty sure the issue still persists, it has everytime I have run the benchmark.
I opened this bug in May and for months, it did not even receive triage. I did not assume that it would now suddenly move faster.
I'm running the benchmark again as we speak. Please reopen.
Thanks,
Markus
Changed status from 'Archived' to: 'Needs Triage'
Changed status from 'Needs Triage' to: 'Needs User Info'
Thanks for keeping it open. I ran it again and it worked, the issue has been resolved, thanks for your efforts.
Changed status from 'Needs User Info' to: 'Resolved'