-
Notifications
You must be signed in to change notification settings - Fork 0
Test Report 28‐03‐2024
piotr-iohk edited this page Apr 10, 2024
·
12 revisions
date | Mina daemon | uptime-service-backend | uptime-service-validation | stateless-verification-tool / submission-updater | E2E Test Result | Notes |
---|---|---|---|---|---|---|
2024-04-10 | 2.0.0berkeley_rc1 | 2.0.0rc7 | 2.0.0rc3 | 2.0.0rc2 | PASSED | validations run with full check |
2024-03-28 | 2.0.0berkeley_rc1 | 2.0.0rc7 | 2.0.0rc2 | 2.0.0rc1 | PASSED | validations run with full check |
Test passed after fixing scores in https://github.com/MinaFoundation/uptime-service-validation/pull/46.
- users: 100, behaviour: submit request between 1-5 seconds
- duration: 1h
- submissions total: 9451
- submissions validated: 9451
We had 35 error responses in last minutes of the test:
- 9:
EOF occurred in violation of protocol (_ssl.c:2426)
- 26:
Remote end closed connection without response
They seem to be somewhat correlated with log entries:
{"level":"debug","ts":"2024-03-28T09:04:31.900Z","logger":"delegation backend","caller":"delegation_backend/submit.go:144","msg":"Error while reading /submit request's body: unexpected EOF"}
{"level":"debug","ts":"2024-03-28T09:04:31.900Z","logger":"delegation backend","caller":"delegation_backend/submit.go:25","msg":"Responding with error: Error reading the body"}
Investigating shows that this was not likely an issue with proxy. Could be also that locust sent something unexpected. Atm, this observation is inconclusive. It was also only 35 responses out of 36k requests so failure rate is close to 0%.