[m-dev.] testing.mercurylang down?

[Julien Fischer]

Hi Peter,

On Sun, 13 Oct 2024 at 13:21, Peter Wang <novalazy at gmail.com> wrote:
>
> On Sun, 13 Oct 2024 13:20:39 +1100 Peter Wang <novalazy at gmail.com> wrote:
> > On Thu, 10 Oct 2024 16:38:59 +1100 Peter Wang <novalazy at gmail.com> wrote:
> > > On Thu, 10 Oct 2024 16:05:37 +1100 Julien Fischer <jfischer at opturion.com> wrote:
> > > > Hi Peter,
> > > >
> > > > testing.mercurylang appears to be down (looking at what it was last doing
> > > > I suspect it may be because the disk was filled up with deep profiles.)
> > >
> > > Thanks. I've cleared up some space by deleting old ROTD archives and
> > > compressing old build logs. On the days when we test the java grade,
> > > the logs take up more space, about 64 MB instead of 20 MB.
> >
> > Actually, you're right. The build directory is filling up with *.procrep
> > files.
> >
> > $ du -h *.procrep|sort -h
>
> And *.data files.

Oh, I see what's happened -- previously we would have just overwritten
each Deep.data
and Deep.procrep file but since they no longer have the same name that
no longer happens.
We have mechanisms to disable the generation of deep profiling files,
but in .profdeep
bootchecks we should be writing them out IMO (i.e. to test that
writing them out works).

I suppose we should add a runtime option that lets us use the old
Deep.data and Deep.procrep
names (or some other standardized names).

Julien.