Make captured stdout and stderr available within the subunit stream

Bug #1012171 reported by Gary Poster on 2012-06-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Brad Crittenden

Bug Description

With the planned change from the fix to bug 996729 in place, we (will) have no access to the stdout and stderr in test runs on buildbot (or anywhere subunit is used). As a next step, we should make it available. I propose that these should be reported as faux tests, just like we do with layer information. Add tags (one for stdout and one for stderr) that we can filter on.

Since this will presumably be done by the yellow squad in support of the parallel tests, please also fix lpbuildbot to filter out these from the test count *and* include new logs of just this output, so people can easily look at them. Nice to have: the name of the worker that generated the stdout or stderr output. Nice to have: anytime stdout or stderr is generated, the log also writes the name of the test that is listed for that worker that is run immediately after any stdout or stderr output. If you'd like to make a separate bug/card for this, great. If it is easy and you want to combine them, that's fine too.

Related branches

Gary Poster (gary) on 2012-06-12
description: updated
Brad Crittenden (bac) on 2012-06-15
Changed in launchpad:
assignee: nobody → Brad Crittenden (bac)
status: Triaged → In Progress
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Brad Crittenden (bac) on 2012-06-22
tags: added: qa-untestable
removed: qa-needstesting
William Grant (wgrant) on 2012-06-25
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers