-
Notifications
You must be signed in to change notification settings - Fork 44
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
[VC_1.11.0] Failed to parse SPECjvm metrics from results because index was outside the bounds of the array if run more than 2 times. #194
Comments
Hi @xuwangfe thanks for reporting, acknowledged, looking into it. |
It would help me a lot if you could help package the results folder so that I can debug right away. Otherwise my run will finish in a couple hours so I will check tomorrow. |
Sorry for that i couldn't sent the data results to you due to the policy limitation. |
|
Could you install a new OS in the host environment directly and try again? The failure rate is 100% in my side. |
Thank you @xuwangfe , I did exactly #.4 with a fresh VM with Ubuntu2004. The fact SPECjvm2008.002.txt is empty is the problem. Our parser failed to parse because the file is empty. If you can't share the log files, would you be open to run SPECjvm without VC and see what happens? The command looks like this Regex, you need to adjust GCThreads and memory you are using. VC uses 85% of total memory by default. |
Sorry I couldn't unblock you right now without being able to reproduce the issue. However I still have a question, did you remove the SPECjvm2008.001-011 folders? Because looks like when you manually ran it, it started from SPECjvm2008.012 instead of SPECjvm2008.001, which makes me think you didn't delete the whole VC_1.11 when reinstalling. Please confirm you removed the whole /specjvm.2008.0.0/results and then reran. Thank you. |
|
Hi xuwangfe, when you copy to VC_1.11_old or VC_1.11_new, you are also copying over the results folder which has the empty result log. So doesn't matter if you are copying, VC will still be looking at that empty result file first. You want that removed. Please run this Let me know if you are open to a Zoom/Teams meeting where I help resolve this quickly. |
The steps which i tried were list as below:
I think this is as same as the rm. Please feel free to open Teams meeting, thanks. |
I would be interested to know the "ls /home/VC_1.11_new/content/linux-x64/packages/specjvm.2008.0.0/results/" after the installation, it should be empty after the unzip. May I know your timezone? I would try to accommodate your working hour. |
Beijing time and 9:00 - 17:00 is OK for me |
What's a good email to reach you? Or you could send it to virtualclient@microsoft.com if you prefer to send it privately. |
Describe the bug
Failed to parse SPECjvm metrics from results because index was outside the bounds of the array if run more than 2 times.
To Reproduce
Steps to reproduce the behavior:
Failed on both Ubuntu 20.04 & 22.04 & redhat8.2, failure rate 100%
Expected behavior
Parse passed for multiple SPECjvm iterations.
Screenshots
See as the attachment.
Additional context
![Failed_Specjvm](https://private-user-images.githubusercontent.com/95741724/277533521-9e7dabb4-3ffe-4b05-8b77-772d38e4d84c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2MTU5OTQsIm5iZiI6MTczOTYxNTY5NCwicGF0aCI6Ii85NTc0MTcyNC8yNzc1MzM1MjEtOWU3ZGFiYjQtM2ZmZS00YjA1LThiNzctNzcyZDM4ZTRkODRjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE1VDEwMzQ1NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRiNjVmNDUyYWFiNDMxNGU1Y2UxNzc3OTU5ZmQzZmEzNWYyYzQyNzU5YWRmYjljYTYzOGIwNzY0Y2QyNjdhZjgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.zUcJWKTJf6QLGRlRlfxKKUVEkN5n6mLkLBq6qfx8Kmk)
Only 1st time result could be parsed successfully;
It will be still failed if delete the old VC version and then enable a new one;
The text was updated successfully, but these errors were encountered: