This is an archive of the discontinued Mercurial Phabricator instance.

ci: generate and report XML test results
Needs RevisionPublic

Authored by danchr on Jan 12 2021, 7:07 AM.

Details

Reviewers
pulkit
Group Reviewers
hg-reviewers

Diff Detail

Repository
rHG Mercurial
Branch
default
Lint
No Linters Available
Unit
No Unit Test Coverage

Event Timeline

danchr created this revision.Jan 12 2021, 7:07 AM
baymax updated this revision to Diff 24870.Jan 14 2021, 9:18 PM

❎ refresh by Heptapod after a failed CI run (🐙 ❤️) https://foss.heptapod.net/octobus/mercurial-devel/-/pipelines/16444

This looks fine, but could you describe a bit what this is suppose to achieve and maybe provide a link to an example ?

pulkit accepted this revision.Jan 29 2021, 3:15 PM
This revision is now accepted and ready to land.Jan 29 2021, 3:15 PM
pulkit added a comment.Feb 3 2021, 4:01 AM

I am happy to push this and next one but they needs to be rebased on current tip of default branch.

This looks fine, but could you describe a bit what this is suppose to achieve and maybe provide a link to an example ?

It exposes the unit tests results to GitLab CI, for nice rendering. See for example this run: https://foss.heptapod.net/octobus/mercurial-devel/-/pipelines/16444/test_report

You also get a summary in any merge request detailing any failed or fixed tests.

This looks fine, but could you describe a bit what this is suppose to achieve and maybe provide a link to an example ?

It exposes the unit tests results to GitLab CI, for nice rendering. See for example this run: https://foss.heptapod.net/octobus/mercurial-devel/-/pipelines/16444/test_report
You also get a summary in any merge request detailing any failed or fixed tests.

ho interresting, thanks.

pulkit requested changes to this revision.Mar 10 2021, 4:15 AM

This patch does not apply on current tip of default branch. Kindly rebase and resend.

This revision now requires changes to proceed.Mar 10 2021, 4:15 AM