Re: [linuxtools-dev] Dataviewers Feature

[Aleksandar Kurtakov]

I saw the problem now. We were missing the dataviewers in the nightly update 
site but when testing it was satisfied by older luna contributions. I reverted 
the commit removing the feature.

Alexander Kurtakov
Red Hat Eclipse team

- Original Message -
> From: "Aleksandar Kurtakov" 
> To: "Linux Tools developer discussions" 
> Sent: Tuesday, April 8, 2014 7:49:50 AM
> Subject: Re: [linuxtools-dev] Dataviewers Feature
> 
> - Original Message -
> > From: "Greg Watson" 
> > To: "Linux Tools developer discussions" 
> > Sent: Tuesday, April 8, 2014 12:11:57 AM
> > Subject: Re: [linuxtools-dev] Dataviewers Feature
> > 
> > I want to be able to reuse GmonView, but it subclasses AbstractSTDataView.
> > The only way I can currently do this is to clone the dataviewers and
> > dataviewers.charts plugins. Previously, I could just build against the p2
> > repo and it would pick up the feature.
> 
> This should still work as long because all the bundles are still in the
> repository. It's just the feature that is missing. Have you tried replacing
> references to the feature with references to the bundles?
> 
> Alexander Kurtakov
> Red Hat Eclipse team
> 
> > 
> > Greg
> > 
> > On Apr 7, 2014, at 4:43 PM, Aleksandar Kurtakov 
> > wrote:
> > 
> > > Short answer - https://git.eclipse.org/r/#/c/23365/ .
> > > What do you need it for? I wouldn't mind bringing it back if someone
> > > steps
> > > in to document and verify its actual reusability.
> > > All the bundles are still there, just not the feature to prevent its sole
> > > installation as the feature adds no real functionality and others
> > > features
> > > bring the relevant bundles in.
> > > 
> > > Alexander Kurtakov
> > > Red Hat Eclipse team
> > > 
> > > - Original Message -
> > >> From: "Greg Watson" 
> > >> To: "linuxtools-dev@eclipse.org developer discussions"
> > >> 
> > >> Sent: Monday, April 7, 2014 11:12:55 PM
> > >> Subject: [linuxtools-dev] Dataviewers Feature
> > >> 
> > >> Hi,
> > >> 
> > >> For some reason the master build
> > >> (http://download.eclipse.org/linuxtools/updates-nightly) seems to be
> > >> missing
> > >> the dataviewers feature. Does anyone know why this would be?
> > >> 
> > >> Thanks,
> > >> Greg
> > >> ___
> > >> linuxtools-dev mailing list
> > >> linuxtools-dev@eclipse.org
> > >> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
> > >> 
> > > ___
> > > linuxtools-dev mailing list
> > > linuxtools-dev@eclipse.org
> > > https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
> > 
> > ___
> > linuxtools-dev mailing list
> > linuxtools-dev@eclipse.org
> > https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
> > 
> ___
> linuxtools-dev mailing list
> linuxtools-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
> 
___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

[linuxtools-dev] Gerrit forward only

[Aleksandar Kurtakov]

Hi everyone, 
What do you think of switching our gerrit configuration from cherry-pick to 
forward only ? This would remove the need for resetting your local clone after 
every review pushed and/or later merge/reset. It will not introduce any major 
drawback in my opinion but I would like to hear others.

Alexander Kurtakov
Red Hat Eclipse team

___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

[linuxtools-dev] [Hudson] Build failed in Hudson: master-java8 #7

[hudsonbuild]

See 

Changes:

[Alexander Kurtakov] Revert "Remove dataviewers feature."

[Alexander Kurtakov] Extend JFace LabelProvider instead of implementing 
ILabelProvider.

[Alexander Kurtakov] perf: Fix recentlry introduced warnings.

[Alexander Kurtakov] profiling.launch: Remove redundant modifiers.

--
[...truncated 12839 lines...]
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
resolve dependencies for project 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core.tests:eclipse-test-plugin:3.0.0-SNAPSHOT:
 The following artifacts could not be resolved: 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.parser:jar:3.0.0-SNAPSHOT,
 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core:jar:3.0.0-SNAPSHOT,
 org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.ui:jar:3.0.0-SNAPSHOT: 
Could not find artifact 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT
at 
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
... 22 more
Caused by: org.sonatype.aether.resolution.DependencyResolutionException: The 
following artifacts could not be resolved: 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.parser:jar:3.0.0-SNAPSHOT,
 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core:jar:3.0.0-SNAPSHOT,
 org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.ui:jar:3.0.0-SNAPSHOT: 
Could not find artifact 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT
at 
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
at 
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
... 23 more
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: The 
following artifacts could not be resolved: 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.parser:jar:3.0.0-SNAPSHOT,
 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core:jar:3.0.0-SNAPSHOT,
 org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.ui:jar:3.0.0-SNAPSHOT: 
Could not find artifact 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT
at 
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
at 
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
at 
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
... 24 more
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not 
find artifact 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT
at 
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:528)
... 26 more
[ERROR] Failed to execute goal on project 
org.eclipse.linuxtools.gdbtrace.ui.tests: Could not resolve dependencies for 
project 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.ui.tests:eclipse-test-plugin:3.0.0-SNAPSHOT:
 The following artifacts could not be resolved: 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.ctf:or

Re: [linuxtools-dev] Gerrit forward only

[Roland Grunberg]

> Hi everyone,
> What do you think of switching our gerrit configuration from cherry-pick to
> forward only ? This would remove the need for resetting your local clone
> after every review pushed and/or later merge/reset. It will not introduce
> any major drawback in my opinion but I would like to hear others.

I think it may be possible to avoid that issue by setting your merge strategy
to rebase (can be done per-branch, per-repo, or globally). I think it's easy
enough now to keep commits up to date, and not doing so with multiple commits
touching the same project *could* cause regressions. That would be one reason
to prefer forward merges.

I guess maybe there's less garbage collection needed to be done by git in a
forward merge since it uses the same commit object in a forward-merge
(unlike cherry-pick). We have had issues in the past with our repos needing
'git gc' run on them, but I would assume this is automated for all
repositories by now.

I don't have any strong preferences on this, but I could be missing something.

Cheers,
-- 
Roland Grunberg
___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

Re: [linuxtools-dev] Gerrit forward only

[Marc Khouzam]

> -Original Message-
> From: linuxtools-dev-boun...@eclipse.org [mailto:linuxtools-dev-
> boun...@eclipse.org] On Behalf Of Roland Grunberg
> Sent: Tuesday, April 08, 2014 9:55 AM
> To: Linux Tools developer discussions
> Subject: Re: [linuxtools-dev] Gerrit forward only
> 
> > Hi everyone,
> > What do you think of switching our gerrit configuration from
> > cherry-pick to forward only ? This would remove the need for resetting
> > your local clone after every review pushed and/or later merge/reset.

CDT also uses cherry-pick, so I am curious to understand the advantage
of moving to fast forward only.  I'm not clear from the above what
use case it will improve.

> > It will not introduce any major drawback in my opinion but I would like to
> hear others.

The obvious one is that it forces to rebase even the smallest changes if they
are not reviewed right away.  With Gerrit's 'Rebase' button, this is not such
a big concern though.

> 
> I think it may be possible to avoid that issue by setting your merge strategy 
> to
> rebase (can be done per-branch, per-repo, or globally). I think it's easy
> enough now to keep commits up to date, and not doing so with multiple
> commits touching the same project *could* cause regressions. That would
> be one reason to prefer forward merges.

To be really safe about properly testing a patch on the exact version it will
be merged on, I see your point here.  We've never run into such a problem
though, as far as I know.

BR,

Marc
___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

Re: [linuxtools-dev] Gerrit forward only

[Alexandre Montplaisir]

On 04/08/2014 04:11 AM, Aleksandar Kurtakov wrote:

Hi everyone,
What do you think of switching our gerrit configuration from cherry-pick to 
forward only ? This would remove the need for resetting your local clone after 
every review pushed and/or later merge/reset. It will not introduce any major 
drawback in my opinion but I would like to hear others.


From what I understand, forward-only actually *forces* you to 
rebase/repush every time you want to put a commit into master if master 
has changed since the last time the commit was put on Gerrit. 
Considering the relatively high rate of change in master, this sounds 
like a pain ;)


I'd recommend not committing anything in your local master branch, but 
instead doing the commits in separate local branches (branches like 
"fix-bug-1234", "add-feature-x", etc.) When the patch is ready, push to 
Gerrit from that branch. And when the commit is merged into master, you 
can delete the local branch. Only update local master via "git pull". 
That's the workflow I use and I find it works quite well.


Cheers,
Alexandre



Alexander Kurtakov
Red Hat Eclipse team




___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

Re: [linuxtools-dev] Tracing TMF for debugging

[Bernd Hufmann]

Hi Francis

If you import the attached custom text parser into TMF then you can load 
the traces (generated by TmfCoreTracer) into TMF and analyze them with TMF.
See integrated LTTng User Guide chapter "Custom Parsers" on how to 
import and manage custom parsers.


/Bernd

On 04/07/2014 05:02 PM, Patrick Tasse wrote:

Hi Francis,

Usually I turn this on in Run/Debug Configurations, select your JUnit 
Plug-in Test configuration, then under the Tracing tab, enable tracing 
for org.eclipse.linuxtools.tmf.core plug-in and select the four check 
boxes.



On Mon, Apr 7, 2014 at 4:55 PM, Francis Giraldeau 
mailto:francis.girald...@gmail.com>> wrote:


I'm trying to trace TMF for debugging purposes. I found the
class TmfCoreTracer and some general instructions [1]. Here is the
.options file I created:

org.eclipse.linuxtools.tmf.core/component=true
org.eclipse.linuxtools.tmf.core/request=true
org.eclipse.linuxtools.tmf.core/signal=true
org.eclipse.linuxtools.tmf.core/event=true

I copied the file in the test workspace and various source
directory (project root, under org.eclipse.tmf.core plug-in) and
the tracing is not enabled. It seems that the file is not taken
into account. Where should this file be located when running a
unit test?

Thanks!

Francis

[1]:

https://wiki.eclipse.org/FAQ_How_do_I_use_the_platform_debug_tracing_facility%3F

___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org 
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev




___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev





-MM-dd HH:mm:ss.SSS


\s*\[(\d*\.\d*)\]\s*\[TID=(\d*)\]\s*\[(SIG|CMP|EVT|REQ)\]\s*(.*)











___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

[linuxtools-dev] [Hudson] Build failed in Hudson: master-java8 #8

[hudsonbuild]

See 

Changes:

[Alexander Kurtakov] systemtap: Axe useless old code.

[Alexander Kurtakov] systemtap: Remove unused method parameters.

[Patrick Tasse] tmf: Bug 424964: Drag and dropping a linked trace doesn't 
create a link

[Patrick Tasse] tmf: Fix linked property inadvertently removed by 35b4320

--
[...truncated 12848 lines...]
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
resolve dependencies for project 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core.tests:eclipse-test-plugin:3.0.0-SNAPSHOT:
 The following artifacts could not be resolved: 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.parser:jar:3.0.0-SNAPSHOT,
 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core:jar:3.0.0-SNAPSHOT,
 org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.ui:jar:3.0.0-SNAPSHOT: 
Could not find artifact 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT
at 
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
... 22 more
Caused by: org.sonatype.aether.resolution.DependencyResolutionException: The 
following artifacts could not be resolved: 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.parser:jar:3.0.0-SNAPSHOT,
 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core:jar:3.0.0-SNAPSHOT,
 org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.ui:jar:3.0.0-SNAPSHOT: 
Could not find artifact 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT
at 
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
at 
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
... 23 more
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: The 
following artifacts could not be resolved: 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.parser:jar:3.0.0-SNAPSHOT,
 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core:jar:3.0.0-SNAPSHOT,
 org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.ui:jar:3.0.0-SNAPSHOT: 
Could not find artifact 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT
at 
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
at 
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
at 
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
... 24 more
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not 
find artifact 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT
at 
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:528)
... 26 more
[ERROR] Failed to execute goal on project 
org.eclipse.linuxtools.gdbtrace.ui.tests: Could not resolve dependencies for 
project 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.ui.tests:eclipse-test-plugin:3.0.0-SNAPSHOT:
 The following artifacts could not be resolved: 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.

Re: [linuxtools-dev] [Hudson] Build failed in Hudson: master-java8 #5

[Marc-André Laperle]

It seems relates to this:
"In previous releases, some implementations of
Collection.removeAll(Collection) and retainAll(Collection) would
silently ignore a null parameter if the collection itself was empty. As
of this release, collections will consistently throw a
NullPointerException if null is provided as a parameter."

http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.html#A999387

I'm looking into possible solutions (upgrading Antlr?).

Marc-Andre

On 14-04-08 12:57 AM, Aleksandar Kurtakov wrote:
> This is a test job compiling against Java 8. Please keep an eye on it and 
> please fix your modules to compile on Java 8 properly.
> Currently it fails in ctf.parser.
>
> Alexander Kurtakov
> Red Hat Eclipse team
>
> - Original Message -
>> From: hudsonbu...@eclipse.org
>> To: linuxtools-dev@eclipse.org
>> Sent: Tuesday, April 8, 2014 1:30:03 AM
>> Subject: [linuxtools-dev] [Hudson] Build failed in Hudson: master-java8 #5
>>
>> See 
>>
>> Changes:
>>
>> [Patrick Tasse] tmf: Add source location to trace properties
>>
>> [Bernd Hufmann] tmf rcp: Disallow opening trace viewer with the same
>> workspace
>>
>> [Alexandre Montplaisir] tmf: Beautify TmfExperimentContext's API
>>
>> [Roland Grunberg] Display program output in real time.
>>
>> --
>> [...truncated 14287 lines...]
>> [INFO]
>> [INFO] --- tycho-packaging-plugin:0.20.0:validate-id (default-validate-id) @
>> org.eclipse.linuxtools.cdt.libhover.devhelp.feature ---
>> [INFO]
>> [INFO] --- tycho-packaging-plugin:0.20.0:validate-version
>> (default-validate-version) @
>> org.eclipse.linuxtools.cdt.libhover.devhelp.feature ---
>> [INFO]
>> [INFO] --- jacoco-maven-plugin:0.7.0.201403182114:prepare-agent (pre-test) @
>> org.eclipse.linuxtools.cdt.libhover.devhelp.feature ---
>> [INFO] argLine set to
>> -javaagent:
>> [INFO]
>> [INFO]
>> [INFO] Forking Linux Tools Libhover Core Tests Plug-in 1.0.0-SNAPSHOT
>> [INFO]
>> [INFO]
>> [INFO] --- tycho-packaging-plugin:0.20.0:build-qualifier
>> (default-build-qualifier) @ org.eclipse.linuxtools.cdt.libhover.tests ---
>> [INFO] The project's OSGi version is 1.0.0.201404072229
>> [INFO]
>> [INFO] --- tycho-packaging-plugin:0.20.0:validate-id (default-validate-id) @
>> org.eclipse.linuxtools.cdt.libhover.tests ---
>> [INFO]
>> [INFO] --- tycho-packaging-plugin:0.20.0:validate-version
>> (default-validate-version) @ org.eclipse.linuxtools.cdt.libhover.tests ---
>> [INFO]
>> [INFO] --- jacoco-maven-plugin:0.7.0.201403182114:prepare-agent (pre-test) @
>> org.eclipse.linuxtools.cdt.libhover.tests ---
>> [INFO] tycho.testArgLine set to
>> -javaagent:
>> [INFO]
>> [INFO]
>> [INFO] Forking Linux Tools LTTng Parent 3.0.0-SNAPSHOT
>> [INFO]
>> [INFO]
>> [INFO] --- jacoco-maven-plugin:0.7.0.201403182114:prepare-agent (pre-test) @
>> linuxtools-lttng-parent ---
>> [INFO] argLine set to
>> -javaagent:
>> [INFO]
>> [INFO]
>> [INFO] Forking Linux Tools CTF Parser Plug-in 3.0.0-SNAPSHOT
>> [INFO]
>> [INFO]
>> [INFO] --- tycho-packaging-plugin:0.20.0:build-qualifier
>> (default-build-qualifier) @ org.eclipse.linuxtools.ctf.parser ---
>> [INFO] The project's OSGi version is 3.0.0.201404072229
>> [INFO]
>> [INFO] --- tycho-packaging-plugin:0.20.0:validate-id (default-validate-id) @
>> org.eclipse.linuxtools.ctf.parser ---
>> [INFO]
>> [INFO] --- tycho-packaging-plugin:0.20.0:validate-version
>> (default-validate-version) @ org.eclipse.linuxtools.ctf.parser ---
>> [INFO]
>> [INFO] --- jacoco-maven-plugin:0.7.0.201403182114:prepare-agent (pre-test) @
>> org.eclipse.linuxtools.ctf.parser ---
>> [INFO] argLine set to
>> -javaagent:

Re: [linuxtools-dev] Tracing TMF for debugging

[Francis Giraldeau]

Thanks, it's good to know, it was hidden in plain sight! I will update the
corresponding wiki pages accordingly.

Cheers,

Francis


2014-04-08 12:08 GMT-04:00 Bernd Hufmann :

>  Hi Francis
>
> If you import the attached custom text parser into TMF then you can load
> the traces (generated by TmfCoreTracer) into TMF and analyze them with TMF.
> See integrated LTTng User Guide chapter "Custom Parsers" on how to import
> and manage custom parsers.
>
> /Bernd
>
>
> On 04/07/2014 05:02 PM, Patrick Tasse wrote:
>
> Hi Francis,
>
> Usually I turn this on in Run/Debug Configurations, select your JUnit
> Plug-in Test configuration, then under the Tracing tab, enable tracing for
> org.eclipse.linuxtools.tmf.core plug-in and select the four check boxes.
>
>
> On Mon, Apr 7, 2014 at 4:55 PM, Francis Giraldeau <
> francis.girald...@gmail.com> wrote:
>
>>  I'm trying to trace TMF for debugging purposes. I found the
>> class TmfCoreTracer and some general instructions [1]. Here is the .options
>> file I created:
>>
>>  org.eclipse.linuxtools.tmf.core/component=true
>>  org.eclipse.linuxtools.tmf.core/request=true
>> org.eclipse.linuxtools.tmf.core/signal=true
>> org.eclipse.linuxtools.tmf.core/event=true
>>
>>  I copied the file in the test workspace and various source directory
>> (project root, under org.eclipse.tmf.core plug-in) and the tracing is not
>> enabled. It seems that the file is not taken into account. Where should
>> this file be located when running a unit test?
>>
>>  Thanks!
>>
>>  Francis
>>
>>  [1]:
>> https://wiki.eclipse.org/FAQ_How_do_I_use_the_platform_debug_tracing_facility%3F
>>
>> ___
>> linuxtools-dev mailing list
>> linuxtools-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
>>
>>
>
>
> ___
> linuxtools-dev mailing 
> listlinuxtools-dev@eclipse.orghttps://dev.eclipse.org/mailman/listinfo/linuxtools-dev
>
>
>
> ___
> linuxtools-dev mailing list
> linuxtools-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
>
>
___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

[linuxtools-dev] [Hudson] Build failed in Hudson: master-java8 #9

[hudsonbuild]

See 

Changes:

[Patrick Tasse] tmf: Refactor bookmarks file handling

[Alexander Kurtakov] systemtap: Removed unudse methods.

--
[...truncated 12847 lines...]
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
resolve dependencies for project 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core.tests:eclipse-test-plugin:3.0.0-SNAPSHOT:
 The following artifacts could not be resolved: 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.parser:jar:3.0.0-SNAPSHOT,
 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core:jar:3.0.0-SNAPSHOT,
 org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.ui:jar:3.0.0-SNAPSHOT: 
Could not find artifact 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT
at 
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
... 22 more
Caused by: org.sonatype.aether.resolution.DependencyResolutionException: The 
following artifacts could not be resolved: 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.parser:jar:3.0.0-SNAPSHOT,
 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core:jar:3.0.0-SNAPSHOT,
 org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.ui:jar:3.0.0-SNAPSHOT: 
Could not find artifact 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT
at 
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
at 
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
... 23 more
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: The 
following artifacts could not be resolved: 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.parser:jar:3.0.0-SNAPSHOT,
 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core:jar:3.0.0-SNAPSHOT,
 org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.tmf:org.eclipse.linuxtools.tmf.ui:jar:3.0.0-SNAPSHOT: 
Could not find artifact 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT
at 
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
at 
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
at 
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
... 24 more
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not 
find artifact 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT
at 
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:528)
... 26 more
[ERROR] Failed to execute goal on project 
org.eclipse.linuxtools.gdbtrace.ui.tests: Could not resolve dependencies for 
project 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.ui.tests:eclipse-test-plugin:3.0.0-SNAPSHOT:
 The following artifacts could not be resolved: 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.core:jar:3.0.0-SNAPSHOT, 
org.eclipse.linuxtools.ctf:org.eclipse.linuxtools.ctf.parser:jar:3.0.0-SNAPSHOT,
 
org.eclipse.linuxtools.gdbtrace:org.eclipse.linuxtools.gdbtrace.core:jar:3.0.0-SNAPSHOT,
 org.eclipse.linuxtools.t

[linuxtools-dev] 2.2.1 source tarball download url points to "2.2.0" named tarball

[Tony Jones]

http://download.eclipse.org/linuxtools/2.2.1-sources/

The link on this page points to:  
http://www.eclipse.org/downloads/download.php?file=/linuxtools/2.2.1-sources/org.eclipse.linuxtools-2.2.0.tar.bz2

I've not tried to download it and see if it actually contains 2.2.1, also if I 
instead download: 
http://www.eclipse.org/downloads/download.php?file=/linuxtools/2.2.1-sources/org.eclipse.linuxtools-2.2.1.tar.bz2
  I get file unavailable error.

tony
___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

Re: [linuxtools-dev] 2.2.1 source tarball download url points to "2.2.0" named tarball

[Aleksandar Kurtakov]

I would recommend getting the tarball from cgit. 
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/snapshot/org.eclipse.linuxtools-2.2.1.tar.bz2
 
For the last few releases we were coping it to downloads area for "compat" 
reasons and the 2.2.1-sources is purely a mistake so I removed it and fixed our 
downloads page to point to cgit. 
Thanks for spotting it.

Alexander Kurtakov
Red Hat Eclipse team

- Original Message -
> From: "Tony Jones" 
> To: "Linux Tools developer discussions" 
> Sent: Wednesday, April 9, 2014 4:45:22 AM
> Subject: [linuxtools-dev] 2.2.1 source tarball download url points to "2.2.0" 
> named tarball
> 
> http://download.eclipse.org/linuxtools/2.2.1-sources/
> 
> The link on this page points to:
> http://www.eclipse.org/downloads/download.php?file=/linuxtools/2.2.1-sources/org.eclipse.linuxtools-2.2.0.tar.bz2
> 
> I've not tried to download it and see if it actually contains 2.2.1, also if
> I instead download:
> http://www.eclipse.org/downloads/download.php?file=/linuxtools/2.2.1-sources/org.eclipse.linuxtools-2.2.1.tar.bz2
> I get file unavailable error.
> 
> tony
> ___
> linuxtools-dev mailing list
> linuxtools-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
> 
___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev