JDK-8145656 : The case : "jnlp_file/updateElement/index.html#index_AlwaysPromptRunYes" test Passed but in log it is showing Failed.
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 8,9
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux_ubuntu
  • CPU: x86
  • Submitted: 2015-10-16
  • Updated: 2016-01-12
  • Resolved: 2016-01-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9Resolved
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
Testsuite name: TCK JNLP 
TestSuite Version : TCK-JNLP-8.0.20/b13
Test name(s):jnlp_file/updateElement/index.html#index_AlwaysPromptRunYes
Product(s) tested: JDK 8u72 b02(32bit) 
OS/architecture:Ubuntu15.04 x86

Error log file : http://scaaa008.us.oracle.com:9502/runs/01134/1134490.ManualSubmit/1134490.ManualSubmit-1/workDir/jnlp_file/updateElement/index_AlwaysPromptRunYes.jtr

Reproducible: Always 
Reproducible on machine: evergreen machine
[If Sometimes] Also reproducible on machine: 

Is it a Regression: Yes 
[If Regression] Regression introduced in release/build: JDK 8u72 b01 
Test result on the last GAed release for this train: Pass(JDK 8u66 b18 with same OS:Pass) 
Test results on other JDK: JDK 8u72 b01 (Failed as the same issue) 

Is it a platform specific issue: No (JDK 8u72 b02 with mac 10.10 x64:Failed as the same issue 
                                                    JDK 8u72 b02 with win7 sp1 x64:Failed as the same issue) 
[If platform specific issue] Is it a new (previously unsupported) OS/browser/mode testing: 
[If new configuration testing] Issue specific to execution mode or OS/browser version: 

ERROR :  Failed. The test status log "updateElement2004: Passed. Initial-Version test cases: 1; all passed updateElement2004: Passed. Initial-Version OKAY " does not contain string "Passed. Updated-Version"

Steps to reproduce: 
1. Install the test JDK 8u72 b02(32bit) (download from http://jre.us.oracle.com/java/re/jdk/8u72/promoted/ea/b02/bundles/) locate at /root/tck
2. Download workspace from http://jre.us.oracle.com/java/re/jnlp_tck/8.0.20/promoted/latest/bundles/jnlp_tck-8_0_20.jar
3. Use java -jar jnlp_tck-8_0_20.jar then put TCK-JNLP-8.0.20 under /root/tck
4. Download attachment file jnlp-WinXPPro.zip. uncompress it to /root/tck
5. Download attachment file jnlp8.0.20.jtx, put it under /root/tck/TCK-JNLP-8.0.20/lib 
6. Run the script javatest.sh under /root/jnlp-WinXPPro/AT-03.26-12.46.15/RUN
7 Press the "Press this button to continue" button of case instructions window
 
Actual behavior: 
Step 8:we click "Press this button to continue" button of the case instructions window, the test failed. But after we have done the aurora, it belongs to the passed list.

The following case has the same issue:
jnlp_file/updateElement/index.html#index_AlwaysPromptUpdateYes

Comments
According to Artem above, this is a dupe of JDK-8141527 and has therefor been fixed in 7u101 b01, 8u72 b10, and JDK9 b96 Closing as a dupe.
12-01-2016

moved this bug into JDK based on the above Artem's analysis.
17-12-2015

The two cases have the same issue on ubuntu 15.10 x86 with JDK 9b94(32bit). The workspace we use tck-jnlp_9.0/b03. "jnlp_file/updateElement/index_AlwaysPromptRunYes" "jnlp_file/updateElement/index_AlwaysPromptUpdateYes"
01-12-2015

The test doesn't seem to be correct. If you have it passed in the released TCK, OK then - it passes according to the provided status.
24-11-2015

Is this JBS issue correctly classified as a TCK issue?
20-11-2015

The two cases have the same issue on Windows 7 SP1 x64 with JDK 7u95b07. "jnlp_file/updateElement/index_AlwaysPromptRunYes" "jnlp_file/updateElement/index_AlwaysPromptUpdateYes" The log for win7: http://aurora-ds3.us.oracle.com:9502/runs/01152/1152086.ManualSubmit/1152086.ManualSubmit-1/workDir/jnlp_file/updateElement/index_AlwaysPromptRunYes.jtr http://aurora-ds3.us.oracle.com:9502/runs/01152/1152086.ManualSubmit/1152086.ManualSubmit-1/workDir/jnlp_file/updateElement/index_AlwaysPromptUpdateYes.jtr
06-11-2015

Reverified - The two cases have the same issue on solaris10-x86 with JDK 7u95b06. "jnlp_file/updateElement/index_AlwaysPromptRunYes" "jnlp_file/updateElement/index_AlwaysPromptUpdateYes"
29-10-2015

The two cases have the same issue on win7-sp1-x86 and solaris10-x86 with JDK 7u95b06. RULE "jnlp_file/updateElement/index_AlwaysPromptRunYes" any any RULE "jnlp_file/updateElement/index_AlwaysPromptUpdateYes" any any The log for win7: http://aurora.ru.oracle.com/slot-gw/1144628.ManualSubmit-1/workDir/jnlp_file/updateElement/index_AlwaysPromptRunYes.jtr http://aurora.ru.oracle.com/slot-gw/1144628.ManualSubmit-1/workDir/jnlp_file/updateElement/index_AlwaysPromptUpdateYes.jtr The log for solaris: http://aurora.ru.oracle.com/slot-gw/1144632.ManualSubmit-1/workDir/jnlp_file/updateElement/index_AlwaysPromptRunYes.jtr http://aurora.ru.oracle.com/slot-gw/1144632.ManualSubmit-1/workDir/jnlp_file/updateElement/index_AlwaysPromptUpdateYes.jtr
29-10-2015

Shilpi, we have updated the attached .jtr, you can refer to index_AlwaysPromptRunYes-new.jtr.
26-10-2015

It seems functionality wise test case is working fine ( no issues with the product). Pass 1: Initial version of the application should be downloaded and run Pass 2: Updated version of the application should be downloaded and run after the appropriate prompt. There is a issue with the test. Getting the "Failed" from the console no matter we are pressing "YES" or "NO". Test is working fine but in logs it is showing Failed. So moving the bug into JCK (test). Will update the bug after investigation.
23-10-2015

Yes, Aurora reads the status from the .jtr and in this case "result: Passed. OKAY". so it is parsing it as "Passed." Tony please update your attached .jtr. It has "test result: Failed. The jnlp client exit code is -1". It could mislead the developer. jnlp-WinXPPro-8.zip has wrong configuration (JDK 6).
23-10-2015

Shilpi, did you follow the exact steps in this bug? From your previous two comments, you got the same test results as: Failed. The test status log "updateElement2004\: Passed. Initial-Version test cases\: 1; all passed updateElement2004\: Passed. Initial-Version OKAY " does not contain string "Passed. Updated-Version" We want to hightlight again: 1) the test case itself to check java functionaity is passed and we clicked "Yes" button from the attached screenshot. In the .jtr file, you can see : ---- updateElement2004: Passed. Initial-Version test cases: 1; all passed updateElement2004: Passed. Initial-Version OKAY result: Passed. OKAY ---- 2) we got the "failed" msg from the console(pls see the attached screenshot) and same msg in the last line of that .jtr filehttp://scaaa008.us.oracle.com:9502/runs/01134/1134490.ManualSubmit/1134490.ManualSubmit-1/workDir/jnlp_file/updateElement/index_AlwaysPromptRunYes.jtr. 3) Next Aurora generated the report (mightly) based on the .jtr file, read the "passed" msg, but not the last "failed". Then has pass in auror system. We think this issue should come from the test workspace or case or tools. Why the case java functionanity is ok and we click "Yes", it still generates that "failed" msg. It is not jdk issue.
23-10-2015

Attaching failed .jtr
22-10-2015

Hi Tony, I am unable to reproduce this issue with this "result: Failed. The jnlp client exit code is -1" I am getting following execStatus=Failed. The test status log "updateElement2004\: Passed. Initial-Version test cases\: 1; all passed updateElement2004\: Passed. Initial-Version OKAY " does not contain string "Passed. Updated-Version" Your bug title is misleading, actually there are 2 issues- 1. Issue with aurora parsing. 2. Test case is failing. We should do the following- 1. Please create a INTJDK bug specifying the issue where " component" = aurora and "subcomponent"= reporting. 2. Re-run this test case in your environment and upload the .jtr in JBS as well as in aurora.
22-10-2015

Hi Tony, Can you please check regression? Please update the following information ASAP. Is it a Regression: Yes/No/Not sure(add explicit comment why not sure and what you did so far to find if the issues is regression or not and what build it was introduced in) [If Regression] Regression introduced in release/build: Test result on the last GAed release for this train: Pass/Fail (Explicitly mention release number) [if Fail] Test result on FCS: Pass/Fail (if applicable, explicitly mention here 1.5.0 FCS , 1.6.0 b105, 1.7.0 b148 or 1.8.0 b132) Is it a platform specific issue: Yes/No [If platform specific issue] Is it a new (previously unsupported) OS/browser/mode testing: Yes/No [If new configuration testing] Issue specific to execution mode or OS/browser version:
21-10-2015