Skip to content
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

Benchmark results not available at the website #29

Closed
lucianor opened this issue Jul 27, 2023 · 4 comments
Closed

Benchmark results not available at the website #29

lucianor opened this issue Jul 27, 2023 · 4 comments
Assignees

Comments

@lucianor
Copy link

lucianor commented Jul 27, 2023

Hello. I ran the benchmark scripts on my new Orange Pi 5 board, and those results got published in the site without a problem: https://pibenchmarks.com/user/lucianor/

However, I ran the benchmark script a couple of minutes after on my Raspberry Pi 4b (which is being replaced by the new board) but no results have been posted on the site: can't find them in 'Latest' or in my username page - I also tried anonymous posting.

  1. Is there a rate limit of how many results one can post in a day?
  2. Is there a delay for the website to update? I found the OPI5 result after a couple of minutes
  3. Is there a filter on more popular boards results which could justify RPI4b results not being published?

Thank you

@terrorpup
Copy link

I have a similar issue with the Radxa Rock 5A and Indiedroid-Nova, and I am trying to get eMMC for the Orange Pi to show up.

@rmkilc
Copy link

rmkilc commented Nov 7, 2023

When I run it on my Orange Pi 5 Plus with a Samsung 970 EVO Plus NVMe M.2 SSD running Armbian, the results do not show up on the website. I do not get the "Result submitted successfully" line. The only thing that stands out to me is this part but I'm not sure if it's related:

Running additional hardware identification tests...
bash: line 398: warning: command substitution: ignored null byte in input

@rglidden
Copy link

rglidden commented Nov 14, 2023

@rmkilc 's error appears to be caused by a bug in the nvme command an recent kernel changes in newer Linux versions. See my #31 (comment) for a temporary work around.

Not sure if it also applies to the other reports above.

@TheRemote
Copy link
Owner

This should now be fixed in the latest version!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants