WARNING! Access to this system is limited to authorised users only.
Unauthorised users may be subject to prosecution.
Unauthorised access to this system is a criminal offence under Australian law (Federal Crimes Act 1914 Part VIA)
It is a criminal offence to:
(1) Obtain access to data without authority. -Penalty 2 years imprisonment.
(2) Damage, delete, alter or insert data without authority. -Penalty 10 years imprisonment.
User activity is monitored and recorded. Anyone using this system expressly consents to such monitoring and recording.

To protect your data, the CISO officer has suggested users to enable 2FA as soon as possible.
Currently 2.6% of users enabled 2FA.

  1. 20 Apr, 2018 1 commit
    • John Zhang's avatar
      fix: callback path issue (Issue #20) · e51633dc
      John Zhang authored
      The path for harness in the target dacapo.jar
      has been put under the harness/ prefix.
      This caused incompatibility problems with previous releases.
      This commit fixes this problem.
  2. 22 Mar, 2018 1 commit
    • John Zhang's avatar
      build versioning · 5022f3e2
      John Zhang authored
      - specify `dacapo.version` and `dacapo.nickname` in dacapo.properties file;
      - build versino is dacapo version + git hash; this can be overwritten by cmd args;
      - use `build.target-jar` as output jar name; append build version to jar name.
  3. 29 Jan, 2018 1 commit
  4. 15 Sep, 2010 1 commit
  5. 25 Aug, 2010 1 commit
  6. 24 Aug, 2010 1 commit
    • john's avatar
      Separated harness and additional benchmark code. · ad34237a
      john authored
      Separated Digest into a separate library for inclusion in Tomcat and default Harness.
      Removed dependency in H2 benchmark code on Config (and commons cli).
      Top-level harness now loads classes through a separate class loader, which has a
      common parent with the benchmark class loader, but is not itself an ancestor or the
      benchmark class loader.  This isolates harness code from benchmark code.
  7. 23 Dec, 2009 1 commit
  8. 12 Aug, 2009 1 commit
    • jzigman's avatar
      [svn r505] Due to python.org switching from subversion to mercurial the svn · 9ba5e5cb
      jzigman authored
      checkout of jython, which uses a indirection for part of the checkout
      to svn.python.org no longer functions correctly.  To address this
      the following has been done:
      1) The svn checkout task now has a parameter to ignore failure---this is
         not ideal but the checkout of jython will checkout all and timeout
         on the indirection then finally fail.
      2) The CPythonLib, which is constructed from python.org source is now
         take from a download of a the 2.5.4 python source package.
      3) MD5 checksums have been updated to reflect the changes.
      4) Oddly the jython build will fail with three of the source files containing
         a non-ASCII character in the some comments.  While these files comply with
         the python standard by indicating the character encoding to use, they still
         do not build under ubuntu 8.10, but do build under ubuntu 9.04.  A patch
         has been added to jython.patch to change the characters to an approximate
         ASCII equivalent.
  9. 24 Jul, 2009 1 commit
    • jzigman's avatar
      [svn r493] Updated jython to 2.5.0 release. · 99f7f28b
      jzigman authored
      - included MD5 checksum
      Added "p" inputstring to svn call to hopefully avoid the svn certificate bug.
      Removed indents from some build files changing them to spaces.
      Removed commented out build code (as we don't want to unnecessarily maintain
        commented code).
  10. 08 Jul, 2009 1 commit
    • jzigman's avatar
      [svn r479] Getting source from svn and cvs now tar up their respective directories without · d661e952
      jzigman authored
      including the meta-data subdirectories in the tar ball and additionally they
      force the file date to be constant to ensure a consistent tar ball.
      Downloads of source files, svn or cvs repositories now work as follows:
      1) if no MD5 checksum exists
           the file(s) are downloaded (and tarred)
           an MD5 checksum is generated
           if the file(s) checksum does not match the existing checksum then
             the file(s) are downloaded (and tarred)
             and the existing checksum is verified to ensure correct behaviour
      Added MD5 checksums for the additional downloads for geronimo (activemq, catalina,
      jasper and jasper-el).  Updated existing MD5 checksums affected by the changed
      tar ball generation.
      Updated a couple of MD5 that seemed to apply to earlier versions.
  11. 15 Jun, 2009 2 commits
  12. 26 Jul, 2008 2 commits
  13. 23 Jul, 2008 2 commits