-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plot the evolution of the jobs running time and performance metrics #69
Comments
In GitLab by @mcastril on Feb 3, 2023, 20:28 I agree it's interesting, it's a good idea, @gmontane. Note that, concerning the Testing Suite, I had already created this issue in the corresponding project: https://earth.bsc.es/gitlab/es/testing_suite/-/issues/32 I think this is something that you, Eric, Alejandro or Genís could implement in the testing suite without much effort. In the GUI it could take some more time. |
In GitLab by @gmontane on Feb 7, 2023, 10:24 You're right @mcastril, I completely forgot about the testing suite issue. Anyway, if you think it is feasible, it would be great to have it integrated in the GUI. It is not an urgent thing, so I think we can wait. |
In GitLab by @jberlin on Feb 7, 2023, 10:26 Hi @gmontane , could please provide a sample graph of the data you want to display, maybe you can create a mockup in google spreadsheet with the desired layout, this will speed up the implementation a bit. thanks! |
In GitLab by @gmontane on Feb 7, 2023, 11:01 Only COMPLETED jobs should be taken into account. |
In GitLab by @mcastril on Feb 15, 2023, 16:51 We are still looking for the new GUI developer. New developments like this one will take time. |
In GitLab by @gmontane on Feb 3, 2023, 17:10
Currently we can see the running time and some performance metrics from the previous runs of a particular job in a table. Would it be possible to show also this information in a graph? I'm not sure if this should go in the historical runs view or inside the Performance metrics tab, but it would make it easier to see the evolution of the different metrics in time, particularly in the testing suite runs.
@jberlin @mcastril
The text was updated successfully, but these errors were encountered: