Great. Thanks for taking the time to do this!
Gary
On Oct 5, 2010, at 21:45, "Tim Sneddon" wrote:
> On 10/06/2010 07:23 AM, sebb wrote:
>> On 2 October 2010 16:11, sebb wrote:
>> These are all due to failure to destroy the subprocess on OpenVMS.
>>
>> I don't know if there is a workround.
>
Hi folks,
one note regarding the regression tests - check if there are still
background processes running because they will break the next test run
as well.
Cheers,
Siegfried Goeschl
On 10/6/10 6:19 PM, sebb wrote:
On 6 October 2010 05:44, Tim Sneddon wrote:
On 10/06/2010 07:23 AM, sebb
On 6 October 2010 05:44, Tim Sneddon wrote:
> On 10/06/2010 07:23 AM, sebb wrote:
>>
>> On 2 October 2010 16:11, sebb wrote:
>> These are all due to failure to destroy the subprocess on OpenVMS.
>>
>> I don't know if there is a workround.
>
> I know some time ago I had some fixes to the OpenVMS s
On 6 October 2010 12:53, James Carman wrote:
> So it's not a blocker then if we want to release?
No, I don't think it's a blocker, though we probably need to make the
restrictions clearer.
But of course it would be nice to have a solution ...
> On Oct 6, 2010 7:21 AM, "sebb" wrote:
>> On 6 Oct
So it's not a blocker then if we want to release?
On Oct 6, 2010 7:21 AM, "sebb" wrote:
> On 6 October 2010 10:36, James Carman wrote:
>> On Tue, Oct 5, 2010 at 7:23 PM, sebb wrote:
>>> These are all due to failure to destroy the subprocess on OpenVMS.
>>>
>>> I don't know if there is a workroun
On 6 October 2010 10:36, James Carman wrote:
> On Tue, Oct 5, 2010 at 7:23 PM, sebb wrote:
>> These are all due to failure to destroy the subprocess on OpenVMS.
>>
>> I don't know if there is a workround.
>>
>
> Is this something new? Did previous versions of exec pass these tests
> on OpenVMS?
On Tue, Oct 5, 2010 at 7:23 PM, sebb wrote:
> These are all due to failure to destroy the subprocess on OpenVMS.
>
> I don't know if there is a workround.
>
Is this something new? Did previous versions of exec pass these tests
on OpenVMS?
On 10/06/2010 07:23 AM, sebb wrote:
On 2 October 2010 16:11, sebb wrote:
These are all due to failure to destroy the subprocess on OpenVMS.
I don't know if there is a workround.
I know some time ago I had some fixes to the OpenVMS support. Sadly I
had to move on to something else before I go
On 2 October 2010 16:11, sebb wrote:
> I've tried running my modified copy of the test cases.
> The testExecuteWatchdogSync() also hangs on OpenVMS. Not sure where to
> put the timeouts for that yet, so I tried disabling it.
>
> I now get the following errors/failures:
>
> Time: 88.365
> There wer
I've tried running my modified copy of the test cases.
The testExecuteWatchdogSync() also hangs on OpenVMS. Not sure where to
put the timeouts for that yet, so I tried disabling it.
I now get the following errors/failures:
Time: 88.365
There were 4 errors:
1)
testExecuteWatchdogAsync(org.apache.
10 matches
Mail list logo