<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2014/1/15 Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=""><div class="h5">On 14 January 2014 19:10, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
> Hi Frank,<br>
><br>
><br>
> On Mon, Jan 13, 2014 at 11:20 PM, Frank Shearar <<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>><br>
> wrote:<br>
>><br>
>> On 13 January 2014 23:42, David T. Lewis <<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>> wrote:<br>
>> > On Tue, Jan 14, 2014 at 12:28:45AM +0100, Nicolas Cellier wrote:<br>
>> >> 2014/1/14 karl ramberg <<a href="mailto:karlramberg@gmail.com">karlramberg@gmail.com</a>><br>
>> >><br>
>> >> > TraitsFileOutTest is failing<br>
>> >> ><br>
>> >> > Correct log attached this time<br>
>> >> ><br>
>> >> > Cheers,<br>
>> >> > Karl<br>
>> >> ><br>
>> >> > id: #[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]<br>
>> >> means the file was closed...<br>
>> >><br>
>> >> I observed increasing failure rate related to randomly closed change<br>
>> >> log<br>
>> >> the last few months (particularly when loading/merging with MC), it<br>
>> >> would<br>
>> >> be good to identify the root cause...<br>
>> >><br>
>> ><br>
>> > That sounds like exactly the problem that Frank was describing in<br>
>> > another<br>
>> > thread. He was ending up with a corrupt changes file IIRC, and the<br>
>> > problems<br>
>> > he described seemed to be related to primSize checks on a changes file<br>
>> > that<br>
>> > had been closed (this would presumably be a process trying to append to<br>
>> > the<br>
>> > changes file when some other process had closed the file stream).<br>
>><br>
>> I'm relieved it's not just me, but sad that it's not just me<br>
>> experiencing this. So my understanding is that changes are stored by<br>
>> accessing SourceFiles at: 2. If you want a readonly copy of sources or<br>
>> changes, you use CurrentReadOnlySourceFiles at: 2. I suppose the first<br>
>> step is verifying that nothing referencing these _directly_ does<br>
>> things like closing files (I'd be tempted to look at CROSF first.)<br>
><br>
><br>
> forgive me for not replying earlier but I needed help to track this down.<br>
> We suffered a very similar symptom a while ago at Cadence. It turns out<br>
> that in our case the issue was the system running out of file handles<br>
> because it left lots of fils open. The cause was with Monticello package<br>
> loading and the fix was to use CurrentReadOnlySourceFiles more. I'm<br>
> attaching a changeset in the hope that this is the same issue and that our<br>
> changeset can point you towards a fix.<br>
<br></div></div></blockquote><div><br></div><div>Yeah, that's the problems that I most often encounter with changes files, and for a long time:<br> 'no such
file or directory' when opening the changes failed<br>I agree, most probably a simple problem of limited resources (like too many readOnlyCopy files were opened, but
not yet closed/reclaimed).<br>Eliot, isn't it your fault? The faster the VM, the sooner we hit the resource limits<br><br>But I also managed to get a corrupt change log recently, could not trace it...<br>I suspect that closing the original changes is a bit different than starving of new readOnlyCopy, but who knows...<br>
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div class="h5">
</div></div>Thanks, Eliot. From what I can make out, the MCPackage >> #snapshot in<br>
this filein differs from trunk's only in the "reject: [:ea | [ea<br>
methodClass language isNewspeakLanguage3]ifError:[false]" guard. So<br>
the significant part of the changeset is PackageInfo >><br>
#changeRecordForOverriddenMethod:, which I've submitted to the Inbox<br>
as an mcz so we can all have a look.<br>
<br>
Thanks!<br>
<br>
frank<br>
<br>
> HTH<br>
<span class=""><font color="#888888">> --<br>
> best,<br>
> Eliot<br>
><br>
><br>
><br>
<br>
</font></span></blockquote></div><br></div></div>