Skip to content
New issue

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

test: TestAcctUpdatesLookupLatestCacheRetry Randomly fails #5566

Conversation

algonautshant
Copy link
Contributor

@algonautshant algonautshant commented Jul 13, 2023

TestAcctUpdatesLookupLatestCacheRetry randomly fails.

Draft PR: indicating the cause of the failure with xxxx marker. to fix.

repro:
go test -run TestAcctUpdatesLookupLatestCacheRetry -count=20

    acctupdates_test.go:2470:
        	Error Trace:	/Users/shantkarakashian/go/src/github.com/algorand/3/go-algorand/ledger/acctupdates_test.go:2470
        	Error:      	Received unexpected error:
        	            	database round 0 is behind in-memory round 2
        	Test:       	TestAcctUpdatesLookupLatestCacheRetry

@codecov
Copy link

codecov bot commented Jul 13, 2023

Codecov Report

Merging #5566 (a7b2eac) into master (aeef625) will decrease coverage by 0.88%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #5566      +/-   ##
==========================================
- Coverage   55.80%   54.93%   -0.88%     
==========================================
  Files         446      446              
  Lines       63417    63417              
==========================================
- Hits        35389    34836     -553     
- Misses      25663    26182     +519     
- Partials     2365     2399      +34     
Impacted Files Coverage Δ
ledger/acctupdates.go 70.68% <0.00%> (-0.12%) ⬇️

... and 56 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants