Repository navigation
Reliability reports by platforms #884
Description
Activity
- addedfeature requestNew features for node-core-utilsNew features for node-core-utils
on Jan 14, 2025 Hey @legendecas, I would love to help with this one. Three of my PRs are stuck due to a bad CI, and it's annoying to ask the maintainer every time for a CI run. If solving this issue helps, I am ready to. I have set up the repository and run the tests; all are passing. I need to know which command I need to look at.
The report workflow is defined at https://github.com/nodejs/reliability/blob/81db301596de4717b67c8463d841665f4d8ee053/.github/workflows/reliability_report.yml#L43-L48.
The command is defined at
.Lines 466 to 481 in 0bd46f4
async aggregate() { const { argv, cli } = this; if (this.queue.length === 0) { return; } const aggregator = new FailureAggregator(cli, this.json); this.json = aggregator.aggregate(); cli.log(''); cli.separator('Stats'); cli.log(''); aggregator.display(); if (argv.markdown || argv.copy) { this.markdown = aggregator.formatAsMarkdown(); } } There is a
--jsonoption available, along with--markdown(link). It can be updating the workflow in thenodejs/reliabilityto pick up the option--json, as it seems already been supported at.Line 472 in 0bd46f4
this.json = aggregator.aggregate(); Reacted by 0hm☘️
Originally posted by @legendecas in nodejs/node#56583 (comment)
A possible improvement is to generate JSON reliability reports so that the reports can be processed programatically and be filtered by platforms.
A reliability history by platform can provide supporting figures for us to determine if a platform is unstable.