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
{{ message }}
This repository has been archived by the owner on Dec 2, 2024. It is now read-only.
One test from plutus-pab-test-full namely can wait for tx output status change fails in my branch about once every 10th test. I reproduced the fail in the main branch by running tests in a loop.
Subjectively it feels like the test fails less often in main and also i could only reproduce it with the error in Actual result. But on my branch that forks from next-node I could also get the error shown below (1).
I definitely could have introduced an additional bug.
Error (1)
[INFO] W79f9602: Signing tx: 9056fcfce1f248c624d91e6e135c293545375dbe5b0936be0f910be243f96786
[INFO] W79f9602: Submitting tx: 9056fcfce1f248c624d91e6e135c293545375dbe5b0936be0f910be243f96786
FAIL
Exception: OtherError "tx output 1 should be tentatively confirmed of depth 1 Expected: TentativelyConfirmed (Depth {unDepth = 1}) TxValid (Spent 9056fcfce1f248c624d91e6e135c293545375dbe5b0936be0f910be243f96786) Actual: TentativelyConfirmed (Depth {unDepth = 1}) TxValid Unspent"
CallStack (from HasCallStack):
error, called at test/full/Plutus/PAB/CoreSpec.hs:103:21 in main:Plutus.PAB.CoreSpec
Reproduced on next-node also getting a new error message:
FAIL
Exception: OtherError "tx output 1 should be committed Expected: Committed TxValid (Spent 04fd3feec8742efd0504593e9a7a5d795a16bdbba9ee803a6bd5f582f25a60ef) Actual: TentativelyConfirmed (Depth {unDepth = 8}) TxValid (Spent 04fd3feec8742efd0504593e9a7a5d795a16bdbba9ee803a6bd5f582f25a60ef)"
CallStack (from HasCallStack):
error, called at test/full/Plutus/PAB/CoreSpec.hs:103:21 in main:Plutus.PAB.CoreSpec
Summary
One test from
plutus-pab-test-full
namelycan wait for tx output status change
fails in my branch about once every 10th test. I reproduced the fail in themain
branch by running tests in a loop.Subjectively it feels like the test fails less often in
main
and also i could only reproduce it with the error in Actual result. But on my branch that forks fromnext-node
I could also get the error shown below (1).I definitely could have introduced an additional bug.
Error (1)
Reproduced on
next-node
also getting a new error message:Steps to reproduce the behavior
main
,next-node
or Update tx with missing fields. #468LANG=C.UTF-8 cabal run plutus-pab-test-full -- -p '/can wait for tx output status change/'
to run test in a loop until fails.
Actual Result
Expected Result
No errors observed.
Describe the approach you would take to fix this
I will try reproduce on
next-node
.I will look for a bug that I might have introduced, but also let me know if some nondeterminism is expected here and in what form.
System info
plutus-apps:
The text was updated successfully, but these errors were encountered: