| Age | Commit message (Collapse) | Author |
|---|
|
This seems to work fine on ARC !
This reverts commit f0567d67075ff7a27ada8ab5bce750fe8a739763.
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
|
|
When ran on ARC, these tests would ocassionally fail
| [ARCLinux]# for i in 1 2 3 4 5 ; do ./tst-cancel2; echo $?; done
| write succeeded
| result is wrong: expected 0xffffffff, got 0x1
| 1 <-- fail
| 0 <-- pass
| 0 <--- pass
| 0 <-- pass
| write succeeded
| result is wrong: expected 0xffffffff, got 0x1
| 1 <-- fail
Same test (which originated form glibc) doesn't fail in glibc builds.
Turns out there's a subtle race in uclibc version
The test creates a new thread, makes it do a looong write call, and
parent then cancels the thread, expecting it to unwind out of write
call cleanly. However the write (even for 10k bytes) could finish
before parent gets a chance to resume and/or cancel it, causing the
occasional failure.
Fix this subtelty by making it write not just once but forever.
Cc: Cupertino Miranda <cmiranda@synopsys.com>
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
|
|
This reverts commit 1502f8269bb8e58f8b29fb69af3a3b8c7b2532de.
|
|
|
|
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
glibc, too
|
|
Disable some test for metag to allow runtime testing again.
Rename the big math meta-data files and do not install them.
Cris and Metag can be runtime tested again.
|
|
|
|
This is a first shot, more improvements required to
allow to run more tests.
|
|
|
|
|
