Bug 27730

Summary:	abort.exp minor regressions (from bunsen data)
Product:	systemtap	Reporter:	Serhei Makarov <serhei>
Component:	testsuite	Assignee:	Unassigned <systemtap>
Status:	RESOLVED FIXED
Severity:	normal	CC:	scox
Priority:	P2
Version:	unspecified
Target Milestone:	---
Host:		Target:
Build:		Last reconfirmed:

Description Serhei Makarov 2021-04-13 21:03:02 UTC

Analysis of the buildbot data shows the following regressions:

abort.exp failures after several commits

executing: stap '/notnfs/smakarov/stap-checkout/testsuite/systemtap.base/abort_6.stp'
FAIL: abort: TEST 6: abort() in timer.profile (using globals): stdout: string should be "fire 3!\nfire 2!\nfire 1!\n", but got "fire 1!
fire 3!
fire 2!
"

7187dcf runtime: fix print races in IRQ context and during print cleanup
(or sometime shortly prior)
- f31, f32, f33, f34, f30 i686, rhel7

d235f70 Support pointer_arg in dyninst mode
- other configurations esp. rhel8

This seems like a minor testsuite-quality issue rather than being related to the commits in question.

Comment 1 Serhei Makarov 2021-04-13 21:36:09 UTC

(not a dyninst problem)

Comment 2 Stan Cox 2022-05-26 19:12:50 UTC

abort.exp is now okay on rhel8, rhel9, f35