You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can no longer see whats happening while it's happening, the log lines were usually not truncated, and even when they were truncated, we can have a very good idea of what is running (configure, make, install, etc... with the exact commands printed in the UI).
It would be great to restore this grouping; I would have expected the RE service and buildbox to send us the messages for every command which runs in every group, whilst they are getting run in the remote worker (or local buildbox daemon).
I think this is a fairly severe regression of the UI and master log.
The text was updated successfully, but these errors were encountered:
See original issue on GitLab
In GitLab by [Gitlab user @tristanvb] on Sep 20, 2020, 08:45
When we run the configure commands, we usually see:
And when we run build commands, we usually see:
But with command batching for
RE
purposes, we've degraded the quality of the UI, and we see:We can no longer see whats happening while it's happening, the log lines were usually not truncated, and even when they were truncated, we can have a very good idea of what is running (configure, make, install, etc... with the exact commands printed in the UI).
It would be great to restore this grouping; I would have expected the RE service and buildbox to send us the messages for every command which runs in every group, whilst they are getting run in the remote worker (or local buildbox daemon).
I think this is a fairly severe regression of the UI and master log.
The text was updated successfully, but these errors were encountered: