On Sat, Nov 23, 2013 at 12:49:01PM +0000, ian.hinder@aei.mpg.de wrote:
Modified: /release-info/ bethe__1_16.log, bethe__2_8.log, bluewaters__1_8.log, bluewaters__2_8.log, datura__1_6.log, datura__2_6.log, gordon__1_8.log, gordon__2_8.log, hopper__1_6.log, hopper__2_6.log, kraken__1_6.log, kraken__2_6.log, mike__1_8.log, mike__2_8.log, nvidia__1_6.log, nvidia__2_6.log, orca__1_1.log, orca__2_1.log, philip__1_8.log, philip__2_4.log, queenbee__1_8.log, queenbee__2_4.log, redshift__1_4.log, redshift__2_2.log, stampede__1_8.log, stampede__2_8.log, titan__1_6.log, titan__2_6.log, trestles__1_8.log, trestles__2_8.log, zwicky__1_6.log, zwicky__2_6.log
Log: Updated test results for bethe, bluewaters, datura, gordon, hopper, kraken, mike, nvidia, orca, philip, queenbee, redshift, stampede, tital, trestles, zwicky
This updated results from queenbee from Nov 18th - which were before some of the testsuite changes. Could it be that this mechanism commits everything instead of just new results?
Frank
Yes, you are right, this was my mistake. The commit to svn has to be manual because the credentials are CCT login credentials and should not be stored in an automated system. Since it is manual, it is subject to human error. I will leave this committing to Erik, since he knows when he launches the test jobs. Hopefully the jobs will run automatically soon.
users@lists.einsteintoolkit.org
-
Frank Loeffler -
Ian Hinder