Hi All,

I have faced this issue a couple of times and wondering if anyone has a way to recover from it. While doing a Myriad build (esp on a new machine) I have experienced failures around these steps

:myriad-scheduler:npmInstall
:myriad-scheduler:gulp_build

After a failure neither ./gradlew clean nor ./gradlew build works

I see error messages like below


FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':myriad-scheduler:gulp_build'.
> Process 'command '/home/home/.gradle/nodejs/node-v4.2.1-linux-x64/bin/node'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

home@systemx:~/ossgit/incubator-myriad$ ./gradlew clean
Parallel execution is an incubating feature.
:myriad-scheduler:nodeSetup
:myriad-executor:clean
:myriad-commons:clean
:myriad-scheduler:nodeSetup UP-TO-DATE
:myriad-scheduler:gulp_clean
module.js:339
    throw err;
    ^

Error: Cannot find module 'vinyl-transform'
    at Function.Module._resolveFilename (module.js:337:15)
    at Function.Module._load (module.js:287:25)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
at Object.<anonymous> (/home/home/ossgit/incubator-myriad/myriad-scheduler/src/main/resources/webapp/gulpfile.js:24:17)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
:myriad-scheduler:gulp_clean FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':myriad-scheduler:gulp_clean'.
> Process 'command '/home/home/.gradle/nodejs/node-v4.2.1-linux-x64/bin/node'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Is there a easy way to get out of this state ?

Regards
Swapnil

Reply via email to