On Mon, Feb 04, Andrew Josey wrote:
> hi Thorsten
>
> The main problem with test result resolution right now is that no one has it
> as their day job to resolve these:-( A little help below, then
> back to the day job...
Ok, and here is the fix for readv_L 28 and writev_L 30. This should be
added for the next version of the LSB.os test suite release.
--- ioprim/readv_L/readv_L.c
+++ ioprim/readv_L/readv_L.c 2002/02/04 16:16:12
@@ -2396,6 +2396,8 @@
DBUG_ENTER("ch_t24");
+ testfail = 0;
+
/*
** if there are IOV_MAX iovectors and each iov_len is onebuf bytes,
** then the sum of all the iov_len values will "overflow a ssize_t"
--- ioprim/writev_L/writev_L.c
+++ ioprim/writev_L/writev_L.c 2002/02/04 16:17:28
@@ -3345,7 +3345,7 @@
(void) unlink(t30_path);
if (testfail == 0)
- PATH_XS_RPT(4);
+ PATH_XS_RPT(3);
DBUG_VOID_RETURN;
}
--
Thorsten Kukuk http://www.suse.de/~kukuk/ [EMAIL PROTECTED]
SuSE GmbH Deutschherrenstr. 15-19 D-90429 Nuernberg
--------------------------------------------------------------------
Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
