search for: tests_basic

...e.g. some other file descriptor, or to a file passed via env or whatever). > This way, it might make sense for vdsm to always pass these vars, continue > logging all stdout/err, and log/keep debug/trace logs only on errors. This now happened again: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/565/ https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/565/artifact/exported-artifacts/test_logs/basic-suite-master/lago-basic-suite-master-host-1/_var_log/vdsm/vdsm.log 2020-11-09 01:05:42,031-0500 INFO (jsonrpc/4) [api.host] FINISH getAllVmIoTuneP...

On Tue, Oct 13, 2020 at 06:45:42PM +0300, Nir Soffer wrote: > I think this is the right solution - when virt-something tool fails, > it should log the reason for the failure - the error that caused the > tool to fail. I'm not sure this is easy to do as the failing code > run inside a special VM. Maybe the code running in the VM should log > the output in a machine readable way,

On Tue, Oct 13, 2020 at 07:56:29PM +0300, Nir Soffer wrote: > On Tue, Oct 13, 2020 at 7:15 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > On Tue, Oct 13, 2020 at 06:45:42PM +0300, Nir Soffer wrote: > > > I think this is the right solution - when virt-something tool fails, > > > it should log the reason for the failure - the error that caused the

...r, or to a file passed via env or whatever). > > This way, it might make sense for vdsm to always pass these vars, continue > > logging all stdout/err, and log/keep debug/trace logs only on errors. > > This now happened again: > > https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/565/ > > https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/565/artifact/exported-artifacts/test_logs/basic-suite-master/lago-basic-suite-master-host-1/_var_log/vdsm/vdsm.log > > 2020-11-09 01:05:42,031-0500 INFO (jsonrpc/4) [api.host] FI...

On Tue, Oct 13, 2020 at 8:40 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > On Tue, Oct 13, 2020 at 07:56:29PM +0300, Nir Soffer wrote: > > On Tue, Oct 13, 2020 at 7:15 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > > > On Tue, Oct 13, 2020 at 06:45:42PM +0300, Nir Soffer wrote: > > > > I think this is the right solution - when

On Mon, Oct 12, 2020 at 9:05 AM Yedidyah Bar David <didi@redhat.com> wrote: > > Hi all, > > On Mon, Oct 12, 2020 at 5:17 AM <jenkins@jenkins.phx.ovirt.org> wrote: > > > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ > > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/479/ > > Above failed with: > > https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/479/testReport/junit/basic-suite-master.test-scenarios/004_basic...

On Tue, Oct 13, 2020 at 7:15 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > On Tue, Oct 13, 2020 at 06:45:42PM +0300, Nir Soffer wrote: > > I think this is the right solution - when virt-something tool fails, > > it should log the reason for the failure - the error that caused the > > tool to fail. I'm not sure this is easy to do as the failing code >