generate cucumber dashboard

[SylvainSenechal]

Issue: ZENKO-5267

Exploiting the extra cucumber log informations available in the ndjson format : Time spent on steps, by worker : We build a new graph to visualize how the step are running together, with some extra infos on step duration
Also now exporting the .html official cucumber report

Link to the new custom report (may take 5/15sec to load as the .ndjson log is ~50mb) : https://artifacts.scality.net/builds/github:scality:Zenko:staging-a91816b16b.build-iso-and-end2end-test.9170/data/ctst-end2end-sharded.1/reports/ctst-dashboard.html

The graph is generated with D3.js
I kept the whole logic in a single html file embedding everything needed to build the graph, as I don't want to clutter the codebase with too much files just for this, I prefer to have something self contained

The new graph is available in the artifacts under /report
Link is also directly available in the summary link, together with the cucumber official html report :

This should give us a good base to work on optimizing the execution speed of the tests, and identifying problematic tests (we can see kafka cleaner test taking 36 min for example)

I also used this branch for another pr, so I've already had the opportunity to generate ~10 times the graph, no problem so far

[bert-e]

Hello sylvainsenechal,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[SylvainSenechal]

im gonna keep it a buck fifty : this is fully ai generated.

I had the general idea in my head to display a chronology graph of the test, I looked at cucumber documentation and found this .ndjson format that provides run time by scenario, by step, and by worker, I told claude to use D3.js on it and voila

I opened multiple independant ai session and ask them to review/optimize/refactor the code

[SylvainSenechal]

I think there could be some nit about truncated text, resizing behavior, but imo good enough for what we want to do

[francoisferrand]

kind of mixed feeling here : it's nice, it gives us the information we need, etc... at a relatively low cost, and fundamentally we don't care so much about "how it's done".

but at the same time,

• this is code which ends up in the CI, and may need maintenance over time : yet we have absolutely no idea how it works, no way to test, ...
• are we confident it really works as it should? (i.e. no hallucination in code)
• if we want to enrich/improve (like adding integration with k8s or zkop status) we will likely hit some growth issues: i.e. it stops working unexpectedly with new features and/or changes to tests/...
• especially looking at the code, this is not just plumbing a few libs together: it reimplements a test parser, a graph renderer, etc.... so all the more opportunities to break

Basically not very happy with the engineering (kind of expected: as you said, this is mostly vibe-coded), but practically maybe good enough : I'll not vote on this one, and let others chip in...

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[delthas]

Super useful. Thanks!!