Skip to content

remind101/stacker-python-bug-squash

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

32 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Python bug squash

One of our internal tools includes hooks to perform functions like building AWS lambda payloads from a configuration file and uploading them to S3.

The content hash generated by the AWS lambda hook seems to change periodically, and is different across machines even when nothing else has changed. The expected behaviour of the hook is for the generated payload to be uploaded only when the user configuration has changed. So if the hook is run on two separate machines for the same configuration file the resulting payload should only be uploaded once.

Running the tests

Locally

First make sure you have pip & virtualenv installed. If not, then perform the following:

brew update && brew upgrade python
easy_install pip
pip install --upgrade pip
pip install virtualenv

Now instantiate a virtualenv and activate it:

virtualenv remind-bug-squash
. ./remind-bug-squash/bin/activate

Now install all the necessary dependencies:

pip install -r requirements.txt

You should now be able to run the test suite from the top level directory of the repo:

nosetests --exe

Docker

Run this command which will build the docker image, and run a bash shell inside it:

make shell

Then directly in the docker container:

$ nosetests --exe

About

A bug squash problem based on Stacker

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published