Skip to contentSkip to conversation

Revert "oeqa/runtime/stap: increase buffer size"

PATCH In review Ross Burton 2 participants 4 messages Jan 24, 2022 – Jan 25, 2022

lore
Share & tools
lore
#0 lore raw

PATCH 1/2 Revert "oeqa/runtime/stap: increase buffer size"

The failures appear to be OOMs during the compile phase, so the buffer size isn't (yet) relevant.

If the buffer size is a problem, SystemTap commit 3106bc65 would be a better fix.

This reverts commit 674fd536bc1c2308d557652ae100b1a1eee103b9.

---
 meta/lib/oeqa/runtime/cases/stap.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/lib/oeqa/runtime/cases/stap.py +1 -1
index 615c290ce61..ac0125edb2b 100644
@@ -18,7 +18,7 @@ class StapTest(OERuntimeTestCase):
         status, output = self.target.run(cmd, 900)
         self.assertEqual(status, 0, msg='\n'.join([cmd, output]))
 
-        cmd = 'stap -v --disable-cache -DSTP_NO_VERREL_CHECK -s1 -e \'probe oneshot { print("Hello, "); println("world!") }\''
+        cmd = 'stap -v --disable-cache -DSTP_NO_VERREL_CHECK -e \'probe oneshot { print("Hello, "); println("world!") }\''
         status, output = self.target.run(cmd, 900)
         self.assertEqual(status, 0, msg='\n'.join([cmd, output]))
         self.assertIn('Hello, world!', output, msg='\n'.join([cmd, output]))
Signature · 1 line
2.25.1
#1 lore raw

PATCH 2/2 core-image-sato-sdk: allocate more memory when in qemu

Compiling code is memory-intensive, especially kernel modules like the SystemTap probes, so give the VM 1GB of RAM.

Hopefully this solves the intermittent failures caused by OOMs during the SystemTap test.

[ YOCTO #14673 ]

---
 meta/recipes-sato/images/core-image-sato-sdk.bb | 3 +++
 1 file changed, 3 insertions(+)
meta/recipes-sato/images/core-image-sato-sdk.bb +3 -0
index b52de0def02..7df8d00971c 100644
@@ -10,3 +10,6 @@ IMAGE_FEATURES += "dev-pkgs tools-sdk \
 
 IMAGE_INSTALL += "kernel-devsrc"
 
+# Compiling stuff, specifically SystemTap probes, can require lots of memory
+# See https://bugzilla.yoctoproject.org/show_bug.cgi?id=14673
+QB_MEM = '-m 1024'
Signature · 1 line
2.25.1
#2 lore raw

Re: [OE-core] [PATCH 2/2] core-image-sato-sdk: allocate more memory when in qemu

Seems to not work on arm(32):

Central error: [ 5.282955] vmap allocation for size 1052672 failed:
use vmalloc=<size> to increase size

https://autobuilder.yoctoproject.org/typhoon/#/builders/110/builds/3528/steps/13/logs/stdio

Alex

Quoted 41 lines · Ross Burton

Compiling code is memory-intensive, especially kernel modules like the SystemTap probes, so give the VM 1GB of RAM.

Hopefully this solves the intermittent failures caused by OOMs during the SystemTap test.

[ YOCTO #14673 ]

---
 meta/recipes-sato/images/core-image-sato-sdk.bb | 3 +++
 1 file changed, 3 insertions(+)
meta/recipes-sato/images/core-image-sato-sdk.bb +1 -0
index b52de0def02..7df8d00971c 100644
@@ -10,3 +10,6 @@ IMAGE_FEATURES += "dev-pkgs tools-sdk \
 
 IMAGE_INSTALL += "kernel-devsrc"
 
+# Compiling stuff, specifically SystemTap probes, can require lots of

memory

meta/recipes-sato/images/core-image-sato-sdk.bb +2 -1
+# See https://bugzilla.yoctoproject.org/show_bug.cgi?id=14673
+QB_MEM = '-m 1024'
--

2.25.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#160890):
https://lists.openembedded.org/g/openembedded-core/message/160890
Mute This Topic: https://lists.openembedded.org/mt/88653349/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#3 lore raw

Re: [OE-core] [PATCH 2/2] core-image-sato-sdk: allocate more memory when in qemu

qemuarm shows something different:
https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/4653/steps/13/logs/stdio

Alex

Quoted 52 lines · Alexander Kanavin

Seems to not work on arm(32):

Central error: [ 5.282955] vmap allocation for size 1052672 failed: use vmalloc=<size> to increase size

https://autobuilder.yoctoproject.org/typhoon/#/builders/110/builds/3528/steps/13/logs/stdio

Alex

Quoted 41 lines · Ross Burton

Compiling code is memory-intensive, especially kernel modules like the SystemTap probes, so give the VM 1GB of RAM.

Hopefully this solves the intermittent failures caused by OOMs during the SystemTap test.

[ YOCTO #14673 ]

---
 meta/recipes-sato/images/core-image-sato-sdk.bb | 3 +++
 1 file changed, 3 insertions(+)
meta/recipes-sato/images/core-image-sato-sdk.bb +1 -0
index b52de0def02..7df8d00971c 100644
@@ -10,3 +10,6 @@ IMAGE_FEATURES += "dev-pkgs tools-sdk \
 
 IMAGE_INSTALL += "kernel-devsrc"
 
+# Compiling stuff, specifically SystemTap probes, can require lots of

memory

meta/recipes-sato/images/core-image-sato-sdk.bb +2 -1
+# See https://bugzilla.yoctoproject.org/show_bug.cgi?id=14673
+QB_MEM = '-m 1024'
--

2.25.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#160890):
https://lists.openembedded.org/g/openembedded-core/message/160890
Mute This Topic: https://lists.openembedded.org/mt/88653349/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-