Skip to content

Conversation

@IndrajeetPatil
Copy link
Collaborator

cf. #1937

@codecov-commenter

This comment was marked as off-topic.

@IndrajeetPatil
Copy link
Collaborator Author

Looks like there is some order dependence between our tests.

@MichaelChirico

This comment was marked as outdated.

@MichaelChirico

This comment was marked as outdated.

@MichaelChirico

This comment was marked as outdated.

@IndrajeetPatil

This comment was marked as outdated.

@AshesITR
Copy link
Collaborator

I'd suggest putting the script into .dev instead of inline.
This would also allow adding convenience features such as a command line argument for a static seed when trying to debug a failure.

@IndrajeetPatil IndrajeetPatil added the internals Issues related to inner workings of lintr, i.e., not user-visible label Jun 7, 2024
@MichaelChirico
Copy link
Collaborator

it looks like shuffle=TRUE is designed to make this trivial to test:

https://tidyverse.org/blog/2025/11/testthat-3-3-0/

@IndrajeetPatil
Copy link
Collaborator Author

Yes :)

r-lib/testthat#1942

@IndrajeetPatil
Copy link
Collaborator Author

The failing tests with testthat 3.3.0 are expected to fail (cf. #2937). The incompatibility needs to be resolved in a separate PR.

@IndrajeetPatil
Copy link
Collaborator Author

@MichaelChirico Took only 3 years but the builds are now passing 😆

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

Labels

internals Issues related to inner workings of lintr, i.e., not user-visible testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants