Error counts in generated table summary tab

[sim642]

The HTML table from table-generator on the Summary tab currently only has counts for correct/correct-unconfirmed/incorrect results, separately for true and false.

Since there can be a lot more different statuses, they could all separately be summarized there as well. For example:

• unknown results
  • unknown true
  • unknown false
• error results
  • TIMEOUT
  • OUT OF MEMORY
  • (one row for each custom error status present)

This would make it visible at a glance, if there are unexpectedly many errors of certain kind. Currently, this is merely reflected in a lower number of correct results and one has to manually go filter the full table by each error status separately to see how many of each occurred, which is a tedious process in tables with ~32000 tasks and ~20 tools where each filter change freezes the page for multiple seconds.

[PhilippWendler]

This is basically a duplicate of #239, which got closed after the current way of computing counts (via filtering) got added. However, I can understand your request and would actually now prefer to have it as well. I can't make any promise as to when this can be implemented, though.

Maybe we can even implement the idea from #239 to have the possibility to toggle visibility of these rows on demand.

[EshaanAgg]

Hi! I am Eshaan Aggarwal, a full-stack developer from India. I want to apply to this project under GSOC '24. Are there any qualification tasks associated with this project or any other minor issues that I can tackle to gain the understanding of the project in the contribution period?

[PhilippWendler]

This issue would need to be implemented inside our HTML tables, for which we have an online example. This is a React application using service workers for the statistics, so these technologies are relevant here, and it is recommended to become familiar with them. The relevant code is in StatisticsTable.js, stats.js, and stats.worker.js.

For working on other tasks in the same area of BenchExec, have a look at the issues with label HTML table.

[ayushsinha25]

This issue would need to be implemented inside our HTML tables, for which we have an online example. This is a React application using service workers for the statistics, so these technologies are relevant here, and it is recommended to become familiar with them. The relevant code is in StatisticsTable.js, stats.js, and stats.worker.js.

For working on other tasks in the same area of BenchExec, have a look at the issues with label HTML table.

SIr, Only these 3 files that you mentioned above will be major part of html tables contribution?

[PhilippWendler]

SIr, Only these 3 files that you mentioned above will be major part of html tables contribution?

For implementing this issue here I guess most of the contribution will be in those 3 files, but I other changes might be necessary as well. For a GSoC proposal it depends on what goals you want to add to your project proposal, this is up to you. (But please keep general discussions about GSoC proposals outside of the comments of a particular issue.)