Public bug reported:
Issue found on Mantic since 6.5.0-11.11
Test failed with:
running attach_disconnected
Fatal Error (unix_fd_server): Unable to run test sub-executable
By hacking the tests/regression/apparmor/prologue.inc:
diff --git a/prologue.inc.orig b/prologue.inc
index 9da05f2..fafc244 100755
--- a/prologue.inc.orig
+++ b/prologue.inc
@@ -297,7 +297,9 @@ checktestfg()
{
# global _pfmode _known _testdesc outfile teststatus testname
local ret expectedsig killedsig
+ echo "==== $outfile ==="
ret=`cat $outfile 2>/dev/null`
+ echo "$ret"
teststatus=pass
case "$ret" in
Run tests/regression/apparmor/attach_disconnected.sh manually, you will
find the test is failing because the second test generates "PASS" twice
(it's not appending the result to the $outfile as we are using
"$testexec "$@" > $outfile 2>&1 &" in runtestfg():
$ sudo bash attach_disconnected.sh
==== /tmp/sdtest.345049-12729-P0mta1/output.unix_fd_server ===
PASS
==== /tmp/sdtest.345049-12729-P0mta1/output.unix_fd_server ===
PASS
PASS
Fatal Error (unix_fd_server): Unable to run test sub-executable
The $ret become 'PASS\nPASS' and consequently falls in the case of testerror:
*) testerror
return
;;
** Affects: qa-regression-testing
Importance: Undecided
Status: New
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Tags: 6.5 mantic sru-20240108 ubuntu-qrt-apparmor
** Also affects: qa-regression-testing
Importance: Undecided
Status: New
** Description changed:
Issue found on Mantic since 6.5.0-11.11
Test failed with:
- running attach_disconnected
- Fatal Error (unix_fd_server): Unable to run test sub-executable
+ running attach_disconnected
+ Fatal Error (unix_fd_server): Unable to run test sub-executable
By hacking the tests/regression/apparmor/prologue.inc:
diff --git a/prologue.inc.orig b/prologue.inc
index 9da05f2..fafc244 100755
--- a/prologue.inc.orig
+++ b/prologue.inc
@@ -297,7 +297,9 @@ checktestfg()
- {
- # global _pfmode _known _testdesc outfile teststatus testname
- local ret expectedsig killedsig
+ {
+ # global _pfmode _known _testdesc outfile teststatus testname
+ local ret expectedsig killedsig
+ echo "==== $outfile ==="
- ret=`cat $outfile 2>/dev/null`
+ ret=`cat $outfile 2>/dev/null`
+ echo "$ret"
- teststatus=pass
-
- case "$ret" in
+ teststatus=pass
+
+ case "$ret" in
Run tests/regression/apparmor/attach_disconnected.sh manually, you will
find the test is failing because the test result got appended to the
- $outfile:
+ $outfile when running the second test:
- $ sudo bash attach_disconnected.sh
+ $ sudo bash attach_disconnected.sh
==== /tmp/sdtest.345049-12729-P0mta1/output.unix_fd_server ===
PASS
==== /tmp/sdtest.345049-12729-P0mta1/output.unix_fd_server ===
PASS
PASS
Fatal Error (unix_fd_server): Unable to run test sub-executable
- And consequently falls in the case of testerror:
- *) testerror
- return
- ;;
+ The $ret become 'PASS\nPASS' and consequently falls in the case of testerror:
+ *) testerror
+ return
+ ;;
** Description changed:
Issue found on Mantic since 6.5.0-11.11
Test failed with:
running attach_disconnected
Fatal Error (unix_fd_server): Unable to run test sub-executable
By hacking the tests/regression/apparmor/prologue.inc:
diff --git a/prologue.inc.orig b/prologue.inc
index 9da05f2..fafc244 100755
--- a/prologue.inc.orig
+++ b/prologue.inc
@@ -297,7 +297,9 @@ checktestfg()
{
# global _pfmode _known _testdesc outfile teststatus testname
local ret expectedsig killedsig
+ echo "==== $outfile ==="
ret=`cat $outfile 2>/dev/null`
+ echo "$ret"
teststatus=pass
case "$ret" in
Run tests/regression/apparmor/attach_disconnected.sh manually, you will
- find the test is failing because the test result got appended to the
- $outfile when running the second test:
+ find the test is failing because the second test generates "PASS" twice
+ (it's not appending the result to the $outfile as we are using
+ "$testexec "$@" > $outfile 2>&1 &" in runtestfg():
$ sudo bash attach_disconnected.sh
==== /tmp/sdtest.345049-12729-P0mta1/output.unix_fd_server ===
PASS
==== /tmp/sdtest.345049-12729-P0mta1/output.unix_fd_server ===
PASS
PASS
Fatal Error (unix_fd_server): Unable to run test sub-executable
The $ret become 'PASS\nPASS' and consequently falls in the case of testerror:
*) testerror
return
;;
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2051932
Title:
attach_disconnected test from test_regression_testsuite of
ubuntu_qrt_apparmor failed with "Unable to run test sub-executable" on
Mantic
Status in QA Regression Testing:
New
Status in ubuntu-kernel-tests:
New
Bug description:
Issue found on Mantic since 6.5.0-11.11
Test failed with:
running attach_disconnected
Fatal Error (unix_fd_server): Unable to run test sub-executable
By hacking the tests/regression/apparmor/prologue.inc:
diff --git a/prologue.inc.orig b/prologue.inc
index 9da05f2..fafc244 100755
--- a/prologue.inc.orig
+++ b/prologue.inc
@@ -297,7 +297,9 @@ checktestfg()
{
# global _pfmode _known _testdesc outfile teststatus testname
local ret expectedsig killedsig
+ echo "==== $outfile ==="
ret=`cat $outfile 2>/dev/null`
+ echo "$ret"
teststatus=pass
case "$ret" in
Run tests/regression/apparmor/attach_disconnected.sh manually, you
will find the test is failing because the second test generates "PASS"
twice (it's not appending the result to the $outfile as we are using
"$testexec "$@" > $outfile 2>&1 &" in runtestfg():
$ sudo bash attach_disconnected.sh
==== /tmp/sdtest.345049-12729-P0mta1/output.unix_fd_server ===
PASS
==== /tmp/sdtest.345049-12729-P0mta1/output.unix_fd_server ===
PASS
PASS
Fatal Error (unix_fd_server): Unable to run test sub-executable
The $ret become 'PASS\nPASS' and consequently falls in the case of testerror:
*) testerror
return
;;
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/2051932/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
