Check bugs:

  • BUG #38420: FIXED
    • set the following parameters:
      <parameter name="JOB_PURGE_RATE" value="5" /> <!-- minutes -->
          <parameter name="JOB_PURGE_POLICY" value="ABORTED 5 minutes ; CANCELLED 5 minutes ; 
                             DONE-OK 5 minutes ; DONE-FAILED 5 minutes ; REGISTERED 5 minutes ;" />
      in the commandexecutor section of the cream configuration
    • submit a short-live job (10 minutes) and verify the "really-running" status
    • wait 20 minutes and verify that the job has been purged

  • BUG #41122: FIXED
    • execute the command "CEMonitorGetEvent" with a "DUMMY" topic and/or a "DUMMY" dialect, or whatever topic which is not listed by the "CEMonitorGetTopics" command.
    • verify that the error message returned is like:
      CEMon raised a fault:
      MethodName  =[getTopicEvent]
      Timestamp   =[1223972246]
      ErrorCode   =[3]
      Description =[Topic "DUMMY" not supported]
      FaultCause  =[Topic "DUMMY" not supported]

  • BUG #41189: FIXED
    • Verify the SQL scripts contained into /opt/glite/etc/glite-ce-cream/ directory

  • BUG #41382: FIXED
    • Submit a jdl containing the statement:
      CERequirements = ( other.GlueHostMainMemoryVirtualSize > 900 );
      and verify the correct execution of the job

  • BUG #41713: HOPEFULLY FIXED
    • internal fix

  • BUG #41716: FIXED
    • Submit a jdl containing the statement:
      CERequirements = ( "other.GlueHostMainMemoryRAMSize > 300" );
      and verify the correct execution of the job
    • There are some problems:
      • The temporary file with the requirement is not removed from the CE
      • If the job cannot submit due to not satisfied requirements a not clear message is returned:
                Status        = [ABORTED]
                ExitCode      = []
                FailureReason = [BLAH error: no jobId in submission script's output (stdout:) (stderr:) N/A (jobId = CREAM954746023)]
        or
                Status        = [ABORTED]
                ExitCode      = []
                FailureReason = [BLAH error: submission command failed (exit code = 1) (stdout:) (stderr:rm: cannot remove `/tmp/ce-req-file-1223995102337785': Operation not permitted-RUNLIMIT: Cannot exceed queue's hard limit(s). Job not submitted.-) N/A (jobId = CREAM698595553)]
        

  • BUG #41724: HOPEFULLY FIXED
    • internal improvement

  • BUG #41818: FIXED
    • execute the cream testsuite

  • BUG #41823: FIXED
    • submit a "one second sleep" job or submit a long-live job and restart the service when the job reaches the "REALLY-RUNNING" status
    • verify that the job reaches a termination state

  • BUG #41880: HOPEFULLY FIXED
    • internal fix, cannot reproduce

  • BUG #42096: FIXED
    • submit a jdl without the outputsandbox parameter and verify the correct execution of the job

  • BUG #42324: FIXED
    • submit a long-live job and restart only the CREAM service when the job reaches the "REALLY-RUNNING" status
    • verify that the status of the job changes after the startup

  • BUG #42401: FIXED
    • submit the following jdl (specify a valid URL for outputsandboxdesturi):
      [
      executable="/bin/env";
      stdoutput="out.txt";
      outputsandbox="out.txt";
      outputsandboxdesturi={ "gsiftp://........../tmp/out.txt" };
      MWversion="3.1.0";
      ]
      
    • verify that the "out.txt" file contains the definition:
      EDG_MW_VERSION=3.1.0

  • BUG #42649: HOPEFULLY FIXED
    • run the testsuite with high values for maxRunningJobs and maxConcurrentSubmit parameters

-- AlessioGianelle - 13 Oct 2008

Edit | Attach | PDF | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | More topic actions
Topic revision: r5 - 2011-02-24 - AlessioGianelle
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback