Hi Patrick, hi list,
After you're logged in with Gerrit, you can get git-compatible
credentials at https://review.coreboot.org/settings/#HTTPCredentials
that you can then store in $HOME/.netrc for git to pick up.
Thanks for the hint. I have no experience with gerrit, so this wasn't
self-explanatory to me.
With the http credentials, I was able to submit my results. At least I
think so, because I had to enter the credentials and didn't see any
error message when I tried it yesterday. But
https://coreboot.org/status/board-status.html still shows a date from
january for the alix2d platform.
Repeating the process today because I thought I did something wrong
results in "Result is a duplicate, aborting", which makes me think
yesterday's commit was successful:
$ util/board_status/board_status.sh -r 192.168.100.22 -u
Extracting config.txt from build/coreboot.rom
Extracting payload_config from build/coreboot.rom
Temporarily placing output in
Verifying that CBMEM is available on remote device
Getting coreboot boot log
Getting timestamp data
Failed to run "cbmem -t", ignoring
Getting remote dmesg
Cloning into 'board-status'...
remote: Counting objects: 65707, done
remote: Finding sources: 100% (28/28)
remote: Total 105407 (delta 3), reused 105404 (delta 3)
Receiving objects: 100% (105407/105407), 214.71 MiB | 652.00 KiB/s, done.
Resolving deltas: 100% (27205/27205), done.
Checking out files: 100% (70725/70725), done.
Checking for duplicate results
Result is a duplicate, aborting
One more thing: My board is an Alix 2C, which is pretty similar to the
Alix 2D. It is reported as "alix2d", so the table at
https://coreboot.org/status/board-status.html will always show "unknown"
as status for the alix2c, which might be confusing.
Thanks and best regards,
coreboot mailing list: ***@coreboot.org