Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): virtio-win-prewhql-21 How reproducible: 100% Steps to Reproduce: 1.Start Win2k3_64 bit guest 2.start running common Scenario Stress with DiskIO Actual results: During job running .NET Framework has Unhandled exception .and job failed in the end Expected results: Additional info:
Created attachment 560168 [details] .Net Framework exception log during job running
Created attachment 560170 [details] Screen Dump when Net Framework exception during job running
Created attachment 560174 [details] job log(failed) in DTM *note* there are 2 log files for this job Common_Scenario_Stress_With_DiskIO.wsf.wtl and diskIO.wtl .all failed logs in diskIO.wtl
Created attachment 560175 [details] job log (passed) from DTM Thanks to my *wrong* configuration which that after guest s4 ,I did not resume it immediately while I resume it after 8hours . the job passed this time. I am sure my operation for this job is wrong although I made the job pass. Attach the *passed* log for your reference.
Hi All, I installed new image for windows 2003 64 bits and submitted the job mentioned in the bug to DTM,neither virtio-win-prewhql-22 nor virtio-win-prewhql-23 could help me to reproduce the bug.I also tried with vnc and spice but it still could not reproduce the issue. Thanks.Any issues please let me know. Best Regards, Min
(In reply to comment #12) > Hi All, > I installed new image for windows 2003 64 bits and submitted the job > mentioned in the bug to DTM,neither virtio-win-prewhql-22 nor > virtio-win-prewhql-23 could help me to reproduce the bug.I also tried with vnc > and spice but it still could not reproduce the issue. > Thanks.Any issues please let me know. > > Best Regards, > Min Thank you, Min. I believe that it was a DTM client's problem. Maybe something went wrong during its installation, or it was just a .Net framework problem. In any case, glad to know that it is not reproducible on a fresh install. Best regards, Vadim.
Based on comment #12 ,close this bug
(In reply to comment #13) > (In reply to comment #12) > > Hi All, > > I installed new image for windows 2003 64 bits and submitted the job > > mentioned in the bug to DTM,neither virtio-win-prewhql-22 nor > > virtio-win-prewhql-23 could help me to reproduce the bug.I also tried with vnc > > and spice but it still could not reproduce the issue. > > Thanks.Any issues please let me know. > > > > Best Regards, > > Min > > Thank you, Min. > > I believe that it was a DTM client's problem. Maybe something went wrong during > its installation, or it was just a .Net framework problem. > In any case, glad to know that it is not reproducible on a fresh install. > > Best regards, > Vadim. Hi Vadim, I have to re-open the bug as the bug can be reproduced via virtio-win-prewhql-0.1-24 at this time.Actually,I've tired the driver on the two images that were the *same* one mentioned in comments 12,it was very easily for reproducing. The issue was,as far as I'm concerned,while the .net Framework error popped up the progress bar was frozen in guest and time recorder on it cannot reduce time,so the job cannot stop in time except for stopping it manually. Furthermore,I also found if I closed the testing dailog in the guest,it meant stopping testing manually.At last,the job's status was changed *passed*.But these actions should be forbidden for whql.So we can not take it as *passed*. It was the following info,which filtered the job.When I tried the issue with virtio-win-prewhql-0.1-23,the job could fail *automatically* but it could be filtered with the below info as well. Maybe,this result was what we expected .(Just my opinio) Anyway,QE will continue to investigate the issue.Welcome to any suggestion for us and any issues please let me know.Thank you very much. Best Regard, Min -----------------info------------------------------------------------------- Pass[2247] Fail[0] -:|:- Common Scenario Stress With DiskIO [ Infrastructure Logs ] - Pass[1] Fail[0] -:|:- RunJob - Common_Scenario_Stress_With_DiskIO Pass[1] Fail[0] -:|:- Register DiskIO COM Assembly Log: NotRequired Pass[45] Fail[0] -:|:- Execute Device_Status_Check Script Log: Present [ Device_Status_Check.wsf.wtl ] Applied Errata Issue Description Applied Nodes Applied Errors Filtered Failures -[Filter Number:3505 Row:354 ] - Device_Status_Script, as used by Common Scenario Stress with DiskIO, neglects to provide the IODevices parameter and mistakenly checks the status of ALL devices. 92 of 95 0 0 Issue Resolution A workaround exists by using a system with all devices working properly, however there are situations where that workaround is not feasible, so this errata will filter any errors, but only as it is used by Common Scenario Stress with DiskIO. This filter does not apply to any other task involved in Common Scenario Stress with DiskIO. Expiration Date This filter expires on 12/01/2012. After that date, this filter will no longer apply and the test must pass without this filter applied. For Errata filters, WHQL reserves the right to change this date without notice. Best Regards, Min
Mike and Min, We would like to move this bug to 6.4 With the new image it seems to be less severe than what It used to be when it was marked as a blocker. What do you think?
Created attachment 572960 [details] win2k3-64bit-block-cpk
(In reply to comment #16) > Mike and Min, > We would like to move this bug to 6.4 > With the new image it seems to be less severe than what It used to be when it > was marked as a blocker. > What do you think? Hi, Ronen According to comment #19 . We can pass WHQL w/o this bug fixed . Seems that I shouldn't raise "rhel6.4.0 ?" flag ,Sorry for that and feel free to move to the right component. Thanks, Mike
Re-open this Bug since We hit it now and it is almost a tesblocker
(In reply to comment #25) > Re-open this Bug since We hit it now and it is almost a tesblocker Hi Mike, Could you please post the most recent cpk file? Thank you, Vadim.
(In reply to comment #26) > (In reply to comment #25) > > Re-open this Bug since We hit it now and it is almost a tesblocker > > Hi Mike, > Could you please post the most recent cpk file? > Thank you, > Vadim. I am still trying to workaround it and job keeps running now .I will provide cpk file once the job finished Mike
Created attachment 658630 [details] Failed job logs Vadim, CPK file attached ,pls review it Thanks, Mike
(In reply to comment #28) > Created attachment 658630 [details] > Failed job logs > > Vadim, CPK file attached ,pls review it > > Thanks, > Mike Hi Mike, Can we be sure that the following DTM filter was applied? https://sysdev.microsoft.com/en-us/Hardware/EC/ECDetails.aspx?id=2871 Thank you, Vadim.
(In reply to comment #29) > (In reply to comment #28) > > Created attachment 658630 [details] > > Failed job logs > > > > Vadim, CPK file attached ,pls review it > > > > Thanks, > > Mike > > Hi Mike, > Can we be sure that the following DTM filter was applied? > https://sysdev.microsoft.com/en-us/Hardware/EC/ECDetails.aspx?id=2871 > Thank you, > Vadim. Hi, Vadim Every times when do use filter ,it shows : Failure Information Issue Description Applied Nodes-[Filter Number:4005 Row:451 ] - The Common Scenario Stress with DiskIO test fails intermittently with exceptions on a variety of configurations. We are investigating the problems to ensure the test is working correctly.1 of 1Issue ResolutionAny failure of the test is acceptable. Any bluescreens caused by the test should be investigated. If errors are not resolved by filters, please use manual errata 2286 in the readme file. We needed to make a manual errata to complement the filter as these filters may not always work. There are some cases we cannot filter. One of the scenarios we cannot filter is where copy logs task fails. We don't want to filter in this scenario as the task was added to other jobs for test security to ensure those tests would fail when the job log is missing. May We use Manual Errata 2286 to submit this job to MSFT ? Thanks, Mike
(In reply to comment #30) > (In reply to comment #29) > > (In reply to comment #28) > > > Created attachment 658630 [details] > > > Failed job logs > > > > > > Vadim, CPK file attached ,pls review it > > > > > > Thanks, > > > Mike > > > > Hi Mike, > > Can we be sure that the following DTM filter was applied? > > https://sysdev.microsoft.com/en-us/Hardware/EC/ECDetails.aspx?id=2871 > > Thank you, > > Vadim. > > Hi, Vadim > Every times when do use filter ,it shows : > > Failure Information > Issue Description Applied Nodes-[Filter Number:4005 Row:451 ] - The Common > Scenario Stress with DiskIO test fails intermittently with exceptions on a > variety of configurations. > We are investigating the problems to ensure the test is working correctly.1 > of 1Issue ResolutionAny failure of the test is acceptable. Any bluescreens > caused by the test should be investigated. If errors are not resolved by > filters, please use manual errata 2286 in the readme file. We needed to make > a manual errata to complement the filter as these filters may not always > work. There are some cases we cannot filter. One of the scenarios we cannot > filter is where copy logs task fails. We don't want to filter in this > scenario as the task was added to other jobs for test security to ensure > those tests would fail when the job log is missing. > > May We use Manual Errata 2286 to submit this job to MSFT ? Hi Mike. I believe yes. At least there is no BSOD and we have cpk file. Best regards, Vadim. > Thanks, > Mike
(In reply to comment #31) > (In reply to comment #30) > > (In reply to comment #29) > > > (In reply to comment #28) > > > > Created attachment 658630 [details] > > > > Failed job logs > > > > > > > > Vadim, CPK file attached ,pls review it > > > > > > > > Thanks, > > > > Mike > > > > > > Hi Mike, > > > Can we be sure that the following DTM filter was applied? > > > https://sysdev.microsoft.com/en-us/Hardware/EC/ECDetails.aspx?id=2871 > > > Thank you, > > > Vadim. > > > > Hi, Vadim > > Every times when do use filter ,it shows : > > > > Failure Information > > Issue Description Applied Nodes-[Filter Number:4005 Row:451 ] - The Common > > Scenario Stress with DiskIO test fails intermittently with exceptions on a > > variety of configurations. > > We are investigating the problems to ensure the test is working correctly.1 > > of 1Issue ResolutionAny failure of the test is acceptable. Any bluescreens > > caused by the test should be investigated. If errors are not resolved by > > filters, please use manual errata 2286 in the readme file. We needed to make > > a manual errata to complement the filter as these filters may not always > > work. There are some cases we cannot filter. One of the scenarios we cannot > > filter is where copy logs task fails. We don't want to filter in this > > scenario as the task was added to other jobs for test security to ensure > > those tests would fail when the job log is missing. > > > > May We use Manual Errata 2286 to submit this job to MSFT ? > > Hi Mike. > I believe yes. At least there is no BSOD and we have cpk file. > > Best regards, > Vadim. > OK ,I will use Manual Errata 2286 for submission instead of using HCK Mike
We will close this bug once MSFT accepts the submission (using Errata 2286). No further work planned for now.
Closing, since mike managed to pass WHQL, and we switch to HCK in RHEL6.5.