#172 Usability: See meaningful errors from the standard-test-roles execution
Opened 6 years ago by mvadkert. Modified 6 years ago

User story: As a user I would like to see meaningful errors if something goes wrong in executions of the testing and how to deal with the situation.

User story: As a CI system I want to be able to inform user with a meaningful error if something goes wrong unrelated to test execution itself and how to deal with the problem.

Examples of current failures:

TASK [standard-test-rpm : Install the test subject RPMs] ***********************

failed: [/workDir/workspace/upstream-fedora-f28-pipeline/images/untested-cloud.qcow2] (item=/workDir/workspace/upstream-fedora-f28-pipeline/images/untested-cloud.qcow2) => {"changed": false, "item": "/workDir/workspace/upstream-fedora-f28-pipeline/images/untested-cloud.qcow2", "module_stderr": "Shared connection to 127.0.0.3 closed.\r\n", "module_stdout": "Traceback (most recent call last):\r\n  File \"/tmp/ansible_lwt5v223/ansible_module_dnf.py\", line 534, in <module>\r\n    main()\r\n  File \"/tmp/ansible_lwt5v223/ansible_module_dnf.py\", line 530, in main\r\n    ensure(module, base, params['state'], params['name'], params['autoremove'])\r\n  File \"/tmp/ansible_lwt5v223/ansible_module_dnf.py\", line 414, in ensure\r\n    base.install(pkg_spec)\r\n  File \"/usr/lib/python3.6/site-packages/dnf/base.py\", line 1810, in install\r\n    raise dnf.exceptions.MarkingError(_('no package matched'), pkg_spec)\r\ndnf.exceptions.MarkingError: no package matched\r\n", "msg": "MODULE FAILURE", "rc": 0}

    to retry, use: --limit @/workDir/workspace/upstream-fedora-f28-pipeline/knot/tests/tests.retry
TASK [standard-test-rhts : Check the results for failures] *********************

fatal: [/workDir/workspace/upstream-fedora-rawhide-pipeline/images/untested-cloud.qcow2]: FAILED! => {"changed": true, "cmd": "egrep '^(FAIL|WARN|None) ' \"/tmp/artifacts/test.log\"", "delta": "0:00:00.009384", "end": "2018-04-10 17:36:21.956866", "failed_when_result": true, "rc": 0, "start": "2018-04-10 17:36:21.947482", "stderr": "", "stderr_lines": [], "stdout": "FAIL Master-server-not-chrooted", "stdout_lines": ["FAIL Master-server-not-chrooted"]}

    to retry, use: --limit @/workDir/workspace/upstream-fedora-rawhide-pipeline/bind/tests/tests.retry
TASK [str-common : include_tasks] *********************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"reason": "Unable to retrieve file contents\nCould not find or access '/mnt/tests/pkgs-unknown.yml'"}
    to retry, use: --limit @/mnt/tests/tests.retry

Login to comment on this ticket.

Metadata