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

Flaky test: gas_price::latest_gas_price__if_node_restarts_gets_latest_value #2395

Closed
netrome opened this issue Oct 25, 2024 · 3 comments · Fixed by #2401
Closed

Flaky test: gas_price::latest_gas_price__if_node_restarts_gets_latest_value #2395

netrome opened this issue Oct 25, 2024 · 3 comments · Fixed by #2401

Comments

@netrome
Copy link
Contributor

netrome commented Oct 25, 2024

Segfault observed on my build server today at cf0bc5e730c394a0552cfb424ef6a24f5088a3ba

     SIGSEGV [   5.469s] fuel-core-tests::integration_tests gas_price::latest_gas_price__if_node_restarts_gets_latest_value

--- STDOUT:              fuel-core-tests::integration_tests gas_price::latest_gas_price__if_node_restarts_gets_latest_value ---

running 1 test
Stopping fuel service
test gas_price::latest_gas_price__if_node_restarts_gets_latest_value ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 235 filtered out; finished in 5.45s
@netrome netrome changed the title Flaky test Flaky test: gas_price::latest_gas_price__if_node_restarts_gets_latest_value Oct 25, 2024
@netrome
Copy link
Contributor Author

netrome commented Oct 25, 2024

These errors seem related so I'm not opening separate issues for them right now:

     SIGABRT [   9.128s] fuel-core-tests::integration_tests recovery::gas_price_updater__if_no_metadata_history_start_from_current_block

--- STDOUT:              fuel-core-tests::integration_tests recovery::gas_price_updater__if_no_metadata_history_start_from_current_block ---

running 1 test
Stopping fuel service
test recovery::gas_price_updater__if_no_metadata_history_start_from_current_block ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 235 filtered out; finished in 9.11s

and

     SIGABRT [   5.151s] fuel-core-tests::integration_tests gas_price::startup__can_override_gas_price_values_by_changing_config

--- STDOUT:              fuel-core-tests::integration_tests gas_price::startup__can_override_gas_price_values_by_changing_config ---

running 1 test
Stopping fuel service
test gas_price::startup__can_override_gas_price_values_by_changing_config ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 235 filtered out; finished in 5.13s

@MitchTurner
Copy link
Member

running 1 test
test gas_price::latest_gas_price__if_node_restarts_gets_latest_value ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 235 filtered out; finished in 3.28s

error: test failed, to rerun pass `--test integration_tests`

Caused by:
  process didn't exit successfully: `/Users/jamesturner/fuel/fuel-core/target/debug/deps/integration_tests-5d6afae6c12a7031 'gas_price::latest_gas_price__if_node_restarts_gets_latest_value' --exact` (signal: 11, SIGSEGV: invalid memory reference)

Process finished with exit code 101

@rafal-ch
Copy link
Contributor

These errors seem related so I'm not opening separate issues for them right now:

     SIGABRT [   5.151s] fuel-core-tests::integration_tests gas_price::startup__can_override_gas_price_values_by_changing_config

--- STDOUT:              fuel-core-tests::integration_tests gas_price::startup__can_override_gas_price_values_by_changing_config ---

I spotted this failure on CI on Dec the 4th, so after #2401 has been merged. I'll open a flaky-test issue for startup__can_override_gas_price_values_by_changing_config

cc: @netrome

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

Successfully merging a pull request may close this issue.

3 participants