posix filesystem call test suite based on pjdfstest

[sequix]

#101 covers performance test, this PR covers posix calls with (pjd/pjdfstest)[https://github.com/pjd/pjdfstest]. It uses perl TAP-Harness to mock posix calls and its test case is written in script like.

desc="rename returns ENAMETOOLONG if a component of either pathname exceeded {NAME_MAX} characters"

dir=`dirname $0`
. ${dir}/../misc.sh

echo "1..8"

n0=`namegen`
nx=`namegen_max`
nxx="${nx}x"

expect 0 create ${nx} 0644
expect 0 rename ${nx} ${n0}
expect 0 rename ${n0} ${nx}
expect 0 unlink ${nx}

expect 0 create ${n0} 0644
expect ENAMETOOLONG rename ${n0} ${nxx}
expect 0 unlink ${n0}
expect ENAMETOOLONG rename ${nxx} ${n0}

You can see this will create files on the rw layer, but I still got some errors, At first I thought this is about the container environment, but the errors disappear when I switched to oci image.

Test Summary Report
-------------------
/work/pjdfstest/tests/chmod/02.t          (Wstat: 0 Tests: 5 Failed: 1)
  Failed test:  5
/work/pjdfstest/tests/chown/02.t          (Wstat: 0 Tests: 10 Failed: 2)
  Failed tests:  5, 10
/work/pjdfstest/tests/ftruncate/02.t      (Wstat: 0 Tests: 5 Failed: 1)
  Failed test:  5
/work/pjdfstest/tests/link/02.t           (Wstat: 0 Tests: 10 Failed: 1)
  Failed test:  10
/work/pjdfstest/tests/mknod/02.t          (Wstat: 0 Tests: 12 Failed: 1)
  Failed test:  12
/work/pjdfstest/tests/rename/01.t         (Wstat: 0 Tests: 8 Failed: 1)
  Failed test:  8
/work/pjdfstest/tests/rmdir/02.t          (Wstat: 0 Tests: 4 Failed: 1)
  Failed test:  4
/work/pjdfstest/tests/truncate/02.t       (Wstat: 0 Tests: 5 Failed: 1)
  Failed test:  5
/work/pjdfstest/tests/unlink/02.t         (Wstat: 0 Tests: 4 Failed: 1)
  Failed test:  4
Files=235, Tests=8813, 220 wallclock secs ( 2.12 usr  0.60 sys + 25.95 cusr 36.24 csys = 64.91 CPU)
Result: FAIL

Interpretation of above log:

/work/pjdfstest/tests/chown/02.t          (Wstat: 0 Tests: 10 Failed: 2)
  Failed tests:  5, 10

Correspond to the 5th and 10th expect statement of file https://github.com/pjd/pjdfstest/blob/master/tests/chown/02.t. After exmaine all failed tests, they all expect ENAMETOOLONG.

Maybe later we can build tests in ro layer based on this.

[fuweid]

@sequix please sign off thanks

[sequix]

@sequix please sign off thanks

signed

[ktock]

Thanks for this! How do you think about ltp(Linux Test Project)?

[ktock]

Do we need them?

[ktock]

I mean apt-transport-https gnupg2 software-properties-common.

[ktock]

I'll also upload it when we merge it.

[ktock]

We should propagate the exit code to the caller scripts (test.sh) so that Github Actions can know the success/failure of this test.

[fuweid]

@sequix thanks! but we need your real name :P

[sequix]

Thanks for this! How do you think about ltp(Linux Test Project)?

Looks like the ltp community is pretty active, not like pjdfstest. I will git ltp a try.

[AkihiroSuda]

Is this still on plan?