We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The problem was found using stress tool during long test run (12 such failures in 2 hours / 164000+ test runs). It's thus rather unlikely to happen.
stress
--- FAIL: Test_GetAtxsLimiting (0.64s) --- FAIL: Test_GetAtxsLimiting/with_limiting:_true (0.56s) logger.go:146: 2025-01-04T00:29:03.456+0400 INFO initialized datastore {"config": {"ATXSize":1000,"MalfeasanceSize":1000}} mesh_data_test.go:991: Error Trace: /Users/ivan4th/work/spacemesh/go-spacemesh/fetch/mesh_data_test.go:991 /Users/ivan4th/work/spacemesh/go-spacemesh/p2p/server/server.go:545 /Users/ivan4th/work/spacemesh/go-spacemesh/p2p/server/server.go:335 /Users/ivan4th/work/spacemesh/go-spacemesh/p2p/server/server.go:279 /Users/ivan4th/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:78 /opt/homebrew/Cellar/go/1.23.4/libexec/src/runtime/asm_arm64.s:1223 Error: "[{ATXDB [84 201 32 12 213 43 49 17 44 74 196 68 49 2 55 212 254 125 231 88 242 134 116 146 60 157 63 229 253 78 107 197]} {ATXDB [244 245 57 20 93 108 148 119 85 30 42 113 5 180 38 252 158 86 150 18 94 160 36 63 1 127 89 212 219 5 16 4]} {ATXDB [27 49 71 153 242 234 113 132 52 50 168 59 155 123 128 92 2 19 104 184 100 77 0 242 52 225 76 8 14 219 38 5]}]" should have 10 item(s), but has 3
This issue appears in commit hash: cdee34f
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
The problem was found using
stress
tool during long test run (12 such failures in 2 hours / 164000+ test runs).It's thus rather unlikely to happen.
Affected code
This issue appears in commit hash: cdee34f
The text was updated successfully, but these errors were encountered: