Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jwt-dev] WG: JWT build question

Wow thanks Mickaël (& happy new year) for the insightful tip, and nice work Chris !

Regards,
Marc

Christian Saad a écrit :

Hi Mickael, all,

thanks for your help. I took a look at the start and noticed that there is indeed another dialog which is opened and therefore blocks the testing.

For some reason the workflow file is copied from

/opt/public/technology/jwt/tester/test-eclipse/eclipse/dropins/eclipse/plugins/org.eclipse.jwt.tests_0.7.0.v20100111-0955-I/org/eclipse/jwt/tests

to

/opt/public/technology/jwt/tester/test-eclipse/eclipse/configuration/org.eclipse.osgi/bundles/251/1/.cp/org/eclipse/jwt/tests (???)

but not the corresponding view file, so my own consistency check mechanism sabotaged me here ;)

So I can finally announce that the automatic builds are working again. Just look at them green dots in all their glory :)

Regards,

Chris

*Von:* Mickael Istria [mailto:mickael.istria@xxxxxxxxxxxxxx]
*Gesendet:* Montag, 11. Januar 2010 14:24
*An:* Christian Saad
*Betreff:* Re: JWT build question

Hello Christian


I hope you had a good start into the new year!

Thanks, I hope you are already enjoying 2010 too!


The Hudson build is now running again except for the “testOpenEditor” call which just causes the script to hang indefinitely. I’m not sure what causes this and have no idea how I can debug the call on the server (it works locally) as I’m not able to find any log entries for the runtime workspace. Maybe you’ve encountered a similar problem somewhere and can give me a hint?

This is usually due to the fact that the test opens a dialog (for example to ask something to user, or to warn him about an error). Then the dialog opens, and Eclipse expects user to close it. But in case of automated test execution, there is no user and the dialog remains open and the test does not stop. We have spent a lot of time to avoid pop-ups in our tests at BonitaSoft, it could be the case for JWT too.

Have you tried to run this test locally or from an installed version of JWT to check whether this test works? AFAIRemember it only opens a new JWT diagram and checks that it opens JWT editor. A reason could be that the target file of the test (the one that is to be created by the new process action) already exists, and JWT opens a dialog to ask whether existing file must be overwritten. In such case you should ensure that test are executed in a clean workspace.

Another thing you could do to have faster feedback on such error is to set a timeout on the ant task that runs the test, so that if test don't end withing a dozen of minutes, you make the test process fail (and the build will be red).

Good luck!

--

*Mickael Istria
**R&D Engineer*

BonitaSoft - Open your processes <http://www.bonitasoft.com>

	


email : mickael.istria@xxxxxxxxxxxxxx <mailto:mickael.istria@xxxxxxxxxxxxxx>


This message and any attachment (the "message") is intended solely for the addressees and is confidential. If you receive this message by mistake, please delete it and notify the sender immediately. Any use not in accordance with its purpose, any out-spread or disclosure, either as a whole or partially, is prohibited except with formal approval. Internet cannot guarantee the integrity of this message, therefore BonitaSoft will not be liable for the message if modified.

------------------------------------------------------------------------

_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev


Back to the top