Return-Path: Received: from [193.112.141.254] (grouse.ravenbrook.com [193.112.141.254]) by raven.ravenbrook.com (8.11.6/8.11.3) with ESMTP id fASL94q42752 for ; Wed, 28 Nov 2001 21:09:04 GMT (envelope-from gdr@ravenbrook.com) Mime-Version: 1.0 X-Sender: gdr@pop3 Message-Id: Date: Wed, 28 Nov 2001 21:09:01 +0000 To: p4dti-staff@ravenbrook.com From: Gareth Rees Subject: Release 1.3.1 test report, 2001-11-28 Content-Type: text/plain; charset="us-ascii" ; format="flowed" This is a test report for P4DTI release 1.3.1. 1. When the migration script stops with an error, it doesn't say which job it was migrating when things went wrong. Usually it's the next one in sequence, but with a complicated migrate_p or a gappy list of jobs it may be hard to figure out. So it would be better if the migrate script printed "Migrating..." before it does so rather than "Migrated..." afterwards. 2. If you have bugzilla_directory set, then there's a long wait after the last job is migrated. I noted this in the AAG but it would be better if the P4DTI said what was happening. (We might put a note in the AAG to turn off bugzilla_directory during migration?) 3. The P4DTI locks the Bugzilla tables during migration so Bugzilla is not available for use. There should be a note about this in the AAG. 4. Translator errors don't let you know which field was being translated. So it's hard to figure out what went wrong. The replicator needs to say what it was up to when the problem happened. See . 5. translate_jobspec must return the job (even if you just modified it) but prepare_issue need not return anything. This is confusing. If we don't fix this we should at least check it. See .