search

eclipse-ocl / org.eclipse.ocl

Eclipse Public License 2.0
0 stars 0 forks source link

FileNotFoundException below OCLVMExecutor.loadExpression (thrown in FileInputStream.open0) #1960

Open eclipse-ocl-bot opened 1 month ago

eclipse-ocl-bot commented 1 month ago

| --- | --- | | Bugzilla Link | 532591 | | Status | UNCONFIRMED | | Importance | P3 normal | | Reported | Mar 19, 2018 06:19 EDT | | Modified | Mar 24, 2018 04:13 EDT | | Depends on | 529886 | | Reporter | EPP Error Reports |

Description

The following problem was reported via the automated error reporting:

Message: \ java.io.FileNotFoundException: (No such file or directory)\ at java.io.FileInputStream.open0(FileInputStream.java:-2)\ at java.io.FileInputStream.open(FileInputStream.java:195)\ at java.io.FileInputStream.(FileInputStream.java:138)\ at org.eclipse.emf.ecore.resource.impl.FileURIHandlerImpl.createInputStream(FileURIHandlerImpl.java:99)\ at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:360)\ at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1269)\ at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:259)\ at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:274)\ at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:406)\ at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getEObject(ResourceSetImpl.java:220)\ at org.eclipse.ocl.examples.debug.evaluator.OCLVMExecutor.loadExpression(OCLVMExecutor.java:48)\ at org.eclipse.ocl.examples.debug.evaluator.OCLVMExecutor.(OCLVMExecutor.java:74)\ at org.eclipse.ocl.examples.debug.launching.OCLLaunchConfigurationDelegate$1.run(OCLLaunchConfigurationDelegate.java:66)\ at org.eclipse.ocl.examples.debug.vm.utils.SafeRunner$SameThreadRunner.run(SafeRunner.java:31)\ at org.eclipse.ocl.examples.debug.vm.utils.SafeRunner$1.run(SafeRunner.java:24)\ at org.eclipse.ocl.examples.debug.vm.utils.ShallowProcess.run(ShallowProcess.java:40)\ at org.eclipse.ocl.examples.debug.vm.utils.ShallowProcess.run(ShallowProcess.java:31)\ at org.eclipse.ocl.examples.debug.launching.OCLLaunchConfigurationDelegate$3.run(OCLLaunchConfigurationDelegate.java:99)\ at java.lang.Thread.run(Thread.java:748)

Bundles:\ | org.eclipse.emf.ecore | 2.13.0.v20170609-0707 | 2.13.0.v20170609-0707 |\ | org.eclipse.ocl.examples.debug | 2.3.0.v20170522-1753 | 2.3.0.v20170522-1753 |\ | org.eclipse.ocl.examples.debug.vm | 2.3.0.v20170522-1753 | 2.3.0.v20170522-1753 |

Operating Systems:\ | MacOSX | 10.12.6 | 10.12.6 |

The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5aa98570e4b029895a2f71dc for the latest data.

Thank you for your assistance.\ Your friendly error-reports-inbox.

eclipse-ocl-bot commented 1 month ago

By Ed Willink on Mar 19, 2018 06:22

The lack of a file name is not helpful; perhaps AERI strips it. It should be straightforward to find out how such a code path is initiated.

The OCL launch was something of a test aid, so, if nothing else, the diagnostics for a failure need revisiting.

eclipse-ocl-bot commented 1 month ago

By Ed Willink on Mar 24, 2018 04:13

Possibly https://www.eclipse.org/forums/index.php/mv/msg/1092367/1783915/#msg_1783915

Bug 529886 identifies that the DebuggerTests are commented out. Actovating them as part of the Tycho migration caused major confusion.

Hopefully resolving Bug 529886 will resolve this.