Skip to content
This repository has been archived by the owner on May 4, 2024. It is now read-only.

[evm] npx hardhat test get affected by previous Move packages in a different git branch #47

Closed
junkil-park opened this issue Apr 18, 2022 · 1 comment · Fixed by #105
Assignees

Comments

@junkil-park
Copy link
Collaborator

See the error log:

$ npx hardhat test
An unexpected error occurred:

[Error: ENOENT: no such file or directory, stat '/Users/jkpark/Work/move/language/evm/hardhat-examples/contracts/ERC721Mock/Move.toml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'stat',
  path: '/Users/jkpark/Work/move/language/evm/hardhat-examples/contracts/ERC721Mock/Move.toml'
}

contracts/ERC721Mock does not exist in this branch. It did in a different branch. However, it complains.

@vgao1996 vgao1996 self-assigned this Apr 18, 2022
@vgao1996
Copy link
Member

This is caused by move package build not cleaning up old artifacts. I'll put up a patch to address this and #27 together as the underlying logic is related.

More precisely, move package build --arch ethereum should check if there are any existing artifacts before rebuilding:

  1. If all artifacts are newer than the source, then it should do nothing
  2. If any of the artifacts is older than the source, then it should delete all existing artifacts and rebuild everything

@vgao1996 vgao1996 reopened this May 5, 2022
@vgao1996 vgao1996 closed this as completed May 5, 2022
brson pushed a commit to brson/move that referenced this issue Feb 21, 2023
brson pushed a commit to brson/move that referenced this issue Mar 23, 2023
brson pushed a commit to brson/move that referenced this issue Mar 23, 2023
brson pushed a commit to brson/move that referenced this issue Jul 17, 2023
brson pushed a commit to brson/move that referenced this issue Jul 17, 2023
brson pushed a commit to brson/move that referenced this issue Jul 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants