You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the signing process is set (like in the Spec.MultiSig module of the use-cases-testsuit). It doesn't seem the signatures are added to the transaction.
In the latest plutus, after looking at the Spec module of use-cases it looks like the reason for this is needing to adopt a newer signing API.
Steps to reproduce the behavior
clone plutus-apps
run nix-shell
cd into the plutus-use-cases repo
cabal repl plutus-use-cases-test
ghci> import Test.Tasty
ghci> import Spec.MultiSig
ghci> defaultMain tests
wait for test to fail
Actual Result
2 out of 3 tests failed (0.01s)
is the output from my machine
Expected Result
I expect the tests will pass once the update to the new signing api is complete.
Summary
When the signing process is set (like in the Spec.MultiSig module of the use-cases-testsuit). It doesn't seem the signatures are added to the transaction.
In the latest plutus, after looking at the Spec module of use-cases it looks like the reason for this is needing to adopt a newer signing API.
Steps to reproduce the behavior
nix-shell
cabal repl plutus-use-cases-test
ghci> import Test.Tasty
ghci> import Spec.MultiSig
ghci> defaultMain tests
Actual Result
2 out of 3 tests failed (0.01s)
is the output from my machine
Expected Result
I expect the tests will pass once the update to the new signing api is complete.
Describe the approach you would take to fix this
No response
System info
OS: NixOS
Plutus: 4127e9cd6e889824d724c30eae55033cb50cbf3e
The text was updated successfully, but these errors were encountered: