Skip to content

fix: execute-block handle no explicit --at #84

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Apr 30, 2024
Merged

fix: execute-block handle no explicit --at #84

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7910de3
fix none at
liamaharon Apr 29, 2024
bb62ecf
bump version
liamaharon Apr 29, 2024
3595669
comments
liamaharon Apr 29, 2024
0f37bde
clippy
liamaharon Apr 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
comments
  • Loading branch information
@liamaharon
liamaharon committed Apr 29, 2024
commit 3595669637a0ab376429637a33561a2ee9f5c6dc
4 changes: 1 addition & 3 deletions core/tests/execute_block.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,14 +105,12 @@ async fn execute_block_works() {

// Try to execute the block.
let mut block_execution = execute_block(&ws_url);

// The execute-block command is actually executing the next block.
let expected_output = r".*Block #(\d+) successfully executed";
let re = Regex::new(expected_output).unwrap();
let matched =
common::wait_for_stream_pattern_match(block_execution.stderr.take().unwrap(), re).await;

// Assert that the block-execution process has executed the expected block.
// Assert that the block-execution process has executed a block.
assert!(matched.is_ok());

// Assert that the block-execution exited succesfully
Expand Down