Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 138596

Summary: Bidi3.2: When running TPTP tests, it hangs up
Product: z_Archived Reporter: Ahmed Farrag <afarrag>
Component: TPTPAssignee: Paul Slauenwhite <paulslau>
Status: CLOSED WORKSFORME QA Contact:
Severity: critical    
Priority: P1 CC: aboualy, camle, kitlo, Lina.Kemmel, mfadl, samwai, steven.wasleski, umarkova
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:
Attachments:
Description Flags
fig1
none
errorlog.txt
none
Test project
none
New English test project
none
ServiceLog.log file
none
displayed SWT error
none
Displayed error message
none
This exception is displayed in the error log view none

Description Ahmed Farrag CLA 2006-04-26 06:18:19 EDT
OS: RHEL 4.0
Build date: 04/24

Steps to recreate the problem:

1) Create Java project
2) Create TPTP manual test
3) Go to main menu Run > Run… 
4) Click on Test Logs tab.  Uncheck Use defaults check box, click Run.

Expected output:
The manual test unit should runs successfully.

Actual output:
When running the TPTP manual test unit it hangs up, and the manual application doesn't show up.

N.B.: This is not a bidi defect however it blocks bidi testing activities
Comment 1 Ahmed Farrag CLA 2006-04-26 08:00:38 EDT
When selecting a deployment with Arabic name, the TPTP manual test unit fails to run, and error message is displayed. fig1 shows the displayed error message and errorlog.txt shows the errors displayed in the error log view.
Comment 2 Ahmed Farrag CLA 2006-04-26 08:05:40 EDT
Created attachment 39515 [details]
fig1
Comment 3 Ahmed Farrag CLA 2006-04-26 08:05:56 EDT
Created attachment 39516 [details]
errorlog.txt
Comment 4 Ahmed Farrag CLA 2006-04-26 08:26:00 EDT
Please discard the previous comment, Sorry for the inconvenience.
Comment 5 Paul Slauenwhite CLA 2006-04-26 15:40:11 EDT
After working with the defect originator, this problem is found in the TPTP-4.2.0-200604210100 TPTP driver and is caused by the Agent Controller when executing TPTP manual and JUnit-based tests.  The test execution hangs 54% (deployment), no test assets are deployed and no test log is generated.  I have asked the defect originator to test using the stable TPTP V4.2.0 build (TPTP-4.2.0-200604131758).  Updating the defect summary accordingly and transfer to the correct component/owner.
Comment 6 Guru Nagarajan CLA 2006-04-26 17:33:41 EDT
Paul,  Was the defect in context reproducible with the i2 driver? (0423 driver)

Changing the component to Platform.Collection since the root cause points to Agent Controller.
Comment 7 Paul Slauenwhite CLA 2006-04-27 07:26:00 EDT
The defect can be reproduced using both the TPTP-4.2.0-200604210100 and TPTP-4.2.0-200604131758 builds.
Comment 8 Samson Wai CLA 2006-04-27 14:51:44 EDT
When you create your deployment, what hostname are you using? From the error log I can see that the hostname contains non-ASCII characters.
Comment 9 Karla Callaghan CLA 2006-04-27 18:10:03 EDT
Assigning to Samson since this is occurring on Linux platform, which is still RAC-based.
Comment 10 Ahmed Farrag CLA 2006-05-02 11:22:06 EDT
(In reply to comment #8)
> When you create your deployment, what hostname are you using? From the error
> log I can see that the hostname contains non-ASCII characters.
> 

The problem also occurs when choosing the default deployment ("local_deployment").
Comment 11 Samson Wai CLA 2006-05-02 11:35:45 EDT
Can you zip up your test project and send it to me?
Comment 12 Ahmed Farrag CLA 2006-05-03 03:54:04 EDT
(In reply to comment #11)

> I am attaching the test project below. I have downloaded and installed the latest TPTP build 200604271249. TPTP maunal test now runs without hanging, but still the manual application doesn't show up. 
Comment 13 Ahmed Farrag CLA 2006-05-03 03:54:52 EDT
Created attachment 40164 [details]
Test project
Comment 14 Karla Callaghan CLA 2006-05-04 12:23:43 EDT
Setting target for i3 as it is under investigation.
Comment 15 Andy Kaylor CLA 2006-05-04 15:03:30 EDT
The secondary process launched by the RemoteSession wasn't be scrubbed.  I changed the default setting for polling to FALSE (as it was in the RAC) so that now we scrub all processes before reading the process list.
Comment 16 Andy Kaylor CLA 2006-05-08 12:40:38 EDT
It looks like there was some kind of hiccup with Bugzilla.  I didn't intend to close this bug, and the comment associated with my closing of the bug belongs with bug 137748.
Comment 17 Samson Wai CLA 2006-05-09 12:04:46 EDT
I have trouble getting the attached project built on my English Windows. Here are some questions/actions:

1. Are you using the RAC or the IAC?

2. If you are using the RAC, edit the file "config/serviceconfig.xml" under the RAC installation directory and change the attribute "loggingLevel" to "DEBUG" and restart the RAC. Rerun the scenario and attach to this bugzilla the file "config/servicelog.log" under the same RAC directory.

3. If you are using the IAC, can you enabled debug from "Window->Preferences..." under "Agent Controller->Integrated Agent Controller" and select "DEBUG" as the level. Then rerun your scenario and attach to this bugzilla the file "<workspace>\.metadata\.plugins\org.eclipse.hyades.execution\tptp_iac.log".

Thanks.
Comment 18 Samson Wai CLA 2006-05-09 12:09:51 EDT
Also, can you try using English as the names of the resources (including project name, test case name, java class names, etc.)? I can see that you are using something like Arabic in the resource names.
Comment 19 Ahmed Farrag CLA 2006-05-09 12:50:29 EDT
(In reply to comment #17)

1) I am using RAC.
2) I have followed the instructions mentioned by you, but the problem still persists even on English locale and using English named resources.

As per your request, I am attaching the "servicelog.log" file and the new project with English named resources.
Comment 20 Ahmed Farrag CLA 2006-05-09 12:51:53 EDT
Created attachment 40758 [details]
New English test project
Comment 21 Ahmed Farrag CLA 2006-05-09 13:17:32 EDT
Created attachment 40766 [details]
ServiceLog.log file
Comment 22 Samson Wai CLA 2006-05-12 09:06:19 EDT
Ahmed, I ended up using my own RHEL 4 AS (switched to Arabic language) to run the test. I cannot run manual test due to a SWT problem (please see bug 115648) but I can run a TPTP JUnit test successfully (with RAC). Please verify if you can run TPTP JUnit tests.

BTW, when I start Eclipse on the Arabic language, the Eclipse workbench still shows English menus, dialogs, etc. Is it correct?
Comment 23 Samson Wai CLA 2006-05-12 15:51:52 EDT
I am returning this since I have no problem running TPTP JUnit Test on Arabic RHEL 4 AS. Please verify. TPTP Manual Test is currently blocked by bug 115648.
Comment 24 Ahmed Farrag CLA 2006-05-14 07:59:00 EDT
(In reply to comment #23)

>Samson,

This bug is not related to the JUnit tests. This bug is opened against the TPTP Manual tests, we haven't faced any problem testing JUnit.
Comment 25 Samson Wai CLA 2006-05-24 13:04:41 EDT
Dup of bug 115648.

*** This bug has been marked as a duplicate of 115648 ***
Comment 26 Samson Wai CLA 2006-05-25 13:42:59 EDT
Paul suggests that this might be somewhat different than bug 115648. Reopen and reassign to Paul.
Comment 27 Paul Slauenwhite CLA 2006-05-25 13:46:29 EDT
Is the test machine SMP?

If not, is this the problem:

http://www.eclipse.org/tptp/home/downloads/releasenotes/releasenotes4_1_0.html#1_7_5
Comment 28 Paul Slauenwhite CLA 2006-05-26 12:44:59 EDT
Please verify https://bugs.eclipse.org/bugs/show_bug.cgi?id=138596#c27.
Comment 29 Ahmed Farrag CLA 2006-05-28 07:48:26 EDT
(In reply to comment #27)

> Is the test machine SMP?
> No, the test machine is not an SMP machine.

> If not, is this the problem:
http://www.eclipse.org/tptp/home/downloads/releasenotes/releasenotes4_1_0.html#1_7_5
>no, the problem is similiar to problem 1.7.8 on the same page except the test machine is not an SMP machine.

>I am attaching the displayed error message as text file for your refrence.

Comment 30 Ahmed Farrag CLA 2006-05-28 07:50:31 EDT
Created attachment 42819 [details]
displayed SWT error
Comment 31 Paul Slauenwhite CLA 2006-05-28 13:17:29 EDT
The error that you are seeing (e.g. gtk_init_check()) is only caused if SWT cannot open a socket to the X server (XOpenDisplay fails), or if the machine is out of memory.  Can you confirm:

 1. The DISPLAY environment variable is set.
 2. The host/port information is correct (e.g. added to /etc/hosts). 
 3. The X server is up.

Comment 32 Ahmed Farrag CLA 2006-06-07 05:55:44 EDT
(In reply to comment #31)
On the RHEL testing machine,
   1. The DISPLAY environment variable is set.
   2. The host/port information is correct.
   3. The X server is up.

and still the problem persists on the following configuration:
eclipse-SDK-3.2RC7-linux-gtk 
emf-sdo-xsd-SDK-2.2.0RC5
tptp.sdk-TPTP-4.2.0-200606021600
tptpdc.all_platforms-TPTP-4.2.0-200605251528

I am attaching the displayed error message, so please advise.
Comment 33 Ahmed Farrag CLA 2006-06-07 05:56:58 EDT
Created attachment 43694 [details]
Displayed error message
Comment 34 Ahmed Farrag CLA 2006-06-07 05:58:35 EDT
Created attachment 43695 [details]
This exception is displayed in the error log view
Comment 35 Paul Slauenwhite CLA 2006-06-07 07:10:27 EDT
(In reply to comment #33)

The Manual Test View uses the Eclipse Standard Widget Toolkit (SWT) Browser. When running the Manual Test View on Linux, Mozilla v1.4 to v1.6 GTK2 is required.  This error is caused by SWT being unable to locate the Mozilla libraries.
Comment 36 Ahmed Farrag CLA 2006-06-08 04:26:51 EDT
The error message states that these libraries are missing from the lib directory of RAC. I had to get these missing libraries from another application and add it manually to the LIB directory. After applying this workaround, I was able to run the manual test unit. The RAC build should include all the required libraries to make the TPTP component functional correctly. 

Anyway, closing this defect as it is not a bidi releated one. 
Comment 37 Paul Slauenwhite CLA 2006-06-08 08:11:33 EDT
(In reply to comment #36)

These are the Mozilla libraries referenced from the SWT libraries which are shipped in the Agent Controller.  As such, it is the responsibility of the user to have the correct version of Mozilla/Firefox installed in their machine (see http://www.eclipse.org/swt/faq.php#browserplatforms).  We do have a defect to provide a dialog informing the user of the problem (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=144777) and I have opened defect  https://bugs.eclipse.org/bugs/show_bug.cgi?id=145983 to add an entry to the TPTP readme.
Comment 38 Ahmed Farrag CLA 2006-06-08 09:02:37 EDT
(In reply to comment #37)
> (In reply to comment #36)

Paul,

I have went through " http://www.eclipse.org/swt/faq.php#browserplatforms "
before adding my last comment, and I am sure that I am using the correct version of Mozilla/Firefox. Anyway my last comment was meant to be FYI and I am sure that you will take the appropriate action.