forked from uutils/coreutils
-
Notifications
You must be signed in to change notification settings - Fork 0
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
update #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now that clap#2624 has been resolved, we can and should test both variants.
See also 9995c63. There is a race condition between the writing thread and the command. It is easily possible that on the developer's machine, the writing thread is always faster, filling the kernel's buffer of the stdin pipe, thus succeeding the write. It is also easily possible that on the busy CI machines, the child command runs first for whatever reason, and exits early, thus killing the pipe, which causes the later write to fail. This results in a flaky test. Let's prevent flaky tests.
chore(deps): update rust crate rayon to 1.9
tests: Harden two tests, prevent 4 flaky tests (cat, numfmt, sort, split, tee)
…ile_busy_error Android CI: workaround: run builds with retry
cargo: fix feature = "cargo-clippy" deprecation
printf: Make printf operate on bytes instead of strings
…ed with '%0c' or '%0s'
printf: '%0c' and '%0s' should fail
…teractive_update cp: fix flaky test test_cp_arg_interactive_update, document adjacent bug
…l_utility test utilities: easy way to simulate terminal context
ci: use codecov token in CICD/GnuTests workflows
Bump chrono to 0.4.35 & replace usage of deprecated functions
* Add tests that stat symlinks * Check follow first in stat * Don't run tests on FreeBSD It would be possible to get them to run on FreeBSD by avoiding get_symlink_times, but the behavior we're testing is not platform-specific, so it's fine to not test it on FreeBSD. --------- Co-authored-by: Sylvestre Ledru <sylvestre@debian.org>
dd : treat arg as bytes if it contains a 'B'
Fix clippy warnings
pr/chgrp: fix warnings
chcon: Handle repeated flags and overrides between --no-XXX and --XXX
tr: Stream output instead of buffering
…by-one shuf: Fix off-by-one errors in range handling
* cp: improve the support of --attributes-only * remove useless comments Co-authored-by: Daniel Hofstetter <daniel.hofstetter@42dh.com> --------- Co-authored-by: Daniel Hofstetter <daniel.hofstetter@42dh.com>
cp: Split the copy_file function a bit
This solves uutils#5584, where the fuzzing would take hours without this.
parser: if closing square bracket not found, stop looking for it again
also remove some FixMEs for FreeBsd
…_at_destination Fix install: invalid link at destination
nix 0.28 changed the return type of unistd::pipe() from Result<(RawFd, RawFd), Error> to Result<(OwnedFd, OwnedFd), Error>
change introduced by nix 0.28
flag was removed from nix::sys::termios::OutputFlags in nix 0.28
nix 0.28 changed "write(fd: RawFd, buf: &[u8]) -> Result<usize>" to "write<Fd: AsFd>(fd: Fd, buf: &[u8]) -> Result<usize>"
Bump nix from 0.27 to 0.28 & fix issues due to API changes
chore(deps): update rust crate blake3 to 1.5.1
GNU testsuite comparison:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
update