Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/ https://git.shady.money/coreutils/atom?h=v8.22 2013-12-05T00:27:11Z 2013-12-05T00:27:11Z Pádraig Brady P@draigBrady.com 2013-12-05T00:02:41Z urn:sha1:37e001d20930bacf188ab9725d063e205b195e34 This could trigger on SELinux systems where we build --qithout-selinux or where the SELinux development libraries are not installed. * init.cfg (require_selinux_enforcing_): Call require_selinux_() to determine if the current build supports SELinux. This avoids a false failure in tests/mkdir/selinux.sh where only mkdir would determine that SELinux was disabled and thus ignore invalid contexts. (require_selinux_): Refactor a little to distinguish whether it's the build or the (file) system that doesn't support SELinux. 2013-04-25T10:13:48Z Pádraig Brady P@draigBrady.com 2013-04-25T10:03:22Z urn:sha1:94f4f658f029f5d0083c6e8fab75d74b73ee5a33 * init.cfg (require_ulimit_v_): Renamed from require_ulimit_ as this only checks for ulimit -v support. Other uses of ulimit -t and ulimit -n in tests shouldn't cause false failures if not supported. * cfg.mk (sc_prohibit_test_ulimit_without_require_): A new syntax check to ensure that require_ulimit_v_() is used iff required. * tests/misc/head-c.sh: Add missing call to require_ulimit_v_. * tests/rm/many-dir-entries-vs-OOM.sh: Likewise. * tests/split/r-chunk.sh: Remove non mandatory require_ulimit_ call. * tests/misc/sort-merge-fdlimit.sh: Likewise. * tests/cp/link-heap.sh: Adjust to renamed require_ulimit_v_. * tests/dd/no-allocate.sh: Likewise. * tests/misc/csplit-heap.sh: Likewise. * tests/misc/cut-huge-to-eol-range.sh: Likewise. * tests/misc/printf-surprise.sh: Likewise. 2013-04-20T14:33:06Z Bernhard Voelker mail@bernhard-voelker.de 2013-04-20T14:33:06Z urn:sha1:d461bfd2743547360793acd2118d4c08ad7b84a8 The --retry option is indeed useful for both following modes by name and by file descriptor. The difference is that in the latter case, it is effective only during the initial open. As a regression of the implementation of the inotify support, tail -f --retry would immediately exit if the given file is inaccessible. * src/tail.c (usage): Change the description of the --retry option: remove the note that this option would mainly be useful when following by name. (main): Change diagnosing dubios uses of --retry option: when the --retry option is used without following, then issue a warning that this option is ignored; when it is used together with --follow=descriptor, then issue a warning that it is only effective for the initial open. Disable inotify also in the case when the initial open in tail_file() failed (which is the actual bug fix). * init.cfg (retry_delay_): Pass excess arguments to the test function. * tests/tail-2/retry.sh: Add new tests. * tests/local.mk (all_tests): Mention it. * doc/coreutils.texi (tail invocation): Enhance the documentation of the --retry option. Clarify the difference in tail's behavior regarding the --retry option when combined with the following modes name versus descriptor. * NEWS (Bug fixes): Mention the fix. Reported by Noel Morrison in: http://lists.gnu.org/archive/html/coreutils/2013-04/msg00003.html 2013-04-14T00:03:56Z Pádraig Brady P@draigBrady.com 2013-04-12T21:57:45Z urn:sha1:1dd8a33169b69716c4a4b92dbe1bd99336d92b23 On OS X it was seen that the group ID used for new files, are set to a that of the directory rather than the current user. It's not currently understood when this happens, but it was confirmed that ACLs, extended attributes and setgid bits are _not_ involved. * init.cfg (skip_if_nondefault_group_): A new function to detect and avoid this situation. Document with links to the discussions for hopefully future clarification. * tests/install/install-C-root.sh: Use the new function. * tests/install/install-C-selinux.sh: Likewise. * tests/install/install-C.sh: Likewise. 2013-04-04T02:02:10Z Pádraig Brady P@draigBrady.com 2013-03-27T12:51:43Z urn:sha1:e92d16f68a97575ed7112204b069514edc8d54a0 * init.cfg (require_gcc_shared_): A new function to check that we can build shared libraries in the particular manner we use in our tests. * tests/cp/nfs-removal-race.sh: Use require_gcc_shared_. Then fail rather than skip, if the actual shared lib build fails. * tests/df/no-mtab-status.sh: Likewise. * tests/df/skip-duplicates.sh: Likewise. * tests/ls/getxattr-speedup.sh: Likewise. Reported in http://bugs.gnu.org/14024 2013-01-01T03:51:20Z Jim Meyering jim@meyering.net 2013-01-01T02:54:51Z urn:sha1:77da73c75432f3c5b4beebae7b0797a1e33160bc Run "make update-copyright", but then also run this, perl -pi -e 's/2\d\d\d-//' tests/sample-test to make that one script use the single most recent year number. 2012-12-21T15:57:25Z Pádraig Brady P@draigBrady.com 2012-12-20T00:09:15Z urn:sha1:dd44ccef0da458b682bcb6b866aac1460a5b50a1 * init.cfg (require_valgrind_): Check the `true` program, which will check more valgrind failure cases as now detailed in the function comments. 2012-11-01T17:37:58Z Bernhard Voelker mail@bernhard-voelker.de 2012-11-01T15:50:51Z urn:sha1:ad5eeacc6740fd98ebe641b6fa88ec4019295b4e An invalid sed expression lead to the following error: + sed -n 'ls/.* //p' sed: -e expression #1, char 2: extra characters after command Use "one" instead of "el". Bug introduced in v8.19-111-g51a4b04. * init.cfg (setuidgid_has_perm_): s/ls/1s/. * NEWS (Build-related): Mention the fix. 2012-09-07T09:03:24Z Jim Meyering meyering@redhat.com 2012-09-06T10:00:16Z urn:sha1:51a4b04954ad5ad12de1d1b82a3603fc350a3bfa * init.cfg (setuidgid_has_perm_): New function. (require_root_): Use it. Improved-by: Bernhard Voelker * NEWS (Build-related): Mention the improvement. 2012-09-05T06:48:29Z Stefano Lattarini stefano.lattarini@gmail.com 2012-09-02T19:55:18Z urn:sha1:303d0743570681237d4e688043be45cebd2db519 * tests/init.cfg (stty_reversible_init_): Quote '$abs_top_srcdir' properly. (fiemap_capable_): Quote '$abs_srcdir' properly. (require_dirent_d_type_): Likewise.