Skip to content
Charts

ci: replace release notes generator action with one maintained by ste… #6352

Sign in to view logs

ci: replace release notes generator action with one maintained by ste…

ci: replace release notes generator action with one maintained by ste… #6352

GitHub Actions / Test Results succeeded Nov 23, 2024 in 0s

All 100 tests pass, 2 skipped in 1m 36s

  1 files   -  1   24 suites  +4   1m 36s ⏱️ +37s
102 tests +33  100 ✅ +34  2 💤 ±0  0 ❌  - 1 
102 runs  + 7  100 ✅ + 8  2 💤 ±0  0 ❌  - 1 

Results for commit 7accf1f. ± Comparison against earlier commit dc860b3.

Annotations

Check notice on line 0 in .github

See this annotation in the file changed.

@github-actions github-actions / Test Results

2 skipped tests found 

There are 2 skipped tests, see "Raw output" for the full list of skipped tests.
Raw output 
011 Should fail when calling msgValue with more value than available balance ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 011 Should fail when calling msgValue with more value than available balance
011 Should fail when calling msgValue with more value than available balance ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 011 Should fail when calling msgValue with more value than available balance

Check notice on line 0 in .github

See this annotation in the file changed.

@github-actions github-actions / Test Results

102 tests found 

There are 102 tests, see "Raw output" for the full list of tests.
Raw output 
"eth_call" for non-existing contract address returns 0x ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call "eth_call" for non-existing contract address returns 0x
001 Should call pureMultiply ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 001 Should call pureMultiply
001 Should call pureMultiply ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 001 Should call pureMultiply
002 Should call msgSender ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 002 Should call msgSender
002 Should call msgSender ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 002 Should call msgSender
003 Should call txOrigin ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 003 Should call txOrigin
003 Should call txOrigin ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 003 Should call txOrigin
004 Should call msgSig ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 004 Should call msgSig
004 Should call msgSig ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 004 Should call msgSig
005 Should call addressBalance ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 005 Should call addressBalance
005 Should call addressBalance ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 005 Should call addressBalance
006 'data' from request body with wrong method signature ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 006 'data' from request body with wrong method signature
006 'data' from request body with wrong method signature ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 006 'data' from request body with wrong method signature
007 'data' from request body with wrong encoded parameter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 007 'data' from request body with wrong encoded parameter
007 'data' from request body with wrong encoded parameter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 007 'data' from request body with wrong encoded parameter
008 should work for missing 'from' field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 008 should work for missing 'from' field
008 should work for missing 'from' field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 008 should work for missing 'from' field
009 should work for missing 'to' field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 009 should work for missing 'to' field
009 should work for missing 'to' field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 009 should work for missing 'to' field
010 Should call msgValue ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 010 Should call msgValue
010 Should call msgValue ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 010 Should call msgValue
011 Should fail when calling msgValue with more value than available balance ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 011 Should fail when calling msgValue with more value than available balance
011 Should fail when calling msgValue with more value than available balance ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 011 Should fail when calling msgValue with more value than available balance
012 should work for wrong 'from' field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With evm address 012 should work for wrong 'from' field
012 should work for wrong 'from' field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call Caller contract With long-zero address 012 should work for wrong 'from' field
@release should be able to call eth_getFilterChanges for NEW_BLOCK filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Positive @release should be able to call eth_getFilterChanges for NEW_BLOCK filter
@release should be able to create a log filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Positive @release should be able to create a log filter
@release should be able to create a newBlock filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Positive @release should be able to create a newBlock filter
@release should be able to debug a failing CALL transaction of type 1559 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 @release should be able to debug a failing CALL transaction of type 1559 with call depth and onlyTopCall false
@release should be able to debug a failing CREATE transaction of type 1559 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 @release should be able to debug a failing CREATE transaction of type 1559 with call depth and onlyTopCall false
@release should be able to debug a successful CALL transaction of type 1559 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 @release should be able to debug a successful CALL transaction of type 1559 with call depth and onlyTopCall true
@release should be able to debug a successful CREATE transaction of type 1559 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 @release should be able to debug a successful CREATE transaction of type 1559 with call depth and onlyTopCall true
@release should execute "eth_call" request to Basic contract ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call @release should execute "eth_call" request to Basic contract
@release should execute "eth_call" request to simulate deploying a contract with `to` field being empty/undefined ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call @release should execute "eth_call" request to simulate deploying a contract with `to` field being empty/undefined
@release should execute "eth_call" request to simulate deploying a contract with `to` field being null ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call @release should execute "eth_call" request to simulate deploying a contract with `to` field being null
@release should execute "eth_getTransactionCount" contract latest ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" contract latest
@release should execute "eth_getTransactionCount" contract with id converted to evm_address historic ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" contract with id converted to evm_address historic
@release should execute "eth_getTransactionCount" contract with id converted to evm_address latest ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" contract with id converted to evm_address latest
@release should execute "eth_getTransactionCount" for account with id converted to evm_address ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" for account with id converted to evm_address
@release should execute "eth_getTransactionCount" historic ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" historic
@release should execute "eth_getTransactionCount" primary ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" primary
@release should execute "eth_getTransactionCount" with block hash ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount @release should execute "eth_getTransactionCount" with block hash
Function calling HederaTokenService.isToken(token) ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call with contract that calls precompiles Function calling HederaTokenService.isToken(token)
Pure method revertWithCustomErrorPure returns tx receipt ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts eth_call for reverted pure contract calls Pure method revertWithCustomErrorPure returns tx receipt
Pure method revertWithNothingPure returns tx receipt ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts eth_call for reverted pure contract calls Pure method revertWithNothingPure returns tx receipt
Pure method revertWithPanicPure returns tx receipt ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts eth_call for reverted pure contract calls Pure method revertWithPanicPure returns tx receipt
Pure method revertWithStringPure returns tx receipt ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts eth_call for reverted pure contract calls Pure method revertWithStringPure returns tx receipt
Returns revert message for pure methods ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts Returns revert message for pure methods
Returns revert message for view methods ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts Returns revert message for view methods
Returns revert reason in receipt for payable methods ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Contract call reverts Returns revert reason in receipt for payable methods
Should return a batch of requests ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Batch Request Test Suite BATCH_REQUESTS_ENABLED = true Should return a batch of requests
Type 3 transactions are not supported for eth_sendRawTransaction ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Shard Blob Transactions Type 3 transactions are not supported for eth_sendRawTransaction
eth_call contract revert returns 200 http status ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call eth_call contract revert returns 200 http status
nonce for contract correctly increments ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount nonce for contract correctly increments
should NOT allow eth_call to process IHRC719.isAssociated() method ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call with contract that calls precompiles eth_call with force-to-consensus-by-selector logic should NOT allow eth_call to process IHRC719.isAssociated() method
should allow eth_call to successfully process IHRC719.isAssociated() method ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call with contract that calls precompiles eth_call with force-to-consensus-by-selector logic should allow eth_call to successfully process IHRC719.isAssociated() method
should be able to debug a failing CALL transaction of type 1559 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 should be able to debug a failing CALL transaction of type 1559 with call depth and onlyTopCall true
should be able to debug a failing CALL transaction of type 2930 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a failing CALL transaction of type 2930 with call depth and onlyTopCall false
should be able to debug a failing CALL transaction of type 2930 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a failing CALL transaction of type 2930 with call depth and onlyTopCall true
should be able to debug a failing CALL transaction of type Legacy with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a failing CALL transaction of type Legacy with call depth and onlyTopCall true
should be able to debug a failing CALL transaction with revert reason of type Legacy with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a failing CALL transaction with revert reason of type Legacy with call depth and onlyTopCall false
should be able to debug a failing CREATE transaction of type 1559 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 should be able to debug a failing CREATE transaction of type 1559 with call depth and onlyTopCall true
should be able to debug a failing CREATE transaction of type 2930 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a failing CREATE transaction of type 2930 with call depth and onlyTopCall false
should be able to debug a failing CREATE transaction of type 2930 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a failing CREATE transaction of type 2930 with call depth and onlyTopCall true
should be able to debug a failing CREATE transaction of type Legacy with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a failing CREATE transaction of type Legacy with call depth and onlyTopCall false
should be able to debug a failing CREATE transaction of type Legacy with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a failing CREATE transaction of type Legacy with call depth and onlyTopCall true
should be able to debug a successful CALL transaction of type 1559 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 should be able to debug a successful CALL transaction of type 1559 with call depth and onlyTopCall false
should be able to debug a successful CALL transaction of type 2930 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a successful CALL transaction of type 2930 with call depth and onlyTopCall false
should be able to debug a successful CALL transaction of type 2930 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a successful CALL transaction of type 2930 with call depth and onlyTopCall true
should be able to debug a successful CALL transaction of type Legacy with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a successful CALL transaction of type Legacy with call depth and onlyTopCall false
should be able to debug a successful CALL transaction of type Legacy with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a successful CALL transaction of type Legacy with call depth and onlyTopCall true
should be able to debug a successful CREATE transaction of type 1559 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type: 2 should be able to debug a successful CREATE transaction of type 1559 with call depth and onlyTopCall false
should be able to debug a successful CREATE transaction of type 2930 with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a successful CREATE transaction of type 2930 with call depth and onlyTopCall false
should be able to debug a successful CREATE transaction of type 2930 with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transaction of type 1 should be able to debug a successful CREATE transaction of type 2930 with call depth and onlyTopCall true
should be able to debug a successful CREATE transaction of type Legacy with call depth and onlyTopCall false ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a successful CREATE transaction of type Legacy with call depth and onlyTopCall false
should be able to debug a successful CREATE transaction of type Legacy with call depth and onlyTopCall true ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Positive scenarios Test transactions of type 0 should be able to debug a successful CREATE transaction of type Legacy with call depth and onlyTopCall true
should be able to uninstall existing log filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Positive should be able to uninstall existing log filter
should be able to uninstall existing newBlock filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Positive should be able to uninstall existing newBlock filter
should execute "eth_call" with both data and input fields ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with both data and input fields
should execute "eth_call" with correct block hash object ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with correct block hash object
should execute "eth_call" with correct block number object ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with correct block number object
should execute "eth_call" with correct block number ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with correct block number
should execute "eth_call" with incorrect block hash object, SC should not exist yet ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with incorrect block hash object, SC should not exist yet
should execute "eth_call" with incorrect block number as an object, SC should not exist yet ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with incorrect block number as an object, SC should not exist yet
should execute "eth_call" with incorrect block number, SC should not exist yet ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" with incorrect block number, SC should not exist yet
should execute "eth_call" without from field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" without from field
should execute "eth_call" without gas field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should execute "eth_call" without gas field
should execute "eth_getTransactionCount" for account with non-zero nonce ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount should execute "eth_getTransactionCount" for account with non-zero nonce
should execute "eth_getTransactionCount" for non-existing address ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount should execute "eth_getTransactionCount" for non-existing address
should execute "eth_getTransactionCount" from hollow account ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount should execute "eth_getTransactionCount" from hollow account
should execute "eth_getTransactionCount" secondary ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_getTransactionCount should execute "eth_getTransactionCount" secondary
should fail "eth_call" request without data field ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should fail "eth_call" request without data field
should fail to debug a transaction with invalid onlyTopCall value type ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Negative scenarios should fail to debug a transaction with invalid onlyTopCall value type
should fail to debug a transaction with invalid tracer type ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Negative scenarios should fail to debug a transaction with invalid tracer type
should fail to execute "eth_call" with wrong block hash object ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should fail to execute "eth_call" with wrong block hash object
should fail to execute "eth_call" with wrong block number object ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should fail to execute "eth_call" with wrong block number object
should fail to execute "eth_call" with wrong block number ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should fail to execute "eth_call" with wrong block number
should fail to execute "eth_call" with wrong block tag ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests eth_call should fail to execute "eth_call" with wrong block tag
should not be able to call eth_getFilterChanges for not existing filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Negative should not be able to call eth_getFilterChanges for not existing filter
should not be able to uninstall not existing filter ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Negative should not be able to uninstall not existing filter
should not support "eth_newPendingTransactionFilter" ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Filter API Test Suite Negative should not support "eth_newPendingTransactionFilter"
should return 400 error for non-existing transaction hash ‑ RPC Server Acceptance Tests Acceptance tests @api-batch-3 RPC Server Acceptance Tests Debug API Test Suite Negative scenarios should return 400 error for non-existing transaction hash
View more details on GitHub Actions