ci: comment compare

[ematipico]

Summary

This PR implements workflow actions to tell github-bot to run the coverage on main branch and execute the comparison between the coverage results of this PR and the coverage results on main.

This the an example of comment in case there's an increase of coverage:

Test result	main count	This PR count	Difference
Total	17608	17608	0
Passed	16767	16787	✅ ⏫ +20
Failed	840	820	✅ ⏬ -20
Panics	1	16787	0
Coverage	95.22%	95.52%	+0.30%

And this is an example in case the coverage decreases:

Test result	main count	This PR count	Difference
Total	17608	17608	0
Passed	16767	16687	❌ ⏬ -80
Failed	840	900	❌ ⏫ +60
Panics	1	1	0
Coverage	95.22%	95.52%	+0.30%

At the moment the command is failing because I changed the logic of the command when using --json as suggested in a previous PR.

Test Plan

I run the commands manually against this PR and the main branch and made sure it works. Also, pasted the results emitted locally.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	fb4c491
Status:	✅  Deploy successful!
Preview URL:	https://20a44747.tools-8rn.pages.dev

View logs

[github-actions]

Test262 coverage results

[github-actions]

Test262 coverage results

Test result	main count	This PR count	Difference
Total	17608	17608	0
Passed	16767	16767	0
Failed	840	840	0
Panics	16767	16767	0
Coverage	95.22%	95.22%	0.00%

[MichaReiser]

Should we add some summary text to the coverage results (with some emoji?) so that it's immediately clear if everything is good or if it requires attention?

[ematipico]

Should we add some summary text to the coverage results (with some emoji?) so that it's immediately clear if everything is good or if it requires attention?

Feel free to suggest what you want. At the moment if some number changes, they are highlighted in bold.

[MichaReiser]

Looks good. Just make sure to strip out the error changes.

[github-actions]

Test262 comparison coverage results on ubuntu-latest

Test result	main count	This PR count	Difference
Total	17608	17608	0
Passed	16767	16767	0
Failed	840	840	0
Panics	1	1	0
Coverage	95.22%	95.22%	0.00%

[github-actions]

Test262 comparison coverage results on windows-latest

Test result	main count	This PR count	Difference
Total	17608	17608	0
Passed	16767	16767	0
Failed	840	840	0
Panics	1	1	0
Coverage	95.22%	95.22%	0.00%

[github-actions]

Test262 comparison coverage results on macos-latest

| Test result | main count | This PR count | Difference |'
'| :---------: | :----------: | :-----------: | :--------: |'
'| Total | 17608 | 17608 | 0 |'
'| Passed | 16767 | 16767 | 0 |'
'| Failed | 840 | 840 | 0 |'
'| Panics | 1 | 1 | 0 |'
'| Coverage | 95.22'%' | 95.22'%' | 0.00'%' |

[MichaReiser]

I noticed that it now takes quite a while until the results show up on the PR because the coverage command must run twice. Do you think there's a way to publish the result for "main" and store it (e.g. using the commit number in the name) whenever a commit gets merged so that we may just retrieve it (and only run xtask coverage in the case it's missing for whatever reason)

[ematipico]

Yes, this is something I discussed with the others during the standup.

Boa uses Github pages to store the results.

Cloudflare doesn't have a storage service yet. Github actions artifacts are not readable across workflows. Maybe, for now, we should use Github pages