-
Notifications
You must be signed in to change notification settings - Fork 296
apm clean
on travis gets into infinite loop Removing @semantic-release
#746
Comments
This has been recently fixed by #705 and should make its way into Atom 1.22.0. |
Ha, I did search the issues before suggesting one was filed here, but ignored that as it was "installing" a scoped package. Thanks for pointing us in the right direction @50Wliu! |
apm clean
on travis get's into infinite loop Removing @semantic-release
apm clean
on travis gets into infinite loop Removing @semantic-release
I'm still seeing this on Windows in apm 1.19.0:
But once #796 is in, we should be able to fix this again by replacing |
Apparently CircleCI has an incredibly long timeout, just found Atom v1.31.0-beta0 builds running loops on there for the last 90 minutes! https://circleci.com/gh/AtomLinter/linter-ruby/180 (1h 33m) |
@smashwilson Note that this is a regression from #796, you can see that stable (v1.30.0) is working and beta (v1.31.0-beta0) is failing on an Ubuntu image, so this isn't just a Windows issue any more: |
Hello, I am trying to setup semantic release for atom package using travis.
But it hangs on
Removing @semantic-release
step: https://travis-ci.org/DianaSuvorova/atom-karma-test-runner/builds/278288913@Arcanemagus from atom slack channel suggested that:
apm
'sgetModulesToRemove
isn't handling the Scoped package naming syntax correctly (https://docs.npmjs.com/misc/scope)Semantic release uses scoped package naming.
Travis owner suggested it is likely an apm script issue as well.
Thanks,
Diana
The text was updated successfully, but these errors were encountered: