benchmark-launcher-cli-3.1.0-linux getting 404 when Choose a Blender version: 4.1.0 #101872
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-open-data#101872
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-launcher-cli-3.1.0-linux ( Same error with GUI/Linux )
Ubuntu 23.10 x86_64
Intel i5-12400F
Intel Arc A750 + Intel GPU Ubuntu Repo drivers ( updated as of today / Mar 28 2023 and GPU shows up in Blender 4.1 )
64GB of ram
benchmark-launcher-cli-3.1.0-linux getting 404 when Choose a Blender version: 4.1.0
$ ./benchmark-launcher-cli --verbosity 3
2024/03/29 00:21:20 metadata.go:14: Fetching Metadata: https://opendata.blender.org/benchmarks/metadata/
2024/03/29 00:21:21 metadata.go:49: Successfully fetched metadata
2024/03/29 00:21:21 metadata.go:71: Getting current launcher.
2024/03/29 00:21:21 checksum.go:16: Calculating checksum of current launcher.
2024/03/29 00:21:21 checksum.go:35: Launcher checksum: d2504fddc513b6b1ccbf18cb75aa381d21a543fe4662d790f24aa7275fa255e9.
? Choose a Blender version: 4.1.0
I see this as well. Looking at what's happening here, I see the following requests being made (along with the response codes - sniffed using HTTP Toolkit):
Looking at the URL in request #3, I see that the file is missing from that mirror.
There doesn't appear to be any way to specifically select a mirror or pre-download the package and put it somewhere so the benchmark program can just use it.
In my case, I have 4.1.0 installed through Steam, but it's not detected by the benchmark program, either, even if I put the executable's path in the system's path.
I see nothing of use in the log either:
I tried creating the directory noted here and putting the tar.xz file in that directory, and the script just deleted the directory and its contents. Same with unpacking Blender 4.1.0 to that directory (which, looking at what happens when I select 4.0.0, is what should work).
The GUI tool just exits with an error, but it seems the issue is that the mirror that's automatically selected doesn't have the file, and there's no way to override it, and no fallback if the file isn't found to a different mirror.
ETA: I was able to work around this by doing the following (I'm on Linux, so if you're not, you may need to adjust this to fit your filesystem structure):
d2ac5390f4a9cb9416c8eb23bdd8fa8e49e68165a889575fd8f56563f5cccaf1
in/home/USERNAME/.cache/blender-benchmark-launcher/blender-versions/
(the filename comes from the log file)valid.launcher
in that directory. (I usedtouch
)Then run
benchmark-launcher-cli
and it'll detect the Blender 4.1.0 installation is present.