Re: [PATCH v3 12/12] tests: f_bad_fname: Test fixes of invalid filenames and duplicates

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Dec 17, 2020 at 06:35:44PM +0100, Arnaud Ferraris wrote:
> From: Gabriel Krisman Bertazi <krisman@xxxxxxxxxxxxx>
> 
> Signed-off-by: Gabriel Krisman Bertazi <krisman@xxxxxxxxxxxxx>
> Signed-off-by: Arnaud Ferraris <arnaud.ferraris@xxxxxxxxxxxxx>

It looks like you didn't regenerate the expect.1 file after changing
the problem description.

% cat f_bad_fname.failed 
--- /usr/projects/e2fsprogs/e2fsprogs/tests/f_bad_fname/expect.1	2021-01-28 03:20:36.813595045 +0000
+++ f_bad_fname.1.log	2021-01-28 03:25:49.940137813 +0000
@@ -1,9 +1,9 @@
 Pass 1: Checking inodes, blocks, and sizes
 Pass 2: Checking directory structure
-Entry 'AM-^?' in /ci_dir (12) has illegal characters in its name.
+Entry 'AM-^?' in /ci_dir (12) has illegal UTF-8 characters in its name.
 Fix? yes
 
-Entry 'AM-~' in /ci_dir (12) has illegal characters in its name.
+Entry 'AM-~' in /ci_dir (12) has illegal UTF-8 characters in its name.
 Fix? yes
 
 Duplicate entry 'A.' found.

I'll fix this up in my tree.

     	           	      	       - Ted



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux