I used to work at a fairly large fabless semiconductor company on the team that developed the internal tools for doing almost exactly what you were doing.
Tooling hasn’t kept up. The state of the art in collaborative debugging is to walk to a coworker’s desk and point to an error in a log file or waveform file. Each chip company rolls out its own tooling and infra to deal with this—this was Kay’s (one of our cofounders) entire job at his last gig.
This is definitely an exaggeration, the tooling has always been a bit "dated" but vManager from Cadence has all the features you are describing (and more). I think nowadays they offer a fully managed cloud service as well. I'm guessing other vendors have similar offerings but we were primarily a Cadence shop.
On the topic of web viewing, do you know that engineers want this? In my experience, managers liked it because they could get an overview quickly, but the engineers hated it because it involved copy-pasting paths from the browser to their local tools.
We had vManager but some teams used their own test runner/manager with a web viewer(similar to your tool) and I ended up building a little TUI that the engineers could use instead. It worked almost the same, except it let you directly relaunch failing tests in an interactive simvision session for debugging, open log files in vim and open the coverage report for the regression.
Anyway, good luck! I always thought that the EDA industry was ripe for disruption, wish you guys all the best!
On the topic of web viewing, do you know that engineers want this? In my experience, managers liked it because they could get an overview quickly, but the engineers hated it because it involved copy-pasting paths from the browser to their local tools.
In my experience it's the opposite. While some firms issue Linux workstations to their engineers most use VDIs (and god forbid sometimes VNC) hosted in a datacenter that can be far from the office. The already poor latency becomes atrocious when they say open Verdi over LSF, which is X-forwarded from the host to the VM before getting encoded and sent to the client.
Web tools bring the interface and rendering over to the client side and allow for a much smoother experience even if the server is physically far away.
Comments
I used to work at a fairly large fabless semiconductor company on the team that developed the internal tools for doing almost exactly what you were doing.
This is definitely an exaggeration, the tooling has always been a bit "dated" but vManager from Cadence has all the features you are describing (and more). I think nowadays they offer a fully managed cloud service as well. I'm guessing other vendors have similar offerings but we were primarily a Cadence shop.
On the topic of web viewing, do you know that engineers want this? In my experience, managers liked it because they could get an overview quickly, but the engineers hated it because it involved copy-pasting paths from the browser to their local tools.
We had vManager but some teams used their own test runner/manager with a web viewer(similar to your tool) and I ended up building a little TUI that the engineers could use instead. It worked almost the same, except it let you directly relaunch failing tests in an interactive simvision session for debugging, open log files in vim and open the coverage report for the regression.
Anyway, good luck! I always thought that the EDA industry was ripe for disruption, wish you guys all the best!
In my experience it's the opposite. While some firms issue Linux workstations to their engineers most use VDIs (and god forbid sometimes VNC) hosted in a datacenter that can be far from the office. The already poor latency becomes atrocious when they say open Verdi over LSF, which is X-forwarded from the host to the VM before getting encoded and sent to the client.
Web tools bring the interface and rendering over to the client side and allow for a much smoother experience even if the server is physically far away.
That's why I use vscode w/ remote ssh. Can't stand input lag on my typing.