[Bug] bacon test doesn't let you scroll its output when there are failed tests

[miguno]

When I run bacon test on a test suite with no failed tests, then I can scroll bacon's output (e.g., in a small terminal window):

^ Note the white scrollbar on the right edge of the screenshot

However, whenever there's at least one failed test, then I can no longer scroll the output of bacon test:

^ Note the lack of a scrollbar.

I tried this both with and without a bacon.toml file (the file, if present, was the default one generated with bacon --init).

Environment:

• macOS
• WezTerm terminal
• bacon version 2.8.1

[miguno]

Possibly related to #133

[dzfrias]

Possibly related to #133

I'm having this issue too. I don't have nextest set up, though. I upgraded my version of bacon, and this issue started appearing. I'm not sure which release caused it though.

[dzfrias]

I tried uninstalling v2.8.1 and installed v2.8.0 and I'm getting the proper output now. I'm on macOS and using Alacritty.

Entering this into my terminal (not through bacon) returns a status code of 101:

bacon/defaults/default-bacon.toml

Lines 27 to 30 in 2f6ad15

	command = [
	"cargo", "test", "--color", "always",
	"--", "--color", "always", # see https://github.com/Canop/bacon/issues/124
	]

[miguno]

The original bug described in my first comment also happens on Ubuntu in WSL2 on Windows 11.

[joshka]

+1 macbook m2 / iterm (both with test and nextest)

[Canop]

This should be fixed by #140 - testers welcome

[miguno]

@Canop : Thanks for the update! #140 does fix the scrolling issue (when there are failing tests) on my side.

[miguno]

Addendum: What is still looking wrong to me though is that errors (or warnings) are not shown right at the top of bacon's output. Here's an example of a failed test suite, with bacon 2.9.0-dev:

I would have expected that the error, which is actually shown at the bottom of the output above, would be shown at the top of bacon's output, similar to the screenshot in the README.

[Canop]

@miguno It's still not parsed. Can you push your project so that I test?

[miguno]

Here's an example project: https://github.com/miguno/rust-template

Open https://github.com/miguno/rust-template/blob/main/tests/tests.rs and modify one of the simple tests to make them fail, and then run bacon test.

[Canop]

Here's what I get with #140:

Are you sure you were using the right version of bacon in your test ?

[miguno]

Are you sure you were using the right version of bacon in your test ?

Yes, I am sure.

Now pressing ? to show the built-in help, note the 2.9.0-dev version string at the top:

Bacon was installed with:

$ cargo install --git https://github.com/Canop/bacon --rev 30f850ca0bff2cbc0c6894eaf32d27ca452a7ddf --force bacon

Bacon was run with:

$ bacon test

Environment:

• macOS
• WezTerm terminal (same behavior also with iTerm and the built-in Terminal.app of macOS)
• bacon version 2.9.0-dev
• zsh

[Canop]

Bacon was installed with:

$ cargo install --git https://github.com/Canop/bacon --rev 30f850ca0bff2cbc0c6894eaf32d27ca452a7ddf --force bacon

This doesn't include the PR #140 branch which hasn't been merged yet (because it may bring regressions, so I want it to be tested before I merge it).

[miguno]

Ack.

I tested with the branch version:

$ cargo install --git https://github.com/Canop/bacon --rev 4d45699c5329db2ecb85ddcbbdf59829498901aa --force bacon

And here bacon test does work as expected, yay!