PopulateLogTile error in MySQL storage tests
Here's a snippet from the output of go test -v ./storage/mysql:
=== RUN TestNodeRoundTrip/store-all-read-all-norevisions
E1028 16:50:59.282101 144538 subtree_cache.go:122] PopulateLogTile(): log repop got: 254 internal nodes, want: 0
=== RUN TestNodeRoundTrip/store-all-read-all-revisions
E1028 16:50:59.299517 144538 subtree_cache.go:122] PopulateLogTile(): log repop got: 254 internal nodes, want: 0
By trial and error I've found that these PopulateLogTile errors started occurring after this commit. However, that commit's description seems to suggest that it may have only surfaced the issue rather than created it.
Hi @patflynn, I’m interested in working on this issue. Could you please let me know if there are any specific guidelines or pointers to keep in mind? Thank you!
Hi @rahulmansharamani14 ! I'm really happy to see external interest, and we welcome contributions. Be aware that we're working quite hard on Tessera ATM, so depending on the size of PR and the review challenge you may see some delays.
@AlCutter may have some pointers
Zde je úryvek z výstupu
go test -v ./storage/mysql:=== RUN TestNodeRoundTrip/store-all-read-all-norevisions E1028 16:50:59.282101 144538 subtree_cache.go:122] PopulateLogTile(): log repop got: 254 internal nodes, want: 0 === RUN TestNodeRoundTrip/store-all-read-all-revisions E1028 16:50:59.299517 144538 subtree_cache.go:122] PopulateLogTile(): log repop got: 254 internal nodes, want: 0Metodou pokus-omyl jsem zjistil, že se tyto
PopulateLogTilechyby začaly vyskytovat po tomto commitu . Popis commitu však naznačuje, že problém mohl pouze odhalit, nikoli ho vytvořit.