| @@ -1,5 +1,7 @@ | |||
| 1 | 1 | # SoloKey 2 (stock firmware from 2022) | |
| 2 | 2 | ||
| 3 | + | Basically cannot handle more than 1-2 workers at the same time. | |
| 4 | + | ||
| 3 | 5 | ```bash | |
| 4 | 6 | $ go run -buildvcs=false ./cmd/ctap-stress \ | |
| 5 | 7 | -device 1 -workers 4 -duration 30s -ops ping \ | |
| @@ -69,7 +71,7 @@ Failure samples: | |||
| 69 | 71 | exit status 1 | |
| 70 | 72 | ``` | |
| 71 | 73 | ||
| 72 | - | # Solokey 2 (2.2363.0) | |
| 74 | + | # SoloKey 2 (2.2363.0) | |
| 73 | 75 | ||
| 74 | 76 | Classic test with random ping sizes but with the limit of max message to 1200 (YubiKey's default). | |
| 75 | 77 | Those Error(0) were actually supposed to be CHANNEL_BUSY; stress util would retry them in this case. | |
savely / solokey_tests.md
Last active 3 weeks ago
Diff is too large to be shown