1170426 - Cannot run |make test-integration|: No compatible version found: marionette-apps@'file:./tests/jsmarionette/plugins/marionette-apps'

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia, defect)

Description

[Tim Guan-tin Chien [:timdream] (please needinfo)]

Attachment: npm-debug.log

Try to run Gij test locally on Ubuntu 14.02, got a npm failure.

Gareth, is this related to your work?

Comment 1

[Tim Guan-tin Chien [:timdream] (please needinfo)]

Looks like I've fix it with |sudo npm install -g npm@latest|.

Should we check the npm version and give out more meaningful error here?

Comment 2

[Frederik Braun [:freddy]]

As a first step, maybe we can just perform extra checks to ensure that these specific versions of those tools exist bail out immediately if not?

It's not a solution, but a good enough hotfix for the Makefile, I assume.
(Especially considering how many engineer hours I have seen wasted because of this problem)

Comment 3

[Michael Henretty [:mikehenrty][:mhenretty]]

The testing story is in really bad shape here. In addition to the fact that we require a non-standard bundling (node 10.x with npm 2.x), we have no documentation about this strange setup. This is unworkable for external contributors and really frustrating even for people who have been with the project for a while.

Tim, are you guys addressing any of these problems with your build2 work?

Comment 4

[Gareth Aye [:gaye] (back from PTO)]

We've been using nodejs@0.10.x forever and there's been a lot on the mailing list about people upgrading their npm versions. I do think that adding a testing check to make sure the node and npm versions work is a good idea.

Comment 5

[Tim Guan-tin Chien [:timdream] (please needinfo)]

(In reply to Michael Henretty [:mhenretty] from comment #3)
> The testing story is in really bad shape here. In addition to the fact that
> we require a non-standard bundling (node 10.x with npm 2.x), we have no
> documentation about this strange setup. This is unworkable for external
> contributors and really frustrating even for people who have been with the
> project for a while.

Agreed, so I filed the bug. Since gaye agreed I guess we should add that check in the tool scripts? Ricky, is this something you could help? Thanks!

> Tim, are you guys addressing any of these problems with your build2 work?

They are not related.

Comment 6

[Ricky Chien [:rickychien] (inactive)]

I prefer to setup a stick stable version number in gala's package.json

"engines": {
  "node": "0.10.x",
  "npm": ">2"
}

first thing we need to test various node / npm versions to make sure which is able to work stably.

Gareth, what do you think?

Comment 7

[Gareth Aye [:gaye] (back from PTO)]

I think that since any node 0.10.x and npm >2 works, we should keep it loose to keep people from having to download more stuff.

Comment 8

[BMO Automation]

Firefox OS is not being worked on