v8/test/message/fail/modules-star-conflict1.out

*%(basename)s:7: SyntaxError: The requested module contains conflicting star exports for name 'a'
import {a} from "../../mjsunit/modules-skip-7.js";
        ^
SyntaxError: The requested module contains conflicting star exports for name 'a'
[modules] Improve error messages. For instance, when an import cannot be resolved, actually point at the corresponding import statement. BUG=v8:1569 Review-Url: https://codereview.chromium.org/2451153002 Cr-Commit-Position: refs/heads/master@{#40594} 2016-10-26 15:09:47 +00:00			`*%(basename)s:7: SyntaxError: The requested module contains conflicting star exports for name 'a'`
Split message tests in failing and non-failing This way, we can also check the return code of d8. We currently have a bug (6981) which makes failing tests not being detected, even though the failure message is (sometimes) being printed. After this refactoring, we can write tests for our mjsunit test functions. R=machenbach@chromium.org Bug: v8:6981 Change-Id: I0aa0abcb0f9a4f622a1e1d1a4d826da1e6eb4f07 Reviewed-on: https://chromium-review.googlesource.com/737991 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#48951} 2017-10-25 09:23:34 +00:00			`import {a} from "../../mjsunit/modules-skip-7.js";`
[modules] Improve error messages. For instance, when an import cannot be resolved, actually point at the corresponding import statement. BUG=v8:1569 Review-Url: https://codereview.chromium.org/2451153002 Cr-Commit-Position: refs/heads/master@{#40594} 2016-10-26 15:09:47 +00:00			`^`
			`SyntaxError: The requested module contains conflicting star exports for name 'a'`