[ OST Failure Report ] [ oVirt master ] [ 01-10-2017 ] [ change-queue-tester ]
by Shlomo Ben David
Hi,
Link to suspected patches: https://gerrit.ovirt.org/#/c/82350/2
Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-
tester/2949/
Link to all logs:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2949/artifa...
(Relevant) error snippet from the log:
<error>
lago.utils: ERROR: Error while running thread Traceback (most recent call
last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in
_ret_via_queue queue.put({'return': func()}) File
"/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in
wrapper return func(get_test_prefix(), *args, **kwargs) File
"/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 78, in
wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs
File "/home/jenkins/workspace/ovirt-master_change-queue-tester@2/ovirt-system-tests/basic-suite-master/test-scenarios/004_basic_sanity.py",
line 372, in live_storage_migration disk_service.get().status,
types.DiskStatus.OK) File
"/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 258, in
assert_equals_within_long func, value, LONG_TIMEOUT,
allowed_exceptions=allowed_exceptions File
"/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 237, in
assert_equals_within '%s != %s after %s seconds' % (res, value, timeout)
AssertionError: False != ok after 600 seconds
</error>
Best Regards,
Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
RHCSA | RHCE | RHCVA
IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
OPEN SOURCE - 1 4 011 && 011 4 1
7 years, 1 month
Invitation to API 'Live Documentation' presentation - Oct 2
by Ori Liel
This coming Monday, Oct 2, I will present a new feature in the API which
has to do with documentation of API operations (it's more exciting than it
sounds).
This presentation is important for everyone submitting patches to the
ovirt-engine-api-model, because these patches will be required to use the
documentation infrastructure in the proper manner.
I invite you all to be there, at:
https://bluejeans.com/u/oliel/3879/
Ori
7 years, 1 month
Heads up: post-merge STDCI triggering is coming to GitHub
by Barak Korren
Over the next few days we're going to review and merge a new patch [1] that
will finally provide the capability to trigger STDCI jobs when PRs are
merged in GitHub.
Once this patch is merged, projects in GitHub that have the proper hook
configured, can have 'check-merged' jobs be triggered for them when patches
are merged (Please note that this is a different hook then the one that is
used for triggering on PR events).
Following this we will also review and merge a series of patches [2] which
closes our GitHub functionality gap further by providing the ability to
automatically build merged PRs or pushed commits and submit them to the
change queue for OST testing and publishing.
This essentially means that, once mentioned patches are merged, projects in
GitHub will be able to fully participate in all the oVirt CI processes.
Some aspects of the GitHub functionality are actually a little more
advanced then what is currently available for Gerrit. It is not longer
needed to specify complex YAML in the 'jenkins' repo. Instead, only a
single line is needed to enable the functionality (We left this requirement
because we don't want to blindly run jobs for everything that hits the
webhook). Everything else, including target platforms and versions can no
be specified via a simple YAML file in the project's own source repository.
An example of this yaml file can be seen in the 'ovirt-ansible' project. We
are working on further documentation and will update when its ready.
[1]: https://gerrit.ovirt.org/c/81971/
[2]:
https://gerrit.ovirt.org/q/topic:%2522change-queue-github%2522+(status:op...
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
7 years, 1 month