Skip to content

Another build break #7

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

Open
vlascik opened this issue Jul 10, 2019 · 7 comments
Open

Another build break #7

vlascik opened this issue Jul 10, 2019 · 7 comments

Comments

@vlascik
Copy link

vlascik commented Jul 10, 2019

Yesterday's fix worked, simple reproduction app now builds, but my larger app fails with a different error:

  ember-cli:command `build:fallback` command running `Build` task +3ms
- Building  broccoli-stew:rename [Funnel] from: .js to: .fb.js +0ms
  broccoli-stew:rename [Funnel] from: .html to: .fb.html +2ms
  ember-cli:command An error occurred running `Build` from the `build:fallback` command. BuilderError: Directory not found: C:\Users\z\AppData\Local\Temp\tmp-47004Hz2HgWt1lk0L\legacy
    at Builder.checkInputPathsExist (P:\Project\node_modules\broccoli\lib\builder.js:268:15)
    at new Builder (P:\Project\node_modules\broccoli\lib\builder.js:66:10)
    at buildsMerger (P:\Project\node_modules\ember-cli-fallback-builds\lib\utils\builds-merger.js:48:19)
    at BuildTask.run (P:\Project\node_modules\ember-cli-fallback-builds\lib\tasks\build.js:85:16)
    at Promise.resolve.then (P:\Project\node_modules\ember-cli\lib\models\command.js:239:24)
    at tryCatcher (P:\Project\node_modules\ember-cli\node_modules\rsvp\dist\rsvp.js:326:21)
    at invokeCallback (P:\Project\node_modules\ember-cli\node_modules\rsvp\dist\rsvp.js:498:33)
    at P:\Project\node_modules\ember-cli\node_modules\rsvp\dist\rsvp.js:562:16
    at flush (P:\Project\node_modules\ember-cli\node_modules\rsvp\dist\rsvp.js:2441:7)
    at process._tickCallback (internal/process/next_tick.js:61:11)
    at Function.Module.runMain (internal/modules/cjs/loader.js:757:11)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
 +15s
  ember-cli:project getProjectRoot P:\Project -> P:\Project +3ms
  ember-cli:project getProjectRoot P:\Project -> P:\Project +2ms
Directory not found: C:\Users\z\AppData\Local\Temp\tmp-47004Hz2HgWt1lk0L\legacy

Any idea what could cause this, or should I debug it more?

@lifeart
Copy link
Owner

lifeart commented Jul 10, 2019

is it "[email protected]"?

@lifeart
Copy link
Owner

lifeart commented Jul 10, 2019

if we have legacy build error -> we don't have legacy output, this is the root for issue.

image

@vlascik
Copy link
Author

vlascik commented Jul 11, 2019

is it "[email protected]"?

yes

if we have legacy build error -> we don't have legacy output, this is the root for issue.

yep, seems that dummyBuilder doesn't create the output tmp directory, and build itself doesn't create it either. maybe it should make sure the folders exist before spawning the builds

@lifeart
Copy link
Owner

lifeart commented Jul 11, 2019

@vlascik try run build under administrator rights.

@vlascik
Copy link
Author

vlascik commented Jul 11, 2019

It was running with administrator rights. Seems that this is the same problem as in #8

@lifeart
Copy link
Owner

lifeart commented Jul 11, 2019

Could you try againist 0.0.8? (debug output added)

@vlascik
Copy link
Author

vlascik commented Jul 11, 2019

Tried it, same thing, and there is no additional debug output, result is not returned, it fails during the spawned build. Maybe it's a bug in e-cli builder itself if the output directory doesn't exist hm, so, maybe the dummyBuilder should create it before spawning the build first? Not sure if e-cli has any code that does it or just relies on dist/ already existing.

  ember-cli:command An error occurred running `Build` from the `build:fallback` command. BuilderError: Directory not found: C:\Users\z\AppData\Local\Temp\tmp-25856CSIwKM86XhNo\legacy
    at Builder.checkInputPathsExist (P:\Project\node_modules\broccoli\lib\builder.js:268:15)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants