Flaky RPC test

Open
#1,954 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
testing-qa

Research direction

Start with the integration::dotenv::can_read_file test and cmd/crates/soroban-test/tests/it/integration/util.rs at line 98. Run the RPC integration test to reproduce the intermittent failure and inspect the reported fee or resource limit behavior. Done means the test passes reliably without the fee limit failure.

Written by the indexing model from the issue text.

Description

bug
What version are you using?

22.5.0

What did you do?

When running RPC test one of the tests is flaky:


---- integration::dotenv::can_read_file stdout ----
ℹ️ Simulating install transaction…
ℹ️ Signing transaction: 5c434a675b26e283e64edd3b7b96b83dc4d4a099a21587ea580442dd9a85e3d9
🌎 Submitting install transaction…

thread 'integration::dotenv::can_read_file' panicked at cmd/crates/soroban-test/tests/it/integration/util.rs:98:10:
called `Result::unwrap()` on an `Err` value: Install(Rpc(TransactionSubmissionFailed("Some(\n    TransactionResult {\n        fee_charged: 186496,\n        result: TxFailed(\n            VecM(\n                [\n                    OpInner(\n                        InvokeHostFunction(\n                            ResourceLimitExceeded,\n                        ),\n                    ),\n                ],\n            ),\n        ),\n        ext: V0,\n    },\n)")))
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
What did you expect to see?

Test pass

What did you see instead?

Test fails with fee limit exceeded

Dominant language
Rust
Stars
123
Forks
141
Avg merge
2d 21h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stellar/stellar-cli

All issues in stellar/stellar-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.