Skip to content
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

Grouped commands are no longer grouped in the UI #1395

Open
Cynical-Optimist opened this issue Oct 14, 2020 · 0 comments
Open

Grouped commands are no longer grouped in the UI #1395

Cynical-Optimist opened this issue Oct 14, 2020 · 0 comments

Comments

@Cynical-Optimist
Copy link

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:

[log line] Running configure-commands

    ./configure --prefix=/usr
        --enable-foo
        ...
        ...

And when we run build commands, we usually see:

[log line] Running build-commands

    ./configure --prefix=/usr
        --enable-foo
        ...
        ...

But with command batching for RE purposes, we've degraded the quality of the UI, and we see:

[log line] Running commands

    ./configure --prefix=/usr
        --enable-foo
        ...
        ...

    Message contained 97 more lines

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant