Closed RoyTimes closed 3 years ago
Thanks reporting, we just came back from vacation, would solve it soon.
The latest version should now have solved this problem and support multi-contract compilation. See this example at https://github.com/patractlabs/redspot/blob/master/examples/multi-contract/redspot.config.ts. Documentation will be added when the official version is released.
To reproduce: compile your smart contract with either
yarn build
. Then, change the smart contract to cause some compile errors and runyarn build
oryarn test
again. Redspot will fail to stop the workflow and proceed with the outdated output files.When the
cargo
cmd throws error, Redspot does not detect the errors thrown. Instead, it tries to copy the.wasm
and.json
files and throw errors when these files fail to be generated. However, if there are previously successful builds that have generated these files but the current build fails, Redspot will have no trouble copying these output to theartifacts
folder and, therefore, fail to stop the rest of the workflow and proceed with the outdated compiled smart contract files.