[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: test fails: mount -o
From:       haroon maqsood <maqsood3525 () live ! com>
Date:       2018-10-21 10:56:21
Message-ID: VI1PR04MB5294D0368340A16058C60028C8FB0 () VI1PR04MB5294 ! eurprd04 ! prod ! outlook ! com
[Download RAW message or body]

On Sun, Oct 21, 2018 at 01:25:57AM +0000, haroon maqsood wrote:
> On Sun, Oct 21, 2018 at 01:22:20AM +0000, haroon maqsood wrote:
> > On Mon, Oct 01, 2018 at 12:37:06PM +0530, Nikita Gupta wrote:
> > > Hi team,
> > > 
> > > While executing the testsuite included with the busybox-1.24.1, I got few
> > > failures.
> > > *Failed test case list*
> > > cpio lists hardlinks
> > > mount -o remount,mand
> > > sed n (flushes pattern space, terminates early)
> > > sed embedded NUL
> > > sed NUL in command
> > > sed append autoinserts newline
> > > sed nonexistent label
> > > unzip (subdir only)
> > > 
> > > Out of the above list, I could figureout the failing reasons of the test
> > > cases but one "mount -o remount,mand" is failing whose failure reason is
> > > unpredictable.
> > > 
> > > If the failing reason can't be figuredout, then how one can resolve it.
> > > 
> > > Failure logs:
> > > 
> > > echo -ne '' >input
> > > echo -ne '' | mount -o loop mount.image1m
> > > /packages/busybox-1.24.1/testsuite/mount.testdir && grep -Fc
> > > /packages/busybox-1.24.1/testsuite/mount.testdir </proc/mounts && mount -o
> > > remount,mand /packages/busybox-1.24.1/testsuite/mount.testdir && grep -F
> > > /packages/busybox-1.24.1/testsuite/mount.testdir </proc/mounts | grep -c
> > > '[, ]mand[, ]'|| grep -F /packages/busybox-1.24.1/testsuite/mount.testdir
> > > </proc/mounts
> > > mount: mounting /dev/loop0 on
> > > /packages/busybox-1.24.1/testsuite/mount.testdir failed: Invalid argument
> > > FAIL: mount -o remount,mand
> > > --- expected
> > > +++ actual
> > > @@ -1,2 +0,0 @@
> > > -1
> > > -1
> > > umount: can't unmount /packages/busybox-1.24.1/testsuite/mount.testdir:
> > > Invalid argument
> > > 
> > > Can somebody help me in figuring out the failure reason for "mount -o
> > > remount,mand" testcase?
> > > -- 
> > > Regards,
> > > Nikita Gupta
> > 
> > > _______________________________________________
> > > busybox mailing list
> > > busybox@busybox.net
> > > http://lists.busybox.net/mailman/listinfo/busybox
> > Hi,
> > can you please share the architecture, kernel and gcc and the libc and libc 
> > version you compiled and ran these tests on, i have tried on 
> > 4.15.0-36-generic #39-Ubuntu SMP x86_64 x86_64 and i dont seem to be able to 
> > reproduce the issue, and even if i try manually.
> > on the other hand, is there a chance that you ran the tests as a non root
> > user first and then ran the tests as sudo again and you saw these failures ?
> > Thanks
> > Haroon
> > _______________________________________________
> > busybox mailing list
> > busybox@busybox.net
> > http://lists.busybox.net/mailman/listinfo/busybox
> Hi,
> i should have mentioned the glibc version, it is 2.27 , and i am talking
> about the mount -o remount,mand test failures
> _______________________________________________
> busybox mailing list
> busybox@busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox

after a bit of playing around with the test script.
the issue you faced i.e ""*wrong
fs type, bad option, bad superblock on /dev/loop0, missing codepage or
helper program, or other error*".
And executing the runtest of busybox-testsuite gives error as "*mounting
/dev/loop0 on /packages/busybox-1.24.1/testsuite/mount.testdir failed:
Invalid argument*""

is because you did not run ./busybox mkfs.minix -v mount.image1m on the image
file, see mount.tests line number 25
Thanks
Haroon
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]