From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4517 invoked by alias); 9 Oct 2007 15:33:39 -0000 Received: (qmail 4439 invoked by uid 48); 9 Oct 2007 15:33:28 -0000 Date: Tue, 09 Oct 2007 15:33:00 -0000 From: "wcohen at redhat dot com" To: systemtap@sources.redhat.com Message-ID: <20071009153328.5150.wcohen@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug tapsets/5150] New: buildok/nfs-all-probes.stp fails X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2007-q4/txt/msg00096.txt.bz2 With the 2.6.23-rc9 kernel the probe points for some of the nfs.* nfs.*.* probes are available. Running /home/wcohen/stap_snap_200710081315/src/testsuite/buildok/nfs-all-probes.stp starting /home/wcohen/stap_snap_200710081315/src/testsuite/buildok/nfs-all-probes.stp spawn1 stap -p4 /home/wcohen/stap_snap_200710081315/src/testsuite/buildok/nfs-all-probes.stp semantic error: no match for probe point while resolving probe point nfs.fop.sendfile semantic error: no match for probe point while resolving probe point nfs.fop.sendfile semantic error: no match for probe point while resolving probe point nfs.fop.sendfile.return semantic error: no match for probe point while resolving probe point nfs.fop.sendfile.return semantic error: no match for probe point while resolving probe point nfs.proc3.commit semantic error: no match for probe point while resolving probe point nfs.proc3.commit semantic error: no match for probe point while resolving probe point nfs.proc4.commit semantic error: no match for probe point while resolving probe point nfs.proc4.commit semantic error: no match for probe point while resolving probe point nfs.proc2.read semantic error: no match for probe point while resolving probe point nfs.proc2.read semantic error: no match for probe point while resolving probe point nfs.proc3.read semantic error: no match for probe point while resolving probe point nfs.proc3.read semantic error: no match for probe point while resolving probe point nfs.proc4.read semantic error: no match for probe point while resolving probe point nfs.proc4.read semantic error: no match for probe point while resolving probe point nfs.proc.read semantic error: no match for probe point while resolving probe point nfs.proc.read semantic error: no match for probe point while resolving probe point nfs.proc2.write semantic error: no match for probe point while resolving probe point nfs.proc2.write semantic error: no match for probe point while resolving probe point nfs.proc3.write semantic error: no match for probe point while resolving probe point nfs.proc3.write semantic error: no match for probe point while resolving probe point nfs.proc4.write semantic error: no match for probe point while resolving probe point nfs.proc4.write semantic error: no match for probe point while resolving probe point nfs.proc.write semantic error: no match for probe point while resolving probe point nfs.proc.write semantic error: no match for probe point while resolving probe point nfs.proc.commit semantic error: no match for probe point while resolving probe point nfs.proc.commit semantic error: no match for probe point while resolving probe point nfs.proc2.read.return semantic error: no match for probe point while resolving probe point nfs.proc2.read.return semantic error: no match for probe point while resolving probe point nfs.proc3.read.return semantic error: no match for probe point while resolving probe point nfs.proc3.read.return semantic error: no match for probe point while resolving probe point nfs.proc4.read.return semantic error: no match for probe point while resolving probe point nfs.proc4.read.return semantic error: no match for probe point while resolving probe point nfs.proc.read.return semantic error: no match for probe point while resolving probe point nfs.proc.read.return semantic error: no match for probe point while resolving probe point nfs.proc2.write.return semantic error: no match for probe point while resolving probe point nfs.proc2.write.return semantic error: no match for probe point while resolving probe point nfs.proc3.write.return semantic error: no match for probe point while resolving probe point nfs.proc3.write.return semantic error: no match for probe point while resolving probe point nfs.proc4.write.return semantic error: no match for probe point while resolving probe point nfs.proc4.write.return semantic error: no match for probe point while resolving probe point nfs.proc.write.return semantic error: no match for probe point while resolving probe point nfs.proc.write.return semantic error: no match for probe point while resolving probe point nfs.proc3.commit.return semantic error: no match for probe point while resolving probe point nfs.proc3.commit.return semantic error: no match for probe point while resolving probe point nfs.proc4.commit.return semantic error: no match for probe point while resolving probe point nfs.proc4.commit.return semantic error: no match for probe point while resolving probe point nfs.proc.commit.return semantic error: no match for probe point while resolving probe point nfs.proc.commit.return Pass 2: analysis failed. Try again with more '-v' (verbose) options. Pass 2: analysis failed. Try again with more '-v' (verbose) options. wait results: 2766 exp15 0 1 FAIL: buildok/nfs-all-probes.stp -- Summary: buildok/nfs-all-probes.stp fails Product: systemtap Version: unspecified Status: NEW Severity: normal Priority: P2 Component: tapsets AssignedTo: systemtap at sources dot redhat dot com ReportedBy: wcohen at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=5150 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.