Ticket #255 (assigned task)

Opened 8 months ago

Last modified 11 days ago

Setup GAE buildslave

Reported by: thijs Owned by: nick
Priority: major Milestone: 0.4
Component: Testing Version: 0.3
Keywords: Cc:

Description (last modified by thijs) (diff)

Would be good to have a buildslave for our GoogleAppEngine adapter.

Change History

  Changed 8 months ago by thijs

  • milestone changed from 0.4 to 0.3.1

  Changed 7 months ago by thijs

  • status changed from new to accepted
  • milestone changed from 0.3.1 to 0.3.2

  Changed 7 months ago by thijs

  • milestone changed from 0.3.2 to 0.4

Milestone 0.3.2 deleted

  Changed 7 months ago by thijs

  • owner changed from thijs to nick
  • status changed from accepted to assigned

  Changed 6 months ago by thijs

  • milestone changed from 0.3.2 to Blue Sky

  Changed 3 months ago by thijs

  • description modified (diff)
  • milestone changed from Blue Sky to 0.4

Nick added a [pyamf/sandbox/nick/gae_client.py@1663 gae client script] that runs GAE PUnit and spits out an error code.

  Changed 3 months ago by thijs

Nick added a gae client script that runs GAE PUnit and spits out an error code

  Changed 3 months ago by thijs

  • status changed from assigned to closed
  • resolution set to fixed

Fixe with r1685, see http://buildbot.pyamf.org/builders/amd64-appengine-py25

follow-up: ↓ 10   Changed 3 months ago by nick

  • status changed from closed to reopened
  • resolution fixed deleted

The client script defaults to http://ae.pyamf.org/punit however it would be better to be able to test the most recent commit as the other buildslaves do. To this end the buildslave should spawn a gae process with punit installed, run the client script against that process and then report the outcome.

in reply to: ↑ 9   Changed 2 months ago by thijs

  • owner changed from nick to thijs
  • status changed from reopened to accepted

Replying to nick:

The client script defaults to http://ae.pyamf.org/punit however it would be better to be able to test the most recent commit as the other buildslaves do. To this end the buildslave should spawn a gae process with punit installed, run the client script against that process and then report the outcome.

And it looks like you added pyamf/sandbox/nick/test_gae.py@1696 this script for that. Will check it out.

  Changed 2 weeks ago by thijs

Currently reports this error when I try to start it up: 

$ python2.5 gae_client.py 
Traceback (most recent call last):
  File "gae_client.py", line 218, in <module>
    x = GAETestRunner(options.url)
  File "gae_client.py", line 71, in __init__
    self.get_all_tests()
  File "gae_client.py", line 87, in get_all_tests
    ret = simplejson.loads(self._get_url(''))
  File "build/bdist.linux-x86_64/egg/simplejson/__init__.py", line 262, in loads
  File "build/bdist.linux-x86_64/egg/simplejson/decoder.py", line 251, in decode
  File "build/bdist.linux-x86_64/egg/simplejson/decoder.py", line 270, in raw_decode
ValueError: No JSON object could be decoded

  Changed 2 weeks ago by thijs

  • owner changed from thijs to nick
  • status changed from accepted to assigned

  Changed 12 days ago by nick

  • keywords review added
  • owner changed from nick to thijs

This buildslave is now ready for review

  Changed 11 days ago by thijs

  • keywords review removed
  • owner changed from thijs to nick

The latest build shows a lot of the following errors: 

OSError: [Errno 1] Operation not permitted

Any idea why this is happening or what to do about it?

Note: See TracTickets for help on using tickets.