Kepler

The revision.txt file needs to be updated each night if the ptII build succeeds. I was under the impression that this was running as a cron job on a server. This is def. something that should be automated not done manually. If the revision.txt file gets too out of date, forking will ensue between ptII and kepler.

I created a script that lives on code.kepler-project.org (ceres) to do this. It is set to run in a cron job every day at 5am PDT. I will monitor it to make sure it keeps running.

Excellent. For whatever reason, the cron job on Pantara was not running. Hopefully this works.

revisions.txt has not been updated since 9/17.

bash-3.2$ svn log ptII/module-info/revision.txt

svn log ptII/module-info/revision.txt

------------------------------------------------------------------------
r20713 | welker | 2009-09-17 07:55:40 -0700 (Thu, 17 Sep 2009) | 1 line

[build-system] Checking in changes to ptII...
------------------------------------------------------------------------
r20691 | berkley | 2009-09-16 10:58:45 -0700 (Wed, 16 Sep 2009) | 1 line

[build-system] Checking in changes to ptII...

We run the real risk of forking the ptII tree and having a hard time merging.

My cron job has, for some reason, decided not to find ant. I'm working with Nick on figuring this out.

Working again. I'll monitor this to make sure it keeps working.

ptolemy/revisions.txt is not being automatically updated so I'm reopening this.

From the svn logs, it looks like the last time it was updated by
the build system was 2/04/10.
I'm marking this as P3/Normal because we run the risk of Kepler
using an out of sync version of ptII and thus forking ptII.

It is important that Kepler developers use the most recent Ptolemy sources
so I'm marking this as targeting Kepler 2.1.0. As of today, 7/6/2010,
kepler/ptolemy/module-info/revision.txt has not been updated since 6/7/2010.
Ptolemy is now at revision 58488, Kepler developers are using 57948. Obviously,
not each revision is a bug fix that is relevant to Kepler.

I'm estimating that it will take 6 hours to get the nightly build to
update ptolemy/module-info/revisions.txt file because it will take
time over several days to keep on top of this.

I just tried to manually move kepler trunk up to ptolemy head, but I can't compile:
[compile] /Users/derik/dev2/kepler.modules.sensorview/ptolemy/src/ptolemy/data/ontologies/InfiniteConcept.java:50: cannot find symbol
[compile] symbol : constructor Concept(ptolemy.kernel.util.NamedObj,java.lang.String)
[compile] location: class ptolemy.data.ontologies.Concept
[compile] super(finiteConcept.getContainer(), finiteConcept.getName());
[compile] ^
[compile] /Users/derik/dev2/kepler.modules.sensorview/ptolemy/src/ptolemy/data/ontologies/lattice/adapters/monotonicityAnalysis/MonotonicityCounterexamples.java:97: method does not override a method from its superclass
[compile] @Override
[compile] ^
[compile] /Users/derik/dev2/kepler.modules.sensorview/ptolemy/src/ptolemy/data/ontologies/lattice/adapters/monotonicityAnalysis/MonotonicityCounterexamples.java:105: method does not override a method from its superclass
[compile] @Override
[compile] ^
[compile] /Users/derik/dev2/kepler.modules.sensorview/ptolemy/src/ptolemy/data/ontologies/lattice/adapters/monotonicityAnalysis/MonotonicityCounterexamples.java:114: method does not override a method from its superclass
[compile] @Override
[compile] ^

r58807 is the most recent version I can compile Kepler with, but on import to eclipse I get 114 errors, to do w/ classes in:
/ptolemy/src/ptolemy/domains/jogl/

This look like because of problems with these missing imports:
import javax.media.opengl.*
com.sun.opengl.*

I see we're already excluding domains/gr in PtolemyClasspathStart. Is domains/jogl something we want to exclude too?

I think the @override warnings are from using Java 1.5.
Adding jogl to the excludes seems reasonable.
data/ontologies could also be added to the excludes.

If excluding those from building system, please make sure it's also updated for eclipse building. To update it, just modify the PtolemyClasspathStart file at build-area/resources/eclipse.

We probably also need to update corresponding files at build-area/resources/netbeans and build-area/resources/idea.

Trunks now using ptolemy r58807, and I added the jogl exclude for eclipse.
idea's PtolemyModuleStart already excludes domains/jogl and I couldn't find any exclude section for netbeans.

A cron job has been started on lore.genomecenter.ucdavis.edu to run 'ant validate-ptolemy' every midnight. The revision.txt commits should be a few minutes after, by SVN user 'riddle'. There were some issues with making the ant target send an email when the command fails. Where to place code that is executed in response to an error at any point along the pipeline (updating modules, compilation, committing revision.txt, etc.) and taking uniform action is not clear.

The code to send the email is, however, already written, so if anyone wants to investigate ant and figure out how to process the different types of errors, they are welcome to.

Since this cron job approach has had problems before, logs are maintained and rotated with logrotate. The logs are located at /home/sean/ptolemy-validation/ (on lore), and can be viewed by any user in the sudo group (Sean Riddle, Daniel Zinn, Sven Koehler, at the moment).

I also added the same information as above to the Kepler Project wiki: https://kepler-project.org/developers/reference/validate-ptolemy-cron-job

Original Bugzilla ID was 4324