DAGMan still producing incorrect gotEvents warning

Description

In gittrac #7548 we fixed a bug where a warning message was incorrectly appearing in the DAGMan log:

Warning for node <nodeName>: unexpected _gotEvents value for proc 0: 0!

However we've had reports that the bogus warning is still showing up, but now under different circumstances than it used to. It would seem there are some different code paths that we didn't notice last time.

The bug is related to a bunch of code that tracks node time metrics but was disabled 7 years ago with a DISABLE_NODE_TIME_METRICS flag. Instead of adding more confusing logical paths to some long-abandoned code, I'm just going to rip it out and set the desired _gotEvents flags somewhere else.

Done

Due date

None

Time remaining

4h

Assignee

Mark Coatsworth

Fix versions

Priority

Minor

Components

Reporter

Mark Coatsworth

Time tracking

0m

Actual Start

Oct 06, 2020, 5:29 PM
Configure