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

ci: enable pindexer integration tests #5057

Merged
merged 1 commit into from
Feb 5, 2025
Merged

Conversation

conorsch
Copy link
Contributor

@conorsch conorsch commented Feb 5, 2025

Describe your changes

Follow-up to #5009, in which these tests were introduced, and #5048, which refactored the smoke tests to make additions like this easier.

Issue ticket number and link

See above.

Testing and review

The tests were already merged, this is just enabling them in CI, so CI passing, specifically on the smoke-test job, is enough.

Checklist before requesting a review

  • I have added guiding text to explain how a reviewer should test these changes.

  • If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

    tests/ci only, no changes to application code

Follow-up to #5009, in which these tests were introduced, and #5048,
which refactored the smoke tests to make additions like this easier.
@conorsch conorsch requested a review from cronokirby February 5, 2025 19:23
@conorsch conorsch merged commit 7869803 into main Feb 5, 2025
10 checks passed
@conorsch conorsch deleted the ci-pindexer-integration-tests branch February 5, 2025 19:46
conorsch added a commit that referenced this pull request Feb 19, 2025
## Describe your changes

Moving the smoke test invocations out of the process-compose wrapper,
preferring running raw `cargo test` invocations instead. Doing so
ensures that the test output is readable, both locally, and crucially in
CI.

### Screenshot before

![smoke-test-before](https://github.com/user-attachments/assets/219b8518-8525-463e-8465-2c16f787d3f6)

### Screenshot after

![smoke-logs-after](https://github.com/user-attachments/assets/b7721d89-c969-4870-8d33-b9aa8dbc6ac9)


## Issue ticket number and link

No guiding issue, just trying to improve the testing setup
opportunistically. We did have inscrutable smoke test failures on #5063
& #5081, both of which were failures of the new pindexer integration
tests (#5057), but it was hard to see the specific failure at a glance,
which slowed down development.

## Testing and review

Check the CI logs for the smoke test job. Are they readable? Consider
running `just smoke` locally and confirm the same.

## Checklist before requesting a review

- [x] I have added guiding text to explain how a reviewer should test
these changes.

- [x] If this code contains consensus-breaking changes, I have added the
"consensus-breaking" label. Otherwise, I declare my belief that there
are not consensus-breaking changes, for the following reason:

  > tests-only, no code changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants