search

mozilla / memchaser

Firefox extension to chase the memory usage and garbage collector activity
https://wiki.mozilla.org/QA/Automation_Services/Projects/Addons/MemChaser
29 stars 23 forks source link

Switch from 'cfx' to 'jpm' for packaging #203

Open whimboo opened 10 years ago

whimboo commented 10 years ago

Looks like the cfx tool is going to be replaced with jpm. So we will have to change our code accordingly. See the blog post from Eric: http://work.erikvold.com/jetpack/2014/08/07/cfx-to-jpm.html

Targeting for the 0.7 release.

xabolcs commented 10 years ago

If nobody works on this, I would like to take it!

@whimboo could you assign me for this issue? I could continue with this after the Australis UI/Toolbar fix.

xabolcs commented 10 years ago

Slightly related post: Node.js as a build script

whimboo commented 10 years ago

Thanks @xabolcs! Btw. you can assign yourself to any issue you want. You should have the permissions to do so. :)

xabolcs commented 10 years ago

You should have the permissions to do so. :)

Interestingly I'm unable to do so.

whimboo commented 10 years ago

Hm strange. Anyway lets get this discussed on IRC when you have time. Thanks for noting it.

xabolcs commented 9 years ago

This needs two step.

  1. entry point in package.json
  2. loading modules from test modules (see MDN page)

The second breaks cfx, so we need to migrate .travis.yml and build.xml too.

But at least 21 of 21 tests passed. :)

whimboo commented 9 years ago

Sounds fine to me. Especially if all tests are still passing.

xabolcs commented 9 years ago

FYI JPM Replaces CFX For Firefox 38.

xabolcs commented 9 years ago

It would be nice to do this migration when next ESR become public.

xabolcs commented 8 years ago

See those failed Travis builds for Nightly 45.0a1 and Aurora 44.0a2!

whimboo commented 8 years ago

It's not that much information you get from the logging output what exactly failed. But looks like its a harness issue.

xabolcs commented 8 years ago

Fixed by commit 120356a565cc5edb38dddff53135e1cce2b0abec above.

whimboo commented 8 years ago

As @xabolcs noted on the PR we missed to update the README file regarding those changes. So we have to reopen given that we need another PR.

Things needs to be fixed