All of lore.kernel.org
 help / color / mirror / Atom feed
From: "P T, Sarath" <Sarath_PT@mentor.com>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Tests run on CIP-LAVA platform
Date: Mon, 17 Oct 2022 07:03:48 +0000	[thread overview]
Message-ID: <47d0ac6c735c4251abb3602a43b20d77@mentor.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]

Hi Team,

I could able to see there are few tests are running in the CIP LAVA platform. I am showing the list below what all LAVA tests are running in the CIP LAVA platform.


Test-case

CIP LAVA job link

Status

Comments


i)                 spectre-meltdown-checker-test

https://lava.ciplatform.org/scheduler/job/686074

Not run

Reason of failure

./spectre-meltdown-checker.sh: Permission denied.


ii)               hackbench

https://lava.ciplatform.org/results/634343

PASS




iii)             cyclictest

https://lava.ciplatform.org/results/634097

SKIP

Reason of failure

$ ./cyclictest.sh -D 2m -p 98 -i 1000 -t 1 -a 0 -h '' -w '' this command is giving "/usr/bin/cyclictest: unrecognized option" error


iv)              cyclicdeadline

https://lava.ciplatform.org/results/633692

Not run

Reason of failure


while executing cyclicdeadline.sh getting an error like

/usr/bin/cyclicdeadline: invalid option -- 'q'



Is there any specific reason why few test-cases are running through LAVA ?


Regards

Sarath P T


[-- Attachment #2: Type: text/html, Size: 14287 bytes --]

             reply	other threads:[~2022-10-17  7:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  7:03 P T, Sarath [this message]
2022-10-18 12:07 ` Tests run on CIP-LAVA platform Chris Paterson
2022-10-18 12:10   ` [cip-dev] " P T, Sarath
2022-10-17 13:01 P T, Sarath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47d0ac6c735c4251abb3602a43b20d77@mentor.com \
    --to=sarath_pt@mentor.com \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.