Tests: Bump pruning size value for unit test

[brbrr]

Update_known_chain_sizes is failing on master, which blocks PR merging to master.

Changes

• Increase boundary prunning size value for the Update_known_chain_sizes test

Types of changes

What types of changes does your code introduce?

• (Temporary) Fix for a unit test

Testing

Requires testing

• Yes
• No

[tkstanczak]

Add test. What would be a good test? Maybe it should fail if there was not update to this file for more than a month?

[brbrr]

From a QA standpoint, the test is fragile by design since it relies on data outside of the test controls. Thus, the behavior of the test cannot be deterministic. Having a test that checks the file updates might work if the pruning size is growing linearly, which I don't know.

Ideally, we'd fetch the expected values on every test run, but it may defeat the purpose of the test :)

Anyway, currently tests on the master are failing, which means all the PRs are blocked. Maybe we can merge it as-is, and then create a follow-up issue/PR with a long-term solution?

[LukaszRozmej]

All this are estimates on moving targets, not sure how would you test it

[tkstanczak]

@LukaszRozmej you can write a test that checks with github hidden folder to verify when the file got last time updated. And fail if it was not updated recently enough.

[tkstanczak]

Oh, this is a test file already? Sorry, I thought ir was some production code.