server 503 blender open data full benchmark #57191
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#57191
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-error-report.txt
benchmark-result.txt
System Information
Linux debian 9 64bit - ryzen 1500X - MSI GeForce GT1030 AERO ITX 2G OC
Blender Version
Broken: blender-benchmark-1.0b2-linux-glibc219-x86_64 (download file name)
Worked: blender 2.79 expected to work normal
Short description of error
503 server error after trying to publish benchmark data, this was the first time running the benchmark. My browser opened localhost:1414 with blank screen. opening this tab again gave a success! client associated window. Nothing changed when I tried to submit the quick benchmark.
Exact steps for others to reproduce the error
open blender benchmark 1.0b2; run full/quick benchmark; publish;
Added subscriber: @Fl_GUI
Added subscriber: @RomanGischig
same for the Windows64-bit version:
error:
C:\Users\blaaa\Downloads\blender-benchmark-1.0b2-windows64>blender-benchmark.exe
Color management: using fallback mode for management
Color management: scene view "Filmic" not found, setting default "Default".
found bundled python: C:\Users\blaaa\Downloads\blender-benchmark-1.0b2-windows64\2.80\python
127.0.0.1 - - [17/Oct/2018 21:23:55] "GET /?token=<>HTTP/1.1" 200 -
Error 503 submitting benchmark: Bad status code received
Response JSON: {'message': 'Service temporarily unavailable, try again later.'}
Added subscriber: @dr.sybren
This should be resolved now, can you try again?
Hi,
Unfortunately my system changed since this bug report, I switched back from linux to windows 10.
I just ran the quick CPU benchmark and publishing resulted in the same error. BUT when I refreshed the browser tab I was met with some nice bar graphs and the shocking realisation that my render times are twice the average.
Thank you very much for your effort.
Changed status from 'Open' to: 'Archived'
Changed status from 'Archived' to: 'Resolved'
Thanks for updating us; marking as solved.