Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 405456 - Allow tests to disable auto-save job
Summary: Allow tests to disable auto-save job
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.3   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 4.3 M7   Edit
Assignee: Paul Webster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-11 07:30 EDT by Paul Webster CLA
Modified: 2013-05-17 10:39 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Webster CLA 2013-04-11 07:30:06 EDT
From Bug 405356 comment #12

+100 for not having a feature in default eclipse that forces long wait on jobs finishing.

I believe we are not the only one that has test that wait for the jobs to finish to avoid conflicts.

We also disable certain jobs explicitly to avoid this (i.e. build and validations are often cause of issues when running tests because they are not build for speed/unitests)

Using plugin_customization.ini is really not a sustainable way to disable this - we would have to put a plugn_customization.ini into every test plugin - configured it in Tycho AND in eclipse (even worse) to be used.

Could we please get a system property or other way of ensuring this job is not going to be present since it is *not* something that makes sense to have during test runs.
Comment 1 Paul Webster CLA 2013-04-11 07:35:42 EDT
See https://git.eclipse.org/r/11810

Should be able to disable the tests with -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true

PW
Comment 2 Max Rydahl Andersen CLA 2013-04-11 10:39:34 EDT
*excellent*
Comment 4 Paul Webster CLA 2013-05-17 10:39:18 EDT
in 4.3.0.I20130516-2200

PW