palantir / gradle-bowerdeps-plugin

A Gradle plugin for controlling build order with bower.json files.
Apache License 2.0
3 stars 4 forks source link

:integrationTest fails with org.gradle.process.internal.ExecException on BSD #1

Open saper opened 9 years ago

saper commented 9 years ago

Running on FreeBSD 10.1/amd64 and

openjdk version "1.7.0_80"
OpenJDK Runtime Environment (build 1.7.0_80-b15)
OpenJDK 64-Bit Server VM (build 24.80-b11, mixed mode)

My currently installed node instance (actually this is io.js 2.0.0) identifies the system as:

> process.versions
{ http_parser: '2.5.0',
  node: '2.0.0',
  v8: '4.2.77.18',
  uv: '1.4.2',
  zlib: '1.2.8',
  ares: '1.10.0-DEV',
  modules: '44',
  openssl: '1.0.2a' }
> os.platform()
'freebsd'
> os.arch()
'x64'

Exceptions:

:integrationTest

com.palantir.bowerdeps.BowerDepsPluginIntegSpec > grunt dependencies added FAILED
    org.gradle.api.GradleException at BowerDepsPluginIntegSpec.groovy:106
        Caused by: org.gradle.internal.exceptions.LocationAwareException
            Caused by: org.gradle.api.tasks.TaskExecutionException
                Caused by: org.gradle.process.internal.ExecException

com.palantir.bowerdeps.BowerDepsPluginIntegSpec > gulp dependencies added FAILED
    org.gradle.api.GradleException at BowerDepsPluginIntegSpec.groovy:148
        Caused by: org.gradle.internal.exceptions.LocationAwareException
            Caused by: org.gradle.api.tasks.TaskExecutionException
                Caused by: org.gradle.process.internal.ExecException

com.palantir.bowerdeps.BowerDepsPluginIntegSpec > grunt dependencies added to alternate task FAILED
    org.gradle.api.GradleException at BowerDepsPluginIntegSpec.groovy:196
        Caused by: org.gradle.internal.exceptions.LocationAwareException
            Caused by: org.gradle.api.tasks.TaskExecutionException
                Caused by: org.gradle.process.internal.ExecException

com.palantir.bowerdeps.BowerDepsPluginIntegSpec > gulp dependencies added to alternate task FAILED
    org.gradle.api.GradleException at BowerDepsPluginIntegSpec.groovy:247
        Caused by: org.gradle.internal.exceptions.LocationAwareException
            Caused by: org.gradle.api.tasks.TaskExecutionException
                Caused by: org.gradle.process.internal.ExecException

com.palantir.bowerdeps.BowerDepsPluginMultiProjectIntegSpec > no plugins and no build task specified FAILED
    org.gradle.api.GradleException at BowerDepsPluginMultiProjectIntegSpec.groovy:202
        Caused by: org.gradle.internal.exceptions.LocationAwareException
            Caused by: org.gradle.api.tasks.TaskExecutionException
                Caused by: org.gradle.process.internal.ExecException

7 tests completed, 5 failed
:integrationTest FAILED

FAILURE: Build failed with an exception.

Gradle daemon reports on its logs

ELF binary type "0" not known.

It seems like node binaries for Linux are downloaded (this is output from file(1) folded for readability)

 build/test/com.palantir.bowerdeps.BowerDepsPluginMultiProjectIntegSpec/no-plugins-and-no-build-task-specified/build/node/node-v0.12.3-linux-x64/bin/node:
 ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.9, not stripped

and

build/test/com.palantir.bowerdeps.BowerDepsPluginMultiProjectIntegSpec/no-plugins-and-no-build-task-specified/build/node/node-v0.11.10-linux-x64/bin/node:
ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, not stripped
nmalaguti commented 9 years ago

Thanks for the issue.

The integration tests are configured to download node. This is based on the behavior of https://github.com/srs/gradle-node-plugin. I can (and might) change that requirement since it is causing problems with Gradle 2.4 as well.

I'm not 100% sure how nebula triggers the gradle run for integration tests, but I think it may be causing issues.

saper commented 9 years ago

This is duplicate of https://github.com/srs/gradle-node-plugin/issues/50.

nmalaguti commented 9 years ago

Ah, yeah it looks like there isn't a FreeBSD build available on the nodejs website.

2 will require that you have node installed globally, which seems fine for the integration tests. Users can still use whatever options like like for the node plugin.

saper commented 9 years ago

No, node is compiled from source via the FreeBSD ports system: (cd /usr/ports/www/node && make install) OR the binary is downloaded via the pkg tool: pkg install node.

http://pkg.FreeBSD.org/FreeBSD:10:amd64/latest/All/node-0.12.3.txz

is a link for the node 0.12.3 FreeBSD package for FreeBSD 10/amd64. To extract the binary itself, just decompress and untar the file, the binary will be in bin.