benchmark-launcher-cli fails to submit results #98358
Labels
No Label
legacy module
Rendering & Cycles
legacy project
1.0.0-beta.2
legacy project
Blender Benchmark
legacy project
Cycles
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
No Milestone
No project
No Assignees
5 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/blender-benchmark-bundle#98358
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?
System Information
Operating system: RHEL 8.4
Graphics card: NVIDIA A100
Blender Version
Broken: benchmark-launcher-cli 3.0.0
Short description of error
After successfully running the benchmark-launcher-cli script the final step of submitting the result fails with a bad handshake. This does not appear to be due to not being able to connect to the data server.
Exact steps for others to reproduce the error
Checking the server connection can be made (i.e. not a firewall issue):
Does the token file error message have anything to do with this?
Added subscriber: @PaulMelis
Added subscriber: @iss
Changed status from 'Needs Triage' to: 'Needs User Info'
@PaulMelis is this still an issue? I wasn't able to reproduce error
Yes, I just tried it again and got the same handshake error. Note that I'm running the benchmark on a GPU node of a supercomputer, but I've never had issues with outgoing network connections there. The weird thing is that apparently the connection to the submit server can easily be made, but something goes wrong after that. I'm not sure where the "bad handshake" error comes from, if that is caused by the websocket connection upgrade failing (HTTPS -> WSS), or if is related to the missing token (which might be part of the submission handshake?).
Can you check if there are any rules for outgoing connections? Not sure what port is in question here though or if this could be debugged somehow. I would have to check sources, to see if it is possible to have some exchange perhaps with python script to see if connection was made at least or not.
Added subscriber: @fsiddi
Looping in Anna, as this might be related to changes recently done on the infrastructure.
This issue was referenced by infrastructure/blender-open-data@0ae0bca34d
Changed status from 'Needs User Info' to: 'Resolved'
This was correct: upgrade was broken since May 24th by the above mentioned changes to the infra, my bad.
benchmark-launcher-cli
should be working again now.