As usual, when people start using new MTT features, they use them in
new/unique ways that we hadn't thought of... ;-)
On Oct 5, 2007, at 2:48 AM, Josh Hursey wrote:
> I just lengthened the size of the 'launcher' value to 128 chars.
> Hopefully that helps.
> In the process I noticed a 'stuck' postgres select that was from
> yesterday sometime. The only way to get rid of it was to restart the
> postgres server. All looks well now.
> -- Josh
> On Oct 4, 2007, at 7:40 PM, Josh Hursey wrote:
>> Just got this from IU. Looks like BigRed is using a script for
>> launch. Should I make the 'laucher' field a bit larger?
>> On Oct 4, 2007, at 7:19 PM, jjhursey_at_[hidden] wrote:
>>> SQL QUERY: INSERT INTO test_run_command
>>> (test_run_command_id, launcher, resource_mgr, parameters, network,
>>> test_run_network_id) VALUES
>>> ('247', '/N/u/mpiteam/BigRed/local/bin/dompich', 'loadleveler',
>>> '', '', '2')
>>> SQL ERROR: ERROR: value too long for type character varying(16)
>>> SQL ERROR:
>> mtt-devel mailing list
> mtt-devel mailing list