Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed tab does not count "Too Many Errors, Failing" as Failed WU #348

Open
muziqaz opened this issue May 25, 2021 · 5 comments
Open

Failed tab does not count "Too Many Errors, Failing" as Failed WU #348

muziqaz opened this issue May 25, 2021 · 5 comments

Comments

@muziqaz
Copy link

muziqaz commented May 25, 2021

HI,

I noticed that this sequence:

19:01:34:WARNING:WU01:FS00:FahCore returned an unknown error code which probably indicates that it crashed
19:01:34:WARNING:WU01:FS00:FahCore returned: UNKNOWN_ENUM (-1073740791 = 0xc0000409)
19:01:38:WARNING:WU01:FS00:FahCore returned an unknown error code which probably indicates that it crashed
19:01:38:WARNING:WU01:FS00:FahCore returned: UNKNOWN_ENUM (-1073740791 = 0xc0000409)
19:02:37:WARNING:WU01:FS00:FahCore returned an unknown error code which probably indicates that it crashed
19:02:37:WARNING:WU01:FS00:FahCore returned: UNKNOWN_ENUM (-1073740791 = 0xc0000409)
19:02:37:WARNING:WU01:FS00:Too many errors, failing
19:01:34:WARNING:WU01:FS00:FahCore returned an unknown error code which probably indicates that it crashed
19:01:34:WARNING:WU01:FS00:FahCore returned: UNKNOWN_ENUM (-1073740791 = 0xc0000409)
19:01:38:WARNING:WU01:FS00:FahCore returned an unknown error code which probably indicates that it crashed
19:01:38:WARNING:WU01:FS00:FahCore returned: UNKNOWN_ENUM (-1073740791 = 0xc0000409)
19:02:37:WARNING:WU01:FS00:FahCore returned an unknown error code which probably indicates that it crashed
19:02:37:WARNING:WU01:FS00:FahCore returned: UNKNOWN_ENUM (-1073740791 = 0xc0000409)
19:02:37:WARNING:WU01:FS00:Too many errors, failing

does not add a failed count to Fail tab in main page.
The sequence above is extract from failing WU. It fails with Unknown_ENUM error, restarts, fails again, restarts and if it keeps failing 5 times (or whatever project owner sets it to), it is marked as failed and sent back as bad WU. HFM does not recognize this as failed WU, however WU History section records it as failed WU.
In order for us to easily catch these failures during the day, when we are at work, it would be great if HFM could recognize this sequence as a failure and add Failed count.
So from this compacted sequence that slot should have 2 failed WUs in main HFM window Failed tab. Instead it still shows 0.
Thanks
Regards

@harlam357
Copy link
Owner

Please send me the complete log for this client containing this sequence of events.

@harlam357
Copy link
Owner

Does WU history show the WU result as UNKNOWN_ENUM? The completed and failed counts are sourced from WU history and the failed count query checks for WUs where the result is not FINISHED_UNIT.

@muziqaz
Copy link
Author

muziqaz commented May 26, 2021

log-20210525-225905.txt

Here is a log. I will check out the history once I'm at home.

Regards

@muziqaz
Copy link
Author

muziqaz commented May 26, 2021

Ok, update. It seems that HFM does not even record these failed WUs in the history at all :/

@harlam357
Copy link
Owner

Makes sense since unknown enum is not a definitive result of the WU. Will have to key on "Too many errors, failing".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants