rclone / rclone/rclone

bisync: the tests are too noisy

Open
#7,736 2 comments 0 reactions 1 assignee View on GitHub

@nielash is already working on this.

Since Apr 6, 2024.

bisync build test issue
Dominant language
Go
Stars
59.8k
Forks
5.4k
Avg merge
2d 14h
Merged PRs (30d)
48

Description

The bisync tests are too noisy.

rclone/rclone/cmd/bisync$ go test 2>&1 | wc -l
5527

When they go wrong in CI it is almost impossible to figure out what went wrong, eg https://github.com/rclone/rclone/actions/runs/8572078457/job/23493782434 - this is partly due to the hard to use web page which involves lots of scrolling within windows, but I think we can do better.

Ideally I'd like the tests to print nothing by default, except actual test failures. If we want to see more info then there is the -verbose flag (fstest.Verbose) which by default enables DEBUG logging, but in bisync's case you can use it to print as much stuff as you want.

What do you think @nielash ?

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.