Launchpad itself

We need a buildbot that runs --layer=MailmanLayer daily

Bug #383348 reported by Barry Warsaw
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Low
Unassigned

Bug Description

With the fix for bug 383203 and the various spurious test failures landing, we will not be running the Mailman integration tests for every landing. This is a good thing since they often fail with spurious failures and most are already disabled anyway, so it's no big loss. However, we really want to run --layer=MailmanLayer at least once a day to ensure we're not breaking things.

Since Gary's Mr. Buildbot atm, he suggested I submit a bug to request a buildbot to run this daily test. In the meantime, I will seduce my local cron and ec2 into running these once a day in headless mode.

Gary Poster (gary)
tags: added: build-infrastructure
Michael Hudson-Doyle (mwhudson)
Changed in launchpad-foundations:
assignee: Gary Poster (gary) → Michael Hudson (mwhudson)
Revision history for this message
Barry Warsaw (barry) wrote :

Hmm. This no longer seems to run just the MailmanLayer tests; it seems to run everything. Have we broken --layer?

% bin/test -vv --layer=MailmanLayer

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Didn't get to this in my BE stint.

Changed in launchpad-foundations:
assignee: Michael Hudson (mwhudson) → nobody
Revision history for this message
Jonathan Lange (jml) wrote :

Why not fix the tests instead?

Revision history for this message
Barry Warsaw (barry) wrote :

Yah, well easier said than done. ;)

We've taken a couple of shots at this, improving it each time but not completely fixing them. The main problem is that Mailman 2 is not really designed well for testing and there are numerous race conditions that are difficult to get rid of. All ideas are welcome though!

Curtis Hovey (sinzui)
Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
tags: added: tech-debt
Revision history for this message
Curtis Hovey (sinzui) wrote :

I think we can plan to get rid of the mailman layer or at least make is reliable in the test runner in a few weeks. We have new test infrastructure that allows us to test lp configuration and monkeypatches in the DatabaseFunctionalLayer

Revision history for this message
Barry Warsaw (barry) wrote :

Note that once I start working on the MM3 integration, we should be able to eliminate all the nasty log file parsing and the accompanying race conditions. MM3 uses a zope.event based notifier which we can hook to do the "task done" notifications (at least in theory).

Curtis Hovey (sinzui)
Changed in launchpad-foundations:
status: Triaged → Won't Fix
Revision history for this message
Curtis Hovey (sinzui) wrote :

The timeouts on this layer happens testing non-integration features. Most of the tests on the mailman layer can be run on the DatabaseFunctionalLayers as unit tests. The mailman layer can be run with every test run when only tests it includes verifies that the mailman <-> xmlrpc <-> launchpad communication operates.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.