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

Same output for westend and ethereum smart contracts test #16

Open
IkerAlus opened this issue Nov 6, 2024 · 0 comments
Open

Same output for westend and ethereum smart contracts test #16

IkerAlus opened this issue Nov 6, 2024 · 0 comments

Comments

@IkerAlus
Copy link
Collaborator

IkerAlus commented Nov 6, 2024

In the current version on main, both for ethereum and westend networks, when running with the --smart-contracts flag the output is:

Nothing to compile
No need to generate any newer typings.


  Block
    Functionality
Storage deployed to: undefined
      ✔ Should return the correct value when multiplying (1460ms)
      ✔ Should return the correct baseFee
      ✔ Should return the correct chainId
      ✔ Should return the correct timestamp
      ✔ Should return the correct gasLimit
      ✔ Should return the correct blocknumber
      ✔ Should return the correct blockHash

  ExplicitRevertReason
    Functionality
      ✔ Should fail with revert reason (155ms)
      ✔ Should return the given input

  Lock
    Deployment
      ✔ Should set the right unlockTime (93ms)
      ✔ Should set the right owner
      1) Should receive and store the funds to lock
      ✔ Should fail if the unlockTime is not in the future (81ms)
    Withdrawals
      Validations
        ✔ Should revert with the right error if called too soon
        ✔ Should revert with the right error if called from another account
        ✔ Shouldn't fail if the unlockTime has arrived and the owner calls it
      Events
        2) Should emit an event on withdrawals
      Transfers
        3) Should transfer the funds to the owner

  Storage
    Functionality
Storage deployed to: undefined
      ✔ Should return the empty data when storage is called for the first time (128ms)
      ✔ Should return the input data


  17 passing (2s)
  3 failing

  1) Lock
       Deployment
         Should receive and store the funds to lock:

      AssertionError: expected 1100001000000000 to equal 1000000000.
      + expected - actual

      -1100001000000000
      +1000000000
      
      at Context.<anonymous> (test/Lock.ts:43:68)

  2) Lock
       Withdrawals
         Events
           Should emit an event on withdrawals:

      AssertionError: Error in "Withdrawal" event: Error in the 1st argument assertion: expected 1100001000000000 to equal 1000000000.
      + expected - actual

      -1100001000000000
      +1000000000
      
      at async Context.<anonymous> (test/Lock.ts:98:9)

  3) Lock
       Withdrawals
         Transfers
           Should transfer the funds to the owner:
     AssertionError: Expected the ether balance of 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 (the 1st address in the list) to change by 1000000000 wei, but it changed by 1100001000000000 wei
Expected the ether balance of 0x9A8Ec3B44ee760b629e204900c86d67414a67e8f (the 2nd address in the list) to change by -1000000000 wei, but it changed by -1100001000000000 wei
      at async Context.<anonymous> (test/Lock.ts:112:9)

where the only differences are in the reported times to complete.

This output is different from the one given by the other networks where the whole Uniswap v3 test coverage is ran.

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

No branches or pull requests

1 participant