Skip to content

Conversation

iduartgomez
Copy link
Collaborator

Summary

Enables the ubertest to run in CI so we can identify and debug any issues.

Changes:

  • Removed #[ignore] attribute from the ubertest
  • Added dedicated CI job for running the ubertest
  • Configured UBERTEST_PEER_COUNT=6 for faster CI execution
  • Added riverctl installation step in CI

Context

The ubertest is a comprehensive integration test that verifies freenet-core can support real-world applications using River as a reference. The test was previously marked as ignored and not running in CI.

What to expect

The ubertest will now run in CI and should reveal any issues that need to be debugged. This test:

  • Sets up a multi-peer network (1 gateway + 6 peers in CI)
  • Verifies network topology formation
  • Tests River chat operations (room creation, invitations, messaging)
  • Validates state consistency across peers

Test plan

  • CI will automatically run the ubertest on this PR
  • Review CI logs to identify any failures or issues
  • Debug and fix any issues that surface

Closes #1932

🤖 Generated with Claude Code

- Remove #[ignore] attribute from ubertest
- Add dedicated ubertest CI job with riverctl installation
- Configure UBERTEST_PEER_COUNT=6 for faster CI execution
- Make ubertest run after test_all to reuse build cache
- Set ubertest to only load cache (not save) to avoid conflicts

This enables the ubertest to run in CI so we can identify and debug
any issues as requested in issue #1932.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
@iduartgomez iduartgomez force-pushed the fix/uber-test-debug-1932 branch from e187235 to 1337cda Compare October 9, 2025 09:42
@iduartgomez iduartgomez marked this pull request as draft October 9, 2025 15:59
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.

Debug issues with uber test

2 participants