Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better message and exit code when merged directory cannot be written #1283

Closed
kevmoo opened this issue Apr 11, 2018 · 0 comments · Fixed by #1343
Closed

Better message and exit code when merged directory cannot be written #1283

kevmoo opened this issue Apr 11, 2018 · 0 comments · Fixed by #1343
Assignees
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures package:build_runner

Comments

@kevmoo
Copy link
Member

kevmoo commented Apr 11, 2018

with Dart SDK 2.0.0-dev.47.0

  • build_runner 0.8.2+2
  • build_web_compilers 0.3.6

Get exit code 1 and output

    [INFO] Initializing inputs
    [INFO] Reading cached asset graph...
    [INFO] Reading cached asset graph completed, took 304ms

    [INFO] Checking for updates since last build...
    [INFO] Checking for updates since last build completed, took 667ms

    [INFO] Running build...
    [INFO] Running build completed, took 17ms

    [INFO] Caching finalized dependency graph...
    [INFO] Caching finalized dependency graph completed, took 118ms

    [WARNING] Skipped creation of the merged output directory.
[e] [SEVERE] Failed after 148ms
[e] Failed to create merged output directories.

Not helpful.

Suggestion:

@jakemac53 jakemac53 added package:build_runner P1 A high priority bug; for example, a single project is unusable or has many test failures labels Apr 11, 2018
@grouma grouma self-assigned this Apr 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures package:build_runner
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants