trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

Re: [trinity-devel] Tim: Collation of TSAK/TDM related issues

From: Darrell Anderson <humanreadable@...>
Date: Wed, 18 Apr 2012 14:41:00 -0700 (PDT)
> Yes it does, but YIKES that's a lot of problems! :-)
> 
> A few of the highest priority problems should already be
> fixed in GIT, but there are a slew of lower-priority (FIFO ownership/location,
> etc.) problems that are not yet fixed.
> 
> I think it would be helpful if we were to re-file each of
> the issues you mentioned above as a separate bug report, then point the
> original (combined) reports to block on any of the new (separate)
> reports that apply.  Otherwise it will be very difficult to keep
> track of what was fixed and what still needs to be done!

Might seem like a lot, but several issues likely need little more than testing the run level or whether TDM is running.

Regarding the FIFO stuff, checking tdmrc:useSAK as the first step and basic housekeeping resolves several issues.

After collating the list I don't think we're in horrible or overwhelming shape. All I see at this point is needing some fine-tuning --- as is the typical bug quashing process for new code. We'll get there much sooner than later. :)

The biggest fix is that tdmrc:useSAK=false is always honored. The quiets 80% or more of all users. :)

Let me finish my build run and then test the latest patches. Then I can assess into separate new reports.

Darrell