hardfork_support_test eats failures in removeClaim #233

New issue

Closed

opened 2018-11-02 18:57:10 +01:00 by BrannonKing · 1 comment

BrannonKing commented

2018-11-02 18:57:10 +01:00

(Migrated from github.com)

Adding asserts to CClaimTrieCache::removeFromExpirationQueue to ensure that all removals happen shows that the unit test hardfork_support_test has four failures. I didn't see any failures in any other tests.

Adding asserts to `CClaimTrieCache::removeFromExpirationQueue` to ensure that all removals happen shows that the unit test `hardfork_support_test` has four failures. I didn't see any failures in any other tests.

BrannonKing commented

2019-12-16 19:58:17 +01:00

(Migrated from github.com)

This scenario is now logged. I'm going to call that good enough.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbrycrd#233

No description provided.