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.

Sign up for GitHub

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

Jump to bottom

Resurrect accounting information at job end records #190

Closed
konvpalto opened this issue Oct 8, 2013 · 2 comments
Closed

Resurrect accounting information at job end records #190

konvpalto opened this issue Oct 8, 2013 · 2 comments

Comments

@konvpalto
Copy link

USESAVEDRESOURCES governs if we will take consumed resources from the
saved information inside the job itself, but consumed resources from
job obituary request must be used unconditionally.

This is a regression from
dbbe2f9
where blindly fixing GCC warnings resulted in functionality loss.

Patch is available,
http://computing.kiae.ru/~rea/torque-2.5.13-resurrect-accounting-information-in-job-end-records.patch

It is now being tested on our Torque farm and shown no problems up to date, while resources_used.* records reappeared in accounting and server logs.
@konvpalto
Copy link
Author

This fix is for 2.5.13, hadn't looked at other branches.

dbeer pushed a commit that referenced this issue Jan 31, 2014
Fix github issue #190. resources used in accounting had a regression …
105a816 
…creep in. Thanks to konvpalto for reporting the issue and supplying a patch.
@dbeer
Copy link

dbeer commented Jan 31, 2014

8246d96..105a816 HEAD -> 2.5-dev

@dbeer dbeer closed this as completed Jan 31, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@konvpalto @dbeer