Re: [netvirt-dev] Tempest output for netvirt-csit-hwvtep-{1,3}node-0cmb-1ctl-2cmp-openstack-queens-upstream-stateful-* ?

JamO Luhrsen

On 11/29/19 4:40 AM, Robert Varga wrote:
is reporting failures even when all tests have succeeded.

actually, I think the robot plugin on the main page of this job is just showing the
last results we got from robot. I think that's job 52 which ran back on 9/26. All
the aborts (red dots) are not producing any robot results.

The reason for that is:

tempest results not found in /opt/stack/tempest/.stestr/0
Robot results publisher started...
-Parsing output xml:
hudson.AbortException: No files found in path /w/workspace/netvirt-csit-hwvtep-1node-0cmb-1ctl-2cmp-openstack-queens-upstream-stateful-sodium with configured filemask: output.xml
	at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(
	at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(
	at hudson.FilePath$
	at hudson.remoting.UserRequest.perform(
	at hudson.remoting.UserRequest.perform(
	at hudson.remoting.Request$
	at hudson.remoting.InterceptingExecutorService$
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$
	Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to prd-centos7-robot-2c-8g-24095
		at hudson.remoting.Channel.attachCallSiteStackTrace(
		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(
		at hudson.FilePath.act(
		at hudson.FilePath.act(
		at hudson.plugins.robot.RobotParser.parse(
		at hudson.plugins.robot.RobotPublisher.parse(
		at hudson.plugins.robot.RobotPublisher.perform(
		at hudson.tasks.BuildStepCompatibilityLayer.perform(
		at hudson.tasks.BuildStepMonitor$1.perform(
		at hudson.model.AbstractBuild$AbstractBuildExecution.perform(
		at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(
		at hudson.model.Build$BuildExecution.post2(
		at hudson.model.AbstractBuild$
		at hudson.model.Run.execute(
		at hudson.model.ResourceController.execute(

I don't think that's the root cause here. I think it's this:

01:20:28 ERROR: Package 'more-itertools' requires a different Python: 2.7.5 not in '>=3.4'
01:20:28 Build step 'Execute shell' marked build as failure

We've had that problem before with verify jobs I think. Here's a quick fix:

I have no clue what the job names are, but this one does not have
'-tempest-' in its name -- so I suspect tempest results are expected to
be missing?

right, I think the log collection we have for the openstack jobs just blindly tries to
fetch tempest results, even though we only run tempest in one of the jobs. But, thte
error we get from it doesn't cause the job to abort.



Links: You receive all messages sent to this group.

View/Reply Online (#8430):
Mute This Topic:
Group Owner: netvirt-dev+owner@...
Unsubscribe:  [jluhrsen@...]

Join { to automatically receive all group messages.