Skip to content

still some linux binary path wackness (travis-ci grr) #16

Description

@gregglind
  1. I don't see this package installed for jpm 1.0.7, should it be?
  2. at least the jpm I am calling is still looking for the old path. On Travis, it puts it in /usr/local/bin/firefox
$ echo `which firefox`
/usr/local/bin/firefox
41.09s$ npm test
> shield-studies-addon-utils@1.0.0 test /home/travis/build/gregglind/shield-studies-addon-utils
> grunt test && istanbul check-coverage --statements 100 --functions 100 --branches 100 --lines 100 coverage/reports/coverage.json

Running "instrument" task

Instrumented 1 file

Running "shell:jpmTest" (shell) task

JPM [info] Starting jpm test on shield-studies-addon-utils

JPM [info] Creating a new profile

JPM [error] No Firefox binary found at null

JPM [error] Specify a Firefox binary to use with the `-b` flag.

JPM [error] Error: spawn /usr/lib64/firefox ENOENT

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions