looks like it passed?

Worst case it could be waiting for input in some silent way

Oh, that's double check right? Not release?

-.txt

No, this is before the release.

@rough-minister-58256: @mammoth-pharmacist-54215 I would sooner expect twitter DNS issues

well, one of the dropped emails was from Eric

Err, twitter + gmail + email

Ah

I see your emails

yeah, I think sometimes gmail may cause delays

At least I see at least one from each of you

But maybe corp gmail is different from individual gmail

I’ve seen it at home too

@ancient-stone-50795: Okay, sorry. This sounds like an unfortunately difficult release

It's possible that nuking the cache exacerbated it

We should probably consider figuring out how to make the release less monolithic

It might not be broken, just downloading a crapton of stuf.f. Its still running. I ran

./pants server --open

and its running:

/Users/zundel/.cache/pants/bin/node/mac/10.11/v5.5.0/unpacked/node/bin/npm install

ah, yea. nuking

~/.cache/pants

will do that.

Maybe i should have been more selective, but it helped me get past the go issue.

I stopped it and restarted it about an hour ago. I'm just going to let it run...

Can anyone else run the following from the command line?

./pants clean-all test contrib/scalajs/tests/python/pants_test::

For me it fails with:

09:40:03 00:01     [pytest]
09:40:03 00:01       [run]
                     
09:40:03 00:01         [chroot]============== test session starts ===============
                     platform darwin -- Python 2.7.10 -- py-1.4.31 -- pytest-2.6.4
                     plugins: cov, timeout
                     collected 0 items / 1 errors 
                     
                     ===================== ERRORS =====================
                      ERROR collecting contrib/scalajs/tests/python/pants_test/contrib/scalajs/tasks/test_scalajs_repl_integration.py 
                     .pants.d/python-setup/chroots/c68fefe8ee0737031c479841d01c2191429e7df8/.deps/py-1.4.31-py2.py3-none-any.whl/py/_path/local.py:650: in pyimport
                         __import__(modname)
                     E   ImportError: No module named contrib.scalajs.tasks.test_scalajs_repl_integration
                     ============ 1 error in 0.03 seconds =============

This is the current thing keeping me from making a release. The other problems I had eventually went away after just re-running the release script.

The weird thing is, I get similar errors when running:

./pants test contrib/go/tests/python/pants_test::

but I think the release script got past that.

Hmm, removing a bunch of init.py files under go fixed that directory. I'll try it with scalajs

Yep, that fixed it there too.

@eric you still need someone to try ad run this?

@mammoth-pharmacist-54215: It fails on my laptop still. Let me know what results you get and what platform you are running on. I'm on a mac, El Capitan (2.11) and python 2.7.10

@ancient-stone-50795: I ran this once and it failed, then it passed the next 3 times in a row .