Skip to contentSkip to conversation

tests: write f_badjour_encrypted output to log

PATCH Applied Andreas Dilger 2 participants 2 messages Jun 5, 2024 – Oct 25, 2024

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 tests: write f_badjour_encrypted output to log

Write the mke2fs and debugfs output from f_badjour_encrypted/script into a log file instead of stdout/stderr, so that it doesn't mess up the "make check" output, and is available if this test ever fails.

Fixes b0cd09e5 ("e2fsck: don't allow journal to have encrypt flag")
---
 tests/f_badjour_encrypted/script | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
tests/f_badjour_encrypted/script +3 -3
index e6778f1d..27b1026b 100644
@@ -3,9 +3,9 @@ if ! test -x $DEBUGFS_EXE; then
 	return 0
 fi
 
-touch $TMPFILE
-$MKE2FS -t ext4 -b 1024 $TMPFILE 2M
-$DEBUGFS -w -R 'set_inode_field <8> flags 0x80800' $TMPFILE
+touch $TMPFILE >> $LOG 2>&1
+$MKE2FS -t ext4 -b 1024 $TMPFILE 2M >> $LOG 2>&1
+$DEBUGFS -w -R 'set_inode_field <8> flags 0x80800' $TMPFILE >> $LOG 2>&1
 
 SKIP_GUNZIP="true"
 . $cmd_dir/run_e2fsck
Signature · 1 line
2.44.0
#1 lore raw
Quoted 5 lines · Andreas Dilger

Write the mke2fs and debugfs output from f_badjour_encrypted/script into a log file instead of stdout/stderr, so that it doesn't mess up the "make check" output, and is available if this test ever fails.

Applied, thanks!

[1/1] tests: write f_badjour_encrypted output to log

      commit: 5cf2c6b1df44e5ef145a5af8e6317ad87b190500

Best regards,

Signature · 1 line
Theodore Ts'o <[email protected]>