Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing builds on master after release #112

Closed
jantman opened this issue Dec 17, 2015 · 4 comments
Closed

Failing builds on master after release #112

jantman opened this issue Dec 17, 2015 · 4 comments
Labels
Milestone

Comments

@jantman
Copy link
Owner

jantman commented Dec 17, 2015

Still need to look into this: https://travis-ci.org/jantman/awslimitchecker/builds/97348751

@jantman jantman added this to the 0.3.0 milestone Dec 17, 2015
@jantman
Copy link
Owner Author

jantman commented Dec 17, 2015

Problem seems to be in the install_git tests, getting AssertionError: git clone not equal to origin.

Example from one of the tests:

I think the problem might be in parsing the git status -u output when we're on a tag.

@jantman
Copy link
Owner Author

jantman commented Dec 17, 2015

The problem is here: https://github.com/jantman/awslimitchecker/blob/master/awslimitchecker/tests/test_versioncheck.py#L1477

        if ('Your branch is up-to-date with' not in status and
                'HEAD detached at' not in status):
            print("\ngit status -u:\n" + status + "\n")
            return 1

The build job checked out a commit that pointed to a tag, but I'd already deleted the branch when I merged the PR, so the build ran against something that was a detached head.

We can clearly see the problem when looking at the output of Test_AGPLVersionChecker_Acceptance._check_git_pushed:

git status -u:
# Not currently on any branch.
nothing to commit, working directory clean

FAILED

I believe this should be fixed with 3e0b90f - I made that commit on an issues/112 branch, then tagged the commit "issue112" and pushed only the tag to origin, not the branch. That should be good to replicate this issue.

@jantman
Copy link
Owner Author

jantman commented Dec 17, 2015

That build/commit fixed the issue here, but revealed a bug in versioncheck._is_git_dirty, also relating to not being on a branch - see https://travis-ci.org/jantman/awslimitchecker/jobs/97352774#L551

[DEBUG versioncheck.py:254 - awslimitchecker.versioncheck._is_git_dirty() ] Git repository dirty based on status: # Not currently on any branch.

nothing to commit, working directory clean

This looks like pretty much the same thing that I fixed in 3e0b90f

@jantman
Copy link
Owner Author

jantman commented Dec 17, 2015

Merged into develop.

@jantman jantman modified the milestones: 0.3.0, 0.2.4 Dec 17, 2015
@jantman jantman modified the milestones: 0.3.0, 0.2.4 Feb 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant