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

Bug 348244

Summary:	Move run.valgrind=no to build-server profile
Product:	[Tools] Linux Tools	Reporter:	Andrew Overholt <overholt>
Component:	Valgrind	Assignee:	Roland Grunberg <rgrunber>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	akurtakov
Version:	unspecified
Target Milestone:	1.0
Hardware:	PC
OS:	Linux
Whiteboard:

Description Andrew Overholt

2011-06-03 12:50:49 EDT

At present, our pom.xml for some of the Valgrind plugin tests is set to never run the test suites that require Valgrind itself to be installed.  It would be better if this were done in the build-server profile and not by default.  Note that one can still run these test suites locally by launching from within Eclipse.

Post-Indigo.

Comment 1 Alexander Kurtakov

2012-04-19 08:07:17 EDT

Roland, would you please check whether this is still needed? I think I have done something similar not so long ago but someone more familiar with valgrind taking a look would definetely help.

Comment 2 Roland Grunberg

2012-04-19 10:06:51 EDT

This property exists in ValgrindTestsPlugin.java, SYSTEM_PROPERTY_RUN_VALGRIND. It is set to "no" in the actual top-level pom that manages the running of tycho-surefire. It will just simulate the running of Valgrind with pre-generated log files. In the case that his property isn't set valgrind will actually run and generate the files. Resolving as fixed.