Project

General

Profile

Bug #2737

AMD OpenCl failes release build in complex tests

Added by Paul Bauer 14 days ago. Updated 13 days ago.

Status:
Feedback wanted
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Affected version - extra info:
Affected version:
Difficulty:
uncategorized
Close

Description

The release build linked here failed two of the complex tests for AMD OpenCl: http://jenkins.gromacs.org/view/Release/job/Release_workflow_master/170/consoleFull

00:42:32.391 [[gcc-8, gpuhw=amd, opencl-1.2, release]] FAILED. Check checkforce.out (1 errors) file(s) in orientation-restraints for orientation-restraints

00:42:32.391 [[gcc-8, gpuhw=amd, opencl-1.2, release]] FAILED. Check checkpot.out (4 errors), checkforce.out (3 errors) file(s) in tip4p_continue for tip4p_continue

History

#1 Updated by Paul Bauer 14 days ago

  • Target version changed from 2019-beta2 to 2019-beta3

bumped to next beta

#2 Updated by Szilárd Páll 14 days ago

  • Status changed from New to Feedback wanted

As far as I can tell, the AMD OpenCL build runs on the ancient AMD slave which we should not use anymore -- it has an very outdated software stack (and hardware) which may or may not function correctly.

Hence, I'm not sure this is a bug, but I'll wait with closing.

That console output is rather confusing, BTW; is there a way to get separate outputs from separate builds?

#3 Updated by Mark Abraham 13 days ago

Yes, you can get console log for individual builds if you look through the "Pipeline steps" but it's not exactly convenient. Thus
http://jenkins.gromacs.org/job/Release_workflow_master/173/execution/node/107/log/?consoleFull shows that the new and GPU slave also has an issue. That issue seems more like OpenCL builds not being able to jit, but we'll need to inspect the mdrun.out files.

Also available in: Atom PDF