Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

I'm using https://github.com/BinaryMuse/atom-mocha-test-runner to run package specs, and I started noticing something weird recently.

The latest Atom beta (1.28.0-beta1) fails to run specs that require package activation on OSX.

The package is activated via await atom.packages.activatePackage(path.join(__dirname, '..')) (since atom-mocha-test-runner doesn't automatically load/activate the package in question). This works on Atom 1.27, and on Windows/Linux on 1.28.0-beta1, but for some reason not on OSX 1.28.0-beta1.

I've went out of my way to get access to an OSX machine, and apparently, specs run fine, more or less, from Atom via window:run-package-specs, but fail completely via atom-beta --test

Overall it appears as if the package fails to activate completely when specs are run with atom --test

Additional Information

Some build examples: https://travis-ci.org/atom-community/markdown-preview-plus/builds/384340951