Skip to content
  1. Feb 23, 2024
  2. Feb 22, 2024
  3. Feb 20, 2024
  4. Feb 19, 2024
  5. Feb 15, 2024
    • Debbie Martin's avatar
      doc,oeqa/cam,yocto: Remove cam-service from Primary Compute · 50cb60e4
      Debbie Martin authored and Debbie Martin's avatar Debbie Martin committed
      
      
      Refine the remit of CAM usage to strictly within the Kronos
      design and test area. This includes:
       1. Remove documentation references to running cam-service on
          the Primary Compute.
       2. Remove test cases which invoke cam-service on the Primary
          Compute and any references to them in the documentation.
       3. Remove test cases which only test the CAM utility help
          output and any references to them in the documentation.
       4. Remove cam-service from the Kronos FEATURE_PACKAGES since
          it should not be used on the Primary Compute.
      
      Signed-off-by: default avatarDebbie Martin <Debbie.Martin@arm.com>
      50cb60e4
    • Debbie Martin's avatar
      oeqa/cam: Check errors on cam-service · 07341bb8
      Debbie Martin authored and Debbie Martin's avatar Debbie Martin committed
      
      
      Scan the cam-service logs for errors after running cam-app-example in
      the positive test cases. This prevents false positive test results
      whereby cam-app-example succeeds but cam-service has found errors.
      
      Signed-off-by: default avatarDebbie Martin <Debbie.Martin@arm.com>
      07341bb8
    • Debbie Martin's avatar
      oeqa/cam: Refactor tests to promote data calibration · 4548868f
      Debbie Martin authored and Debbie Martin's avatar Debbie Martin committed
      
      
      Refactor the CAM integration tests to reflect the new CAM reproduce
      workflow.
      
      Remove mention of default and custom UUIDs since we are no
      longer relying on a default one.
      
      Extend the processing period from 3000 to 4000 milliseconds in line
      with documentation.
      
      Remove the output command line argument for cam-tool analyze and
      cam-tool pack.
      
      Signed-off-by: default avatarDebbie Martin <Debbie.Martin@arm.com>
      4548868f
    • Debbie Martin's avatar
      doc: Make the data calibration workflow the default for CAM · 781d82d7
      Debbie Martin authored and Debbie Martin's avatar Debbie Martin committed
      
      
      In the CAM reproduce documentation, make the data calibration workflow
      the default flow rather than using the deployed example preset data
      (.csd files). This allows for greater flexibility in the UUIDs and
      parameters chosen, and also condenses the two workflows into a single
      one.
      
      Extend the processing period from 3000 to 4000 milliseconds to fix
      temporal error on cam-service.
      
      Fix copy-and-paste error where baremetal is referenced in the
      virtualization section.
      
      Remove the output command line argument for the cam-tool pack and
      cam-tool analyze commands since it will infer the same by default
      from the input argument.
      
      Signed-off-by: default avatarDebbie Martin <Debbie.Martin@arm.com>
      781d82d7
  6. Feb 14, 2024
    • Ziad Elhanafy's avatar
      doc: Rename Introduction section to Overview · 3af03b05
      Ziad Elhanafy authored
      
      
      Rename the Introduction section to Overview and improve it,
      The following changes are also included:
      1- Move "Documentation Overview" to the top and rename it
         to "Audience".
      2- Remove/Rework some sentences.
      3- Rename RSS to RSE, but use RSS as an alias for it.
      4- Use "Kronos Reference Design" as an alias for "Arm Reference
         Design-1 AE".
      
      Signed-off-by: Ziad Elhanafy's avatarZiad Elhanafy <ziad.elhanafy@arm.com>
      3af03b05
  7. Feb 13, 2024
    • Luca Fancellu's avatar
      yocto/oeqa: Improve LinuxBackgroundRun __exit__ function · 0595e101
      Luca Fancellu authored
      
      
      If an exception is thrown inside the 'with' context, the
      __exit__ method will be called and the code inside it will
      return False to re-raise the exception at the end of the
      __exit__ function, but before that, the kill() method will
      be called and some command will be sent to the console.
      
      However in the case of an exception for timeout, for example
      a command that runs indefinitely for any reason, the underlying
      console is still busy with the overrun command and any subsequent
      commands issued by the kill() function won't be executed.
      
      To prevent this case, rework the __exit__ function to send a
      signal through ctrl-C and try to stop the command running, wait
      for the prompt to be available and only at this point start the
      procedure to stop the background process.
      Create a new helper function in LinuxTermUtils to stop the running
      command and wait for the prompt.
      
      Signed-off-by: Luca Fancellu's avatarLuca Fancellu <luca.fancellu@arm.com>
      0595e101
  8. Feb 12, 2024
  9. Feb 08, 2024
  10. Feb 07, 2024
Loading