That's ok to leave as qa-untestable if the final fix hasn't landed yet.
qa-untestable is understood as "we cannot QA this", that meaning now or at
all.
To avoid QA bot to change the status of the bug now, when submitting the
branch just add the --incremental option to ec2 land, or manually add [incr]
to the commit message. That should be enough to QA bot doesn't touch this
bug until you submit the final fix of the series of fixes.
On Tue, Aug 17, 2010 at 11:22 AM, Curtis Hovey
<email address hidden>wrote:
> qa-untestible means the fix has landed and it cannot be tested. The
> final fix has not landed in this case. We do know how to test
> this...watch the pitti and mdz's pages fall off the timeout list.
>
> ** Tags removed: qa-untestable
>
> --
> ~person/+participation timeouts
> https://bugs.launchpad.net/bugs/607879
> You received this bug notification because you are subscribed to
> Launchpad Suite.
>
That's ok to leave as qa-untestable if the final fix hasn't landed yet.
qa-untestable is understood as "we cannot QA this", that meaning now or at
all.
To avoid QA bot to change the status of the bug now, when submitting the
branch just add the --incremental option to ec2 land, or manually add [incr]
to the commit message. That should be enough to QA bot doesn't touch this
bug until you submit the final fix of the series of fixes.
On Tue, Aug 17, 2010 at 11:22 AM, Curtis Hovey
<email address hidden>wrote:
> qa-untestible means the fix has landed and it cannot be tested. The +participation timeouts /bugs.launchpad .net/bugs/ 607879
> final fix has not landed in this case. We do know how to test
> this...watch the pitti and mdz's pages fall off the timeout list.
>
> ** Tags removed: qa-untestable
>
> --
> ~person/
> https:/
> You received this bug notification because you are subscribed to
> Launchpad Suite.
>