Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Search results

  • &lt;overholt&gt; something that makes thigns *so* easy to package that our jobs there are not very difficult<br /> ...nichoj_work&gt; scsibear, last time I checked, there were some things that failed against 1.5<br />
    28 KB (5,050 words) - 13:52, 17 January 2007
  • It is quite simple to find out when jobs, including those owned by others, are scheduled, run, awoken, and finished. ...<tt>done</tt> event is sent regardless of whether the job was cancelled or failed to complete, and the result status in the job change event will tell you ho
    1,018 bytes (146 words) - 16:35, 27 March 2012
  • ...round work, make sure to have that indicated in the Progress view (via the Jobs API). This will help people trust the tool, since their Eclipse could be g ...ifications of incoming changes, and indicates when a query synchronization failed. It is also the anchor for managing the offline support, since only the ta
    62 KB (9,005 words) - 13:39, 20 June 2019
  • ...the state of the model, and provide the user interface elements that allow jobs to be launched and controlled. The ''runtime controller'' is responsible fo ...icular physical computer system. For example, host A may allow interactive jobs to be run directly using the MPICH2 runtime system, or batched via the LSF
    27 KB (4,092 words) - 14:44, 9 May 2008
  • ...res within the failure trace part for analysing why a test case might have failed. You have real great navigation possibilities and comparisation support fro ...development, you must carefully indentify the output part belonging to the failed test case and copy the failure stack trace from there to you RSE developmen
    19 KB (2,828 words) - 09:24, 2 January 2007
  • ...or Bamboo continuous integration server builds and create Mylyn tasks from failed builds. *Create tasks from failed builds
    51 KB (7,131 words) - 10:23, 17 July 2019
  • ** Simulation Engine (org.eclipse.stem.jobs) ...e>true</code>. An assertion failure then pinpoints precisely the test that failed.
    60 KB (9,124 words) - 01:32, 30 April 2016
  • ...d reports not encouraged. Mik will resolve bug#152869 - creating bugs from failed unit tests for 2.1 * Rob: related bug#185805 (timestamp bug) and bug#186939 (blocked jobs)
    28 KB (3,945 words) - 12:16, 17 June 2008
  • ...ED || <strike>[Tests] Move test suite of o.e.ui.tests and migrate progress jobs to JUnit 4</strike> ...untime || normal || Lars.Vogel || FIXED || <strike>Update org.eclipse.core.jobs to Java 8 to use lambdas and to use @FunctionalInterface annotation</strike
    139 KB (16,498 words) - 05:21, 12 May 2016
  • More information on creating and scheduling jobs can be found in the [[EPF Wiki Installation Guide]]. ...>"<p>Hi #{cadmin.name},</p><p>The zip file \"#{d}/#{entry}</p>\"</nowiki> failed to auto_deploy because a Baseline Process with the exact same derived folde
    20 KB (3,269 words) - 15:14, 24 October 2019
  • ...e Eclipse IDE or a drop of the EAR/WAR into the '''deploy''' directory has failed on both a 1.5 and 1.6 JRE. at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    9 KB (1,248 words) - 10:18, 8 April 2010
  • == Q: I get the error "Failed to execute command: ompi_info -a --parseable" when I use the Open MPI targe If the Active Jobs view is empty when you know jobs are running on the system, perhaps the commands queried from the monitoring
    24 KB (3,889 words) - 09:56, 14 March 2019
  • Different jobs have been created on CDT's Hudson instance to test the different configurat * '''debug-tests-master-all-gdb-versions''' - This jobs runs the local DSF-GDB tests of the master branch using all GDB versions.
    29 KB (4,539 words) - 15:11, 22 January 2020
  • ...e https://ci.eclipse.org/swtbot . Here is a quick description of available jobs: ...: +1 if everything is fine, -1 in case of a compile error, build error, or failed test
    13 KB (2,020 words) - 11:11, 21 May 2021
  • 13:36:10 11:36:10 [ERROR] Dependency license check failed. Some dependencies need to be vetted. bazel test //... --jobs=4
    79 KB (12,107 words) - 07:16, 4 December 2023
  • For the first workflow the console output of a failed execution is as follows. First the BeforeStep writes its output, next the e org.eclipse.core.runtime.CoreException: d956bfa5-5b7b-458b-ba67-cbcc9e665cc0: FAILED
    63 KB (8,811 words) - 18:32, 22 March 2013
  • ...clipse.gmt.modisco] to its Workspace (<code>/opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-nightly/workspace</code>). If the build was started automatical ...tures from the head of the trunk into <code>/opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-nightly/workspace/MoDiscoTree</code>
    16 KB (2,291 words) - 04:00, 21 July 2010
  • ...lds framework, provides a Builds view to monitor status, notifications for failed build and makes build results accessible from the IDE. That enables develop Management and creation of build jobs and configuration of Hudson servers is out of scope of the project.
    3 KB (413 words) - 12:46, 16 February 2011
  • *batch jobs running and waiting in queues<br> *system state (failed components, ...)<br>
    18 KB (3,045 words) - 10:50, 10 February 2011
  • * Wait until all jobs are finished ...project, and members of the Callisto-dev group can launch EMF Facet build jobs from Hudson.
    17 KB (2,644 words) - 05:16, 30 May 2012

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Back to the top