This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: S390x - REL5 stap_testing_200611132049.results]


David Wilder wrote:
David Smith wrote:

David Wilder wrote:

A number of new errors popped up today when testing on the s390x. The new failures were:

FAIL: BASIC2 wasn't cached
FAIL: OPTION2 wasn't cached
FAIL: RUNTIME2 wasn't cached
FAIL: BASIC4 wasn't cached

I have not investigated the cause yet.


Hmm, those are all related to the caching functionality/tests that I wrote. This could be a expect buffering problem. Can I see the full log for BASIC2?

I included the full test log. Let me know if you need something else.

Here's the start of the cache.exp output:


------------------------------------------------------------------------
Running /home/testing/test_dir/stap_testing_redhat-release_200611132049/src/testsuite/systemtap.base/cache.exp ...
Pass 1: parsed user script and PASS: BASIC1 wasn't cached
Pass 1: parsed user script and 52 library script(s) in 5730usr/90sys/8488real ms.
Pass 2: analyzed script: 1 probe(s), 0 function(s), 0 embed(s), 0 global(s) in 90usr/0sys/143real ms.
Pass 3: translated to C into "/tmp/stapm04SSl/stap_068fff0329d56e3f18c39099d7f15ca8_184.c" in 0usr/0sys/2real ms.
FAIL: BASIC2 wasn't cached
Pass 1: parsed user script and 52 library script(s) in 5710usr/100sys/8399real ms.
Pass 2: analyzed script: 1 probe(s), 0 function(s), 0 embed(s), 0 global(s) in 90usr/0sys/133real ms.
Pass 3: translated to C into "/tmp/stapQXFRli/stap_649b328956d15729d5a17b8e8ec98b64_189.c" in 0usr/0sys/1real ms.
PASS: OPTION1 wasn't cached

Something *really* strange is going on there. The above output (and the part that I cut out) shows that stap didn't do pass 4 for any of the cache tests. That's really odd, since "stap -p4" is hardcoded in that test.


Can you run the following command *twice* and send me the output?

# stap -v -p4 -e "probe begin {}"

The output should look something like:

---------------
# stap -v -p4 -e "probe begin {}"
Pass 1: parsed user script and 53 library script(s) in 140usr/10sys/165real ms.
Pass 2: analyzed script: 1 probe(s), 0 function(s), 0 embed(s), 0 global(s) in 10usr/10sys/3real ms.
Pass 3: translated to C into "/tmp/stapGSMvEZ/stap_7a5fe045c67645c83d0df1d327d2de1c_122.c" in 0usr/0sys/0real ms.
Pass 4: compiled C into "stap_7a5fe045c67645c83d0df1d327d2de1c_122.ko" in 880usr/140sys/2566real ms.
# stap -v -p4 -e "probe begin {}"
Pass 1: parsed user script and 53 library script(s) in 140usr/20sys/490real ms.
Pass 2: analyzed script: 1 probe(s), 0 function(s), 0 embed(s), 0 global(s) in 10usr/0sys/3real ms.
Pass 3: using cached /home/dsmith/.systemtap/cache/7a/stap_7a5fe045c67645c83d0df1d327d2de1c_122.c
Pass 4: using cached /home/dsmith/.systemtap/cache/7a/stap_7a5fe045c67645c83d0df1d327d2de1c_122.ko
---------------


--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]