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

Incorrect calls to getrusage() #10

Closed
PeterCoghlan opened this issue Apr 12, 2017 · 4 comments
Closed

Incorrect calls to getrusage() #10

PeterCoghlan opened this issue Apr 12, 2017 · 4 comments
Assignees
Labels
BUG The issue describes likely incorrect product functionality that likely needs corrected. (Duplicate) An issue was already created for the described problem. Please also refer to the other issue. (*MOVED*) (the original issue was moved into a different issue)

Comments

@PeterCoghlan
Copy link

Please take a look at issue #217 on the hercules-390/hyperion issues page as the same code is present in this fork.

While it looks likely that the issue arises only on Linux or other unix platforms and probably does not arise on Windows platforms, I suspect there is a desire here to ensure things work correctly on all platforms and that use is not made of undocumented features.

@Fish-Git
Copy link
Member

Hi Peter!

Yes, I saw that. I monitor hercules-390/hyperion's issues so I bookmarked the relevant posts so I could address the issue in my Hyperion as well.

There have been several other changes made to hercules-390/hyperion over the past month or so too, which I have not yet gotten around to applying to my Hyperion yet due to not only personal life issues(*) but also due to my not having finished yet with the changes I'm currently working on. It's one of those changes that started out simple but then snowballed into a much larger and more complicated change due to discovered bugs leading to yet other bugs, etc. Attention to detail is important to me and the closer I look at things the more problems I'm seeing. As a result, my "simple" change is taking much longer than expected. (You know what they say: "The last 1% of a project takes 99% of the time and effort.")

Anyway... once I finish what I'm working on I will return to addressing one by one all of the most recently raised issues, yours (getrusage) being one of them.

In the mean time I appreciate your having taken the time to report this to me (my hyperion) and ask for your continued patience as I work through my personal and Hercules issues as quickly as I can.

Thanks.


(*) My wife became very ill and was taken to the hospital last week. She spent 6 days there slowly getting better and was discharged just this past Sunday. She is now spending another week convalescing at home and hopes to return back to work on Monday. Her physical and emotional well being of course takes precedence over anything/everything else in my life. She is my world. My own needs are a distant second, and Hercules? ... well, the difference between their respective importance is lightyears apart.

@Fish-Git Fish-Git self-assigned this Jul 28, 2017
@Fish-Git Fish-Git added the BUG The issue describes likely incorrect product functionality that likely needs corrected. label Dec 5, 2017
@Fish-Git Fish-Git added (Duplicate) An issue was already created for the described problem. Please also refer to the other issue. IN PROGRESS... I'm working on it! (Or someone else is!) labels Jan 20, 2018
@Fish-Git
Copy link
Member

This issue is a duplicate of issue #79 "Incorrect CPU Timer - Now Corrected".

@Fish-Git
Copy link
Member

Fish-Git commented Jan 20, 2018

This issue is resolved by (or rather, will be resolved by) pull request #79 "Incorrect CPU Timer - Now Corrected", which I have already merged into my test respository.

Once I am finished with what I'm currently working on, the fix (pull request #79 "Incorrect CPU Timer - Now Corrected") will appear in this publicly visible fish-git/hyperion repository and this issue will be closed.

@Fish-Git
Copy link
Member

UPDATE: This issue is now a duplicate of issue #83 "CPU Timer Fix Stopping 2nd Level VM ABENDs" (not issue #79).

I am closing this issue.

The originally reported problem will be eventually fixed by issue #83.

@Fish-Git Fish-Git added (*MOVED*) (the original issue was moved into a different issue) and removed IN PROGRESS... I'm working on it! (Or someone else is!) labels Feb 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG The issue describes likely incorrect product functionality that likely needs corrected. (Duplicate) An issue was already created for the described problem. Please also refer to the other issue. (*MOVED*) (the original issue was moved into a different issue)
Projects
None yet
Development

No branches or pull requests

2 participants