Bug 27730 - abort.exp minor regressions (from bunsen data)
Summary: abort.exp minor regressions (from bunsen data)
Status: RESOLVED FIXED
Alias: None
Product: systemtap
Classification: Unclassified
Component: testsuite (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-13 21:03 UTC by Serhei Makarov
Modified: 2022-05-26 19:12 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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