Set explicit limit for getPosts/getComments in tests #4250
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Looking at CI test failures, I noticed there were a couple cases where the expected value wasnt found in return value from
getPosts()
:https://woodpecker.join-lemmy.org/repos/129/pipeline/4262/20
https://woodpecker.join-lemmy.org/repos/129/pipeline/4276/20
This seems to happen because it uses the default limit which is 10, but there are more posts than that and the expected value is not returned. So setting an explicit, high limit should resolve this.