Skip to contentSkip to conversation

syscalls: semop: Increase timeout for semop03

PATCH New Viresh Kumar 3 participants 3 messages Oct 7, 2020 – Oct 9, 2020

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 syscalls: semop: Increase timeout for semop03

Sometimes the timeout happens before the signal is received and it causes the test to fail with following error:

semop03.c:55: TFAIL: unexpected failure: EAGAIN/EWOULDBLOCK (11)

Fix this by increasing the timeout to a sufficiently large value.

---
 testcases/kernel/syscalls/ipc/semop/semop03.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
testcases/kernel/syscalls/ipc/semop/semop03.c +1 -1
index 89603f19d651..3a79ed38a904 100644
@@ -71,7 +71,7 @@ static void setup(void)
 	semop_supported_by_kernel(tv);
 
 	timeout.type = tv->ts_type;
-	tst_ts_set_sec(&timeout, 0);
+	tst_ts_set_sec(&timeout, 2);
 	tst_ts_set_nsec(&timeout, 10000000);
 
 	SAFE_SIGNAL(SIGHUP, sighandler);
Signature · 1 line
2.25.0.rc1.19.g042ed3e048af
#1 lore raw

PATCH 1/1 syscalls: semop: Increase timeout for semop03

----- Original Message -----

Quoted 28 lines

Sometimes the timeout happens before the signal is received and it causes the test to fail with following error:

semop03.c:55: TFAIL: unexpected failure: EAGAIN/EWOULDBLOCK (11)

Fix this by increasing the timeout to a sufficiently large value.

---
 testcases/kernel/syscalls/ipc/semop/semop03.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
testcases/kernel/syscalls/ipc/semop/semop03.c +1 -2
index 89603f19d651..3a79ed38a904 100644
@@ -71,7 +71,7 @@ static void setup(void)
 	semop_supported_by_kernel(tv);
 
 	timeout.type = tv->ts_type;
-	tst_ts_set_sec(&timeout, 0);
+	tst_ts_set_sec(&timeout, 2);
 	tst_ts_set_nsec(&timeout, 10000000);
 
 	SAFE_SIGNAL(SIGHUP, sighandler);
--
Quoted 1 line

2.25.0.rc1.19.g042ed3e048af

pointer to arm thread:
https://lore.kernel.org/linux-arm-kernel/20201007053345.4xbyjx4u4ccwkep5@vireshk-i7/T/#t

I see it sporadically on ppc kvm guests too.

#2 lore raw

PATCH 1/1 syscalls: semop: Increase timeout for semop03

Quoted 29 lines · Jan Stancek

----- Original Message -----

Quoted 26 lines

Sometimes the timeout happens before the signal is received and it causes the test to fail with following error:

semop03.c:55: TFAIL: unexpected failure: EAGAIN/EWOULDBLOCK (11)

Fix this by increasing the timeout to a sufficiently large value.

---
 testcases/kernel/syscalls/ipc/semop/semop03.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
testcases/kernel/syscalls/ipc/semop/semop03.c +1 -1
index 89603f19d651..3a79ed38a904 100644
@@ -71,7 +71,7 @@ static void setup(void)
      semop_supported_by_kernel(tv);
 
      timeout.type = tv->ts_type;
-     tst_ts_set_sec(&timeout, 0);
+     tst_ts_set_sec(&timeout, 2);
      tst_ts_set_nsec(&timeout, 10000000);
 
Quoted 6 lines
Quoted 3 lines
testcases/kernel/syscalls/ipc/semop/semop03.c +0 -1
      SAFE_SIGNAL(SIGHUP, sighandler);
--

2.25.0.rc1.19.g042ed3e048af

Patch applied.

Signature · 5 lines
Regards,
Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20201009/9fac53d4/attachment.htm>