This PR makes GitHub actions contain the code size and gas cost stats produced by the compilation script and the e2e test.
It is exposed as a stats.zip file that can be found at the Actions page for a commit (Look at the second heading called "artifacts"). Unfortunately there is no way to have anything other than a zip file.
So, currently this is not extremely useful other than record-keeping purposes. But my plan is merging these first, and after a few weeks create a script to fetch last N artifacts to create a line graph. This might also make it possible to do fancier things like automatically sending a PR reporting the change. But we can think about them later on once we have more data.
Another thing we can do is to have another CI step (possibly nightly) running mutation tests, and export its results in a similar fashion. We can start thinking about it once our mutation-testing strategy is more refined.
This PR makes GitHub actions contain the code size and gas cost stats produced by the compilation script and the e2e test.
It is exposed as a
stats.zipfile that can be found at the Actions page for a commit (Look at the second heading called "artifacts"). Unfortunately there is no way to have anything other than a zip file.So, currently this is not extremely useful other than record-keeping purposes. But my plan is merging these first, and after a few weeks create a script to fetch last N artifacts to create a line graph. This might also make it possible to do fancier things like automatically sending a PR reporting the change. But we can think about them later on once we have more data.
Another thing we can do is to have another CI step (possibly nightly) running mutation tests, and export its results in a similar fashion. We can start thinking about it once our mutation-testing strategy is more refined.