webdav/sync/go/pkg/mod/golang.org/x/tools@v0.21.1-0.20240531212143-b6235391adb3/cmd/bisect/testdata - 志元云盘

File OriginalPic	EditTime	Size
basic.txt	2024-08-14 10:33:57	1.76 KB
count2.txt	2024-08-14 10:33:57	2.82 KB
double.txt	2024-08-14 10:33:57	2.41 KB
max1.txt	2024-08-14 10:33:57	928 B
max2.txt	2024-08-14 10:33:57	2.64 KB
maxset.txt	2024-08-14 10:33:57	4.28 KB
maxset1.txt	2024-08-14 10:33:57	559 B
maxset4.txt	2024-08-14 10:33:57	7.71 KB
negate.txt	2024-08-14 10:33:57	2.45 KB
rand.txt	2024-08-14 10:33:57	2.55 KB
rand1.txt	2024-08-14 10:33:57	1021 B
rand2.txt	2024-08-14 10:33:57	782 B
README.md	2024-08-14 10:33:57	1.2 KB

This directory contains test inputs for the bisect command.

Each text file is a txtar archive (see <https://pkg.go.dev/golang.org/x/tools/txtar>
or `go doc txtar`).

The comment at the top of the archive is a JSON object describing a
target behavior. Specifically, the Fail key gives a boolean expression
that should provoke a failure. Bisect's job is to discover this
condition.

The Bisect key describes settings in the Bisect struct that we want to
change, to simulate the use of various command-line options.

The txtar archive files should be "stdout" and "stderr", giving the
expected standard output and standard error. If the bisect command
should exit with a non-zero status, the stderr in the archive will end
with the line "<bisect failed>".

Running `go test -update` will rewrite the stdout and stderr files in
each testdata archive to match the current state of the tool. This is
a useful command when the logging prints from bisect change or when
writing a new test.

To use `go test -update` to write a new test:

- Create a new .txt file with just a JSON object at the top,
   specifying what you want to test.
 - Run `go test -update`.
 - Reload the .txt file and read the stdout and stderr to see if you agree.

云盘

Home / 志元云盘 / webdav / sync / go / pkg / mod / golang.org / x / [email protected] / cmd / bisect / testdata