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

Test cases of running targets should iteratively appear as they are processed #9443

Open
berman7 opened this issue Dec 19, 2018 · 9 comments
Labels
P2 We'll consider working on this in future. (Assignee optional) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: feature request

Comments

@berman7
Copy link

berman7 commented Dec 19, 2018

Description of the feature request:

Have bazel java test runner report specific test runs outcomes as they finish (or fail), instead of collecting the output at the end of the run and only then reporting it.

what underlying problem are you trying to solve with this feature?

We use bazel from intellij, and currently the output of running tests is only displayed when the whole process has finished. This is a regression from running tests directly from intellij, which shows a very friendly UI, and especially important when running integration tests which can be lengthy.

Running with bazel 0.20.0.

@ittaiz
Copy link
Member

ittaiz commented Dec 20, 2018 via email

@or-shachar
Copy link
Contributor

ping... :)
How can we help to make it happen?

cc: @sha1n

@dslomov
Copy link
Contributor

dslomov commented Jul 5, 2019

also cc @jin as this is IDE related

@susinmotion susinmotion changed the title Feature request: Test cases of running targets should iteratively appear as they are processed Test cases of running targets should iteratively appear as they are processed Sep 25, 2019
@susinmotion
Copy link
Contributor

cc @laurentlb This looks like a front end/IDE issue -- what do you think?

@jin
Copy link
Member

jin commented Sep 25, 2019

This is definitely a BEP / Front End / IDE feature request.

A possible direction here is to expose a BEP server in the IntelliJ plugin to receive build events from Bazel as a BEP client, and update the UI in real time. For build events like test results, we'd prefer IDEs to read from BEP streams instead of the command line because of the API contract.

This is certainly nice to have, and should be an issue filed in the IntelliJ plugin repo instead of Bazel.

Edit: transferred this issue to the intellij repo.

@jin jin closed this as completed Sep 25, 2019
@jin jin transferred this issue from bazelbuild/bazel Sep 25, 2019
@jin jin reopened this Sep 25, 2019
@jin jin transferred this issue from bazelbuild/intellij Sep 26, 2019
@jin
Copy link
Member

jin commented Sep 26, 2019

After understanding this issue better, the bulk of the work here is done in Bazel and not IDEs. Bazel needs to expose a finer-grained test execution stream for IDEs to use.

Sorry for the confusion, transferring this back to the Bazel repository.

@laurentlb laurentlb added team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website and removed team-Front-End labels Jul 10, 2020
@mrkb80
Copy link

mrkb80 commented Dec 10, 2020

@jin any update on this work?

@philwo philwo added P2 We'll consider working on this in future. (Assignee optional) and removed untriaged labels Feb 8, 2021
@philwo
Copy link
Member

philwo commented Feb 8, 2021

@mai93 Hey Mai, this might be an interesting feature request for you. Assigning it as a P2, so you can have a look and prioritize.

@ittaiz
Copy link
Member

ittaiz commented Jul 14, 2022

I'm taking a look at the edit-compile-test feedback loop of devs and wanted to say again that the local dev experience with bazel is not good. To be honest many feel it is bad.
I think a significant portion is because other tools (maven, sbt, bloop) do a better job with perceived performance (for example right now IntelliJ plugin waits for the build to finish to read the file and doesn't use the stream).
While there also additional avenues of perceived performance improvements I think this area can be significant.

@mai93 mai93 removed their assignment Oct 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: feature request
Projects
None yet
Development

No branches or pull requests

10 participants