| Summary: | Add tracing option for build cycles | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Lars Vogel <Lars.Vogel> |
| Component: | Resources | Assignee: | Lars Vogel <Lars.Vogel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | hoffmann, Lars.Vogel |
| Version: | 4.14 | ||
| Target Milestone: | 4.14 M1 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| See Also: |
https://bugs.eclipse.org/bugs/show_bug.cgi?id=536592 https://git.eclipse.org/r/149822 https://git.eclipse.org/c/platform/eclipse.platform.resources.git/commit/?id=5f82cf63a762295655e90b25c3eae85b8613b09d https://bugs.eclipse.org/bugs/show_bug.cgi?id=551147 |
||
| Whiteboard: | |||
|
Description
Lars Vogel
New Gerrit change created: https://git.eclipse.org/r/149822 Hi Lars, the change looks good to me. If you give me a short hint how to check out that change in my workspace (sorry for the stupid question) I can test it with my example. (In reply to Marc R. Hoffmann from comment #2) > Hi Lars, the change looks good to me. If you give me a short hint how to > check out that change in my workspace (sorry for the stupid question) I can > test it with my example. You have to 1.) clone the repo, see https://git.eclipse.org/r/#/admin/projects/platform/eclipse.platform.resources 2.) Import the affected project 3.) Ctrl+3 Fetch from Gerrit and enter 149822 -> Ctrl+Space 4.) Start a runtime Eclipse via right mouse click on the project -> Run as Eclipse application 5.) Cancel this and go to the tracing tab and activate debug and the new option 6.) Start Eclipse runtime 5.) Import the example into your runtime Eclipse and see Or I just merge so that you can test this in tomorrows I-Build. ;-) Will be in tomorrows I-Build from https://download.eclipse.org/eclipse/downloads/ Marking as fixed, please reopen if logging could be improved Gerrit change https://git.eclipse.org/r/149822 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.resources.git/commit/?id=5f82cf63a762295655e90b25c3eae85b8613b09d Thanks Lars! I can confirm that I can now see cycles in tracing output. (In reply to Marc R. Hoffmann from comment #7) > Thanks Lars! I can confirm that I can now see cycles in tracing output. My pleasure. IMHO all cycles should also be reported via the Problems view, so please update your tickets if you have new information. (In reply to Lars Vogel from comment #8) > (In reply to Marc R. Hoffmann from comment #7) > > Thanks Lars! I can confirm that I can now see cycles in tracing output. > > My pleasure. IMHO all cycles should also be reported via the Problems view, > so please update your tickets if you have new information. No, cycles are not reported (any more). This is the whole point about bug 536592. Please find a very simple reproducer there. |