Add missing Tags

Changes:
Add missing Tags for test cases

Tested:
NA

Change-Id: I5f5983005ba16d630af76361bbb39d668e63c0ed
Signed-off-by: Sridevi Ramesh <sridevra@in.ibm.com>

Update log collection logic

Changes:
- Terminate log collection if SSH, and Redfish fails

Change-Id: Ib3dde69d1a1b4396640421160277909ccd83ef67
Signed-off-by: George Keishing <gkeishin@in.ibm.co

Update log collection logic

Changes:
- Terminate log collection if SSH, and Redfish fails

Change-Id: Ib3dde69d1a1b4396640421160277909ccd83ef67
Signed-off-by: George Keishing <gkeishin@in.ibm.com>

show more ...

ffdc: Integrate ffdc script into robot framework flow.

This commit provides interface to enable automation tests (robot/jenkins)
to activate the new cli ffdc collector.

- Patchset 1: Initial commit

ffdc: Integrate ffdc script into robot framework flow.

This commit provides interface to enable automation tests (robot/jenkins)
to activate the new cli ffdc collector.

- Patchset 1: Initial commit for review.
- Patchset 2: Redesing and fixing issues
- Patchset 3: Fix build issue (pycodestyle)
- Patchset 4: Default ffdc store location running direct CLI
- Patchset 5: Addressing review comments and questions
- Patchset 6: Restore direct CLI default location to /tmp
- Patchset 7: Addressing issues from comments
Also extend socket timeout for long-running command peltool -a
- Patchset 8: Use Builtin().log_to_console("") method in the bridge code
- Patchset 9: Rebase

Tests:
- Standalone script: python3 ./ffdc/collect_ffdc.py
- Within robot env: python3 -m robot .... -v FFDC_DEFAULT:0 ./tools/myffdc.robot

Signed-off-by: Peter D Phan <peterp@us.ibm.com>
Change-Id: Ic892c48efe7dbdb3a4345ba89c3a0257f03a7ffb

show more ...

Enforced robotframework standards.

- The standards are enforced using the rflint static anylysis tool.
- More standards will be added in future commits but this is a base
starting point.

Change-I

Enforced robotframework standards.

- The standards are enforced using the rflint static anylysis tool.
- More standards will be added in future commits but this is a base
starting point.

Change-Id: I7dd8a2b0b42a51327b748cb730609d7ee2538de3
Signed-off-by: Joy Onyerikwu <onyekachukwu.joy.onyerikwu@ibm.com>

show more ...

Name changes for FFDC Test Cases: "FFDC On Test Case Fail" and "FFDC"

Changed FFDC Test Cases Names in lib/openbmc_ffdc.robot:
Changed the name of "Log FFDC" to "FFDC On Test Case Fail"
Changed the

Name changes for FFDC Test Cases: "FFDC On Test Case Fail" and "FFDC"

Changed FFDC Test Cases Names in lib/openbmc_ffdc.robot:
Changed the name of "Log FFDC" to "FFDC On Test Case Fail"
Changed the name of "Log FFDC If Test Case Failed" to "FFDC"
The names were reversed..
"Log FFDC" had a check to see if Test Case failed.
"Log FFDC If Test Case Failed" had the actual FFDC gathering.

Change-Id: I50a0cae783180c4bdbe82c94f2cd57f803a05998
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>

show more ...

Manual FFDC log collection

There is use case where a user needs to trigger FFDC collection
manually on demand. This would be helpful while doing developement
or manual test for specific use case and

Manual FFDC log collection

There is use case where a user needs to trigger FFDC collection
manually on demand. This would be helpful while doing developement
or manual test for specific use case and recreate logs.

The robot code is a wrapper to the existing FFDC infrastructure.

Resolves openbmc/openbmc-test-automation#134

Change-Id: I85f11e3f64ba94e17da1c8fbafc4fd29a87fef1f
Signed-off-by: George Keishing <gkeishin@in.ibm.com>

show more ...