Open andygolay opened 1 week ago
If we had our new e2e running on cicd:bridge
job, this would have caught the issue before merging. This effectively stalls e2e testing on the bridge. What I would suggest is a dedicated PR just to add the bridge e2e
test in CI (at the moment it's just integration tests).
Then revert this PR, and re-merge it with it having to pass that test.
@l-monninger @0xPrimata please chime in on what you think the appropriate approach is here.
Describe the bug
Suzuka + bridge build, run with command
fails since the merge of 651 (commit
7aa85be210524d0b18c1f29299e4f3be8778d13b Merge pull request #561 from movementlabsxyz/primata/contract-pipeline
)See screenshot for error:
This highlights the need to utilize proper CI checks when merging PRs.
To Reproduce
At the
movement
project root:You should see
This is the commit prior to the merge of 651.
Expected behavior This command should start the bridge without errors:
Screenshots Expected behavior screenshot: