Bruno Haible wrote:
> Hi Eric,
>
>> > -ASSERT (errno == EINVAL || errno == EBUSY);
>> > +ASSERT (errno == EINVAL || errno == EBUSY || errno == EEXIST);
>
>> The patch to relax the testsuite looks okay to me; we're already
>> allowing other non-standard errno values here, so no one h
Hi Eric,
> > -ASSERT (errno == EINVAL || errno == EBUSY);
> > +ASSERT (errno == EINVAL || errno == EBUSY || errno == EEXIST);
> The patch to relax the testsuite looks okay to me; we're already
> allowing other non-standard errno values here, so no one has complained
> about it cau
On OSF/1 5.1, I get these test failures:
test-rename.h:342: assertion failed
sh: 366977 Abort - core dumped
FAIL: test-rename
test-rename.h:342: assertion failed
sh: 366978 Abort - core dumped
FAIL: test-renameat
The reason are different errno values. The following patch fixes it for me.
OK to c
On 12/22/2010 08:31 AM, Bruno Haible wrote:
> On OSF/1 5.1, I get these test failures:
>
> test-rename.h:342: assertion failed
> sh: 366977 Abort - core dumped
> FAIL: test-rename
>
> test-rename.h:342: assertion failed
> sh: 366978 Abort - core dumped
> FAIL: test-renameat
>
> The reason are di
