[Dart] Proposed changes to Nightly targets

Ken Martin ken.martin at kitware.com
Thu, 26 Jul 2001 09:50:19 -0400


This is a multi-part message in MIME format.

------=_NextPart_000_0014_01C115B8.61300FB0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

The Update.html for vtk doesn't seem to be working. update.tmp is correctly
generated and update.xml is started but then it seems that the Tcl script
dies/crashes (with an error reported to Dan? via email?) Any ideas on what
is killing this?

Thanks
Ken


  -----Original Message-----
  From: dart-admin at public.kitware.com
[mailto:dart-admin at public.kitware.com]On Behalf Of Miller, James V (CRD)
  Sent: Tuesday, July 24, 2001 10:22 AM
  To: Dart (E-mail)
  Subject: [Dart] Proposed changes to Nightly targets


  Ken, Bill, and I were discussing changing Dart in the following ways:

  1. Move the dashboards start time from 3am EST to 11pm EST

      Motivation:
         This would allow people in Europe to submit dashboards that they
can use.  They could start their builds at 6am and hopefully finish before
they got into work.

      Solution:
          Modify existing cron jobs on servers to open/close the dashboard.
Clients still have the flexibility to run their jobs at a time that is
convenient for them.  But we should strive to have results on the Dashboards
early enough to be useful to Europe.

          Modify Update.tcl to specify a different time for an update

          We should probably parameterize Update.tcl so that a given project
can decide for itself when Nighly dashboards will be done.

      Impact:
          Eastern US would have to check in changes to be tested by nightly
dashboard to 11pm. Western US would have to check in changes to be tested by
nightly dashboard 8pm.

          Does this impact dashboard rollups, navigations, or datestamps? I
think datestamps are based on GMT.  So moving from 3am EST to 11pm EST will
not cause a change in date in GMT.


  2. make Nightly should do an Update

      Motivation:
         Clients current have to do a
              make DashboardStart
              make Nightly

          While servers have to do a
              make DashboardStart
              make DashboardEnd

          This will be confusing to people setting up clients because they
need to run a server operation (DashboardStart) before they do a client
operation (make Nightly) but they never run the matching server operation
DashboardEnd.

      Solution:
          "make Nightly" target should always do an update.

          Clients can then just do a "make Nightly".

          Servers would still do
                 make DashboardStart
                 make DashboardEnd

          make DashboardStart would still generate Update.xml for the
server's Dashboard tree

          Client's should generate an Update.xml and put it in the Sites
tree.  This will allow us to summarize the changes that appear for each
build (Nightly or Experimental).  This is vital for Experimental builds (we
can determine whether this is a continuous build and what changed) and is
nice for Nightly builds (so we can verify that all builds actually succeeded
in performing the update).

          Overall, we are striving to separate the client operation from the
server operation.  So people that just want to submit to the dashboard have
the "simplest" task.  People running Dart servers, have a little more to do
but there is a clear distinction on what is a client operation and what is a
server operation.

      Impact:
          Shared source builds would have multiple updates being run on the
same tree.  Probably not a big deal since cvs should properly lock/unlock so
one machine would do the update and the others would have an up to date
tree. We can finess this problem by building in some delays in our shared
source builds.


  I'll attack these in the next few days. I may wait until we label our
alpha for Insight before I change Dart.


  Jim Miller
  _____________________________________
  Visualization & Computer Vision
  GE Corporate Research & Development
  Bldg. KW, Room C218B
  P.O. Box 8, Schenectady NY 12301

  millerjv at crd.ge.com <mailto:millerjv at crd.ge.com>
  (518) 387-4005, Dial Comm: 8*833-4005,
  Cell: (518) 505-7065, Fax: (518) 387-6981




------=_NextPart_000_0014_01C115B8.61300FB0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3103.1000" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D488254813-26072001>The=20
Update.html for vtk doesn't seem to be working. update.tmp is correctly=20
generated and update.xml is started but then it seems that the Tcl =
script=20
dies/crashes (with an error reported to Dan? via email?) Any ideas on =
what is=20
killing this?</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D488254813-26072001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D488254813-26072001>Thanks</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D488254813-26072001>Ken</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D488254813-26072001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D488254813-26072001></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B>=20
  dart-admin at public.kitware.com =
[mailto:dart-admin at public.kitware.com]<B>On=20
  Behalf Of </B>Miller, James V (CRD)<BR><B>Sent:</B> Tuesday, July 24, =
2001=20
  10:22 AM<BR><B>To:</B> Dart (E-mail)<BR><B>Subject:</B> [Dart] =
Proposed=20
  changes to Nightly targets<BR><BR></DIV></FONT>
  <DIV><SPAN class=3D420202613-24072001><FONT size=3D2>Ken, Bill, and I =
were=20
  discussing&nbsp;changing Dart in the following =
ways:</FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT size=3D2><STRONG>1. Move =
the=20
  dashboards start time from 3am EST to 11pm =
EST</STRONG></FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D420202613-24072001>&nbsp;&nbsp;&nbsp; <FONT=20
  size=3D2><STRONG>Motivation:</STRONG></FONT></SPAN></DIV>
  <DIV><SPAN=20
  =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<FON=
T=20
  size=3D2>This would allow people in Europe to submit dashboards that =
they can=20
  use.&nbsp; They could start their builds at 6am and hopefully finish =
before=20
  they got into work.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D420202613-24072001><STRONG><FONT =
size=3D2>&nbsp;&nbsp;&nbsp;=20
  Solution:</FONT></STRONG>=20
  <DIV><SPAN class=3D420202613-24072001><FONT size=3D2>
  <DIV><SPAN class=3D420202613-24072001><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Modify existing =
cron jobs on=20
  servers to open/close the dashboard.&nbsp; Clients still have the =
flexibility=20
  to run their jobs at a time that is convenient for them.&nbsp; But we =
should=20
  strive to have results on the Dashboards early enough to be useful to=20
  Europe.</FONT></SPAN></DIV>
  <DIV><SPAN=20
  =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;=20
  </SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Modify Update.tcl =
to specify=20
  a different time for an update</FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; We should probably =

  parameterize Update.tcl so that a given project can decide for itself =
when=20
  Nighly dashboards will be done.</FONT></SPAN></DIV>
  <DIV><SPAN =
class=3D420202613-24072001></SPAN>&nbsp;</DIV></FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001></SPAN><STRONG><FONT =
size=3D2><SPAN=20
  class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;=20
  </SPAN>Impact:</FONT></STRONG></SPAN></DIV></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Eastern US would =
have to=20
  check in changes to be tested by nightly dashboard to 11pm. Western US =
would=20
  have to check in changes to be tested by nightly dashboard=20
  8pm.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  <FONT size=3D2>Does this impact dashboard rollups, navigations, or =
datestamps? I=20
  think datestamps are based on GMT.&nbsp; So moving from 3am EST to =
11pm EST=20
  will not cause a change in date in GMT.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  </SPAN><SPAN class=3D420202613-24072001><FONT =
size=3D2></FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT size=3D2>
  <DIV><SPAN class=3D420202613-24072001><FONT size=3D2><STRONG>2. make =
Nightly=20
  should do an Update</STRONG></FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><STRONG></STRONG></SPAN><SPAN=20
  class=3D420202613-24072001><FONT size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D420202613-24072001>&nbsp;&nbsp;&nbsp; <FONT=20
  size=3D2><STRONG>Motivation:</STRONG></FONT></SPAN></DIV>
  <DIV><SPAN=20
  =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Clie=
nts=20
  current have to do a </SPAN></DIV>
  <DIV><SPAN=20
  =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;=20
  make DashboardStart</SPAN></DIV>
  <DIV><SPAN=20
  =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;=20
  make Nightly</SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001></SPAN>&nbsp;</DIV>
  <DIV><SPAN =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  While servers have to do a</SPAN></DIV>
  <DIV><SPAN=20
  =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;=20
  make DashboardStart</SPAN></DIV>
  <DIV><SPAN=20
  =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;=20
  make DashboardEnd</SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001></SPAN>&nbsp;</DIV>
  <DIV><SPAN =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  This will be confusing to people setting up clients because they need =
to run a=20
  server operation (DashboardStart) before they do a client operation =
(make=20
  Nightly) but they never run the matching server operation=20
  DashboardEnd.</SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D420202613-24072001><STRONG>&nbsp;&nbsp;&nbsp;=20
  Solution:</STRONG></SPAN></DIV>
  <DIV><SPAN =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "make Nightly" target should always do an update.&nbsp; </SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001></SPAN>&nbsp;</DIV>
  <DIV><SPAN =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Clients can then just do a "make Nightly".</SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001></SPAN>&nbsp;</DIV>
  <DIV><SPAN =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Servers would still do </SPAN></DIV>
  <DIV><SPAN=20
  =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;make=20
  DashboardStart</SPAN></DIV>
  <DIV><SPAN=20
  =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;make=20
  DashboardEnd</SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001></SPAN>&nbsp;</DIV>
  <DIV><SPAN =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  make DashboardStart would still generate Update.xml for the server's=20
  <STRONG>Dashboard </STRONG>tree</SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001></SPAN>&nbsp;</DIV>
  <DIV><SPAN =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Client's should generate an Update.xml and put it in the=20
  <STRONG>Sites</STRONG> tree.&nbsp; This will allow us to summarize the =
changes=20
  that appear for each build (Nightly or Experimental).&nbsp; This is =
vital for=20
  Experimental builds (we can determine whether this is a continuous =
build and=20
  what changed) and is nice for Nightly builds (so we can verify that =
all builds=20
  actually succeeded in performing the update).</SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001></SPAN>&nbsp;</DIV>
  <DIV><SPAN =
class=3D420202613-24072001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Overall, we are striving to separate the client operation from the =
server=20
  operation.&nbsp; So people that just want to submit to the dashboard =
have the=20
  "simplest" task.&nbsp; People running Dart servers, have a little more =
to do=20
  but there is a clear distinction on what is a client operation and =
what is a=20
  server operation.</SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001></SPAN><SPAN=20
  class=3D420202613-24072001></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D420202613-24072001>&nbsp;&nbsp;&nbsp; <FONT=20
  size=3D2><STRONG>Impact:</STRONG></FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Shared source =
builds would=20
  have multiple updates being run on the same tree.&nbsp; Probably not a =
big=20
  deal since cvs should properly lock/unlock so one machine would do the =
update=20
  and the others would have an up to date tree. We can finess this =
problem by=20
  building in some delays in our shared source =
builds.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D420202613-24072001></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D420202613-24072001>I'll attack these in the next =
few days. I=20
  may wait until we label our alpha for Insight before I change=20
  Dart.</SPAN></DIV>
  <DIV><SPAN =
class=3D420202613-24072001></SPAN>&nbsp;</DIV></FONT></SPAN></DIV>
  <DIV><SPAN class=3D420202613-24072001><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><B><FONT color=3D#000080 face=3D"Comic Sans MS">Jim=20
  Miller</FONT></B>&nbsp;<BR><B><I><FONT color=3D#ff0000 face=3DArial=20
  =
size=3D2>_____________________________________</FONT></I></B><I></I><BR><=
I></I><I><FONT=20
  color=3D#000000 face=3DArial size=3D1>Visualization &amp; Computer =
Vision<BR>GE=20
  Corporate Research &amp; Development<BR>Bldg. KW, Room C218B<BR>P.O. =
Box 8,=20
  Schenectady NY 12301<BR><BR></FONT><U><FONT color=3D#0000ff =
face=3DArial=20
  size=3D1>millerjv at crd.ge.com &lt;<A=20
  =
href=3D"mailto:millerjv at crd.ge.com">mailto:millerjv at crd.ge.com</A>&gt;</F=
ONT></U></I><BR><I><FONT=20
  color=3D#000000 face=3DArial size=3D1>(518) 387-4005, Dial Comm: =
8*833-4005,=20
  </FONT></I><BR><I><FONT color=3D#000000 face=3DArial size=3D1>Cell: =
(518) 505-7065,=20
  Fax: (518) 387-6981</FONT></I> </DIV><BR>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0014_01C115B8.61300FB0--