8000 split produces one million lines of error messages in the GNU test suite · Issue #4073 · uutils/coreutils · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

split produces one million lines of error messages in the GNU test suite #4073

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.

Sign up for GitHub

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

Jump to bottom
Closed
jfinkels opened this issue Oct 23, 2022 · 5 comments · Fixed by #4315
Closed

split produces one million lines of error messages in the GNU test suite #4073

jfinkels opened this issue Oct 23, 2022 · 5 comments · Fixed by #4315
Labels
good first issue For newcomers! U - split

Comments

@jfinkels
Copy link
Collaborator

The tests/split/filter.sh test is still producing about one million lines of shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory. So, maybe we should skip that part of the test for the moment? I believe it is this part:

# Ensure that "endless" input _is_ processed for unbounded number of filters    
for buf in 1000 1000000; do
  returns_ 124 timeout .5 sh -c \
    "yes | split --filter='head -c1 >/dev/null' -b $buf" || fail=1
done

Originally posted by @jfinkels in #3281 (comment)
@sylvestre
Copy link
Contributor

or do &> /dev/null to redirect stderr too :)

@sylvestre sylvestre added the good first issue For newcomers! label Oct 23, 2022
@jfinkels
Copy link
Collaborator Author

I believe this issue also causes this occasional failure:

GNU test failed: tests/misc/timeout. tests/misc/timeout is passing on 'main'. Maybe you have to rebase?

@jfinkels jfinkels mentioned this issue Nov 11, 2022
Open
@tertsdiepraam
Copy link
Member

Both options seem good to me. In the meantime, do we have any idea what's causing this? Seems like the working directory does not exist. How would something like that happen?

@miles170 miles170 mentioned this issue Nov 22, 2022
Closed
@miles170 miles170 mentioned this issue Mar 15, 2023
Merged
@tertsdiepraam
Copy link
Member

I think @miles170 was right about this being fixed by #4315. Let's hope the timeout test is also no longer intermittent.

@jfinkels
Copy link
Collaborator Author

Excellent work @miles170, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue For newcomers! U - split
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

timeout: fix subprocess is never terminated miles170/coreutils
3 participants
@jfinkels @sylvestre @tertsdiepraam
0