Skip to content

Hotfix/2015 10 15 - #10195

Merged
adampalay merged 9 commits into
releasefrom
hotfix/2015-10-15
Oct 16, 2015
Merged

Hotfix/2015 10 15#10195
adampalay merged 9 commits into
releasefrom
hotfix/2015-10-15

Conversation

@adampalay

Copy link
Copy Markdown
Contributor

dianakhuang and others added 5 commits October 7, 2015 11:20
The heart of this fix is to change the "My Team" view to use a
collection of teams instead of memberships. The team card is
refactored to only take a team, rather than attempt to be polymorphic
over teams and team memberships. This change enabled removing a good
amount of old code. This also requires adding a `username` parameter
to the teams list endpoint which allows getting a list of all teams
for a single user, in order to allow refreshing the "My Teams" view
correctly. Currently this list is of length at most one.

TNL-3410
@adampalay

Copy link
Copy Markdown
Contributor Author

Looks like test are failing because migrations didn't run...

@adampalay

Copy link
Copy Markdown
Contributor Author

@jzoldak , @benpatterson , should I just rerun tests to trigger a migration?

@benpatterson

Copy link
Copy Markdown
Contributor

@adampalay for the python test failures? I don't think rerunning jenkins jobs would help...

@adampalay

Copy link
Copy Markdown
Contributor Author

@benpatterson it looks like tests failed because a migration wasn't run — do you know how to get the migrations to run?

@adampalay

Copy link
Copy Markdown
Contributor Author

jenkins run python please

@benpatterson

Copy link
Copy Markdown
Contributor

@adampalay if "running it again" will solve this problem, then we should still fix it. Because we'd be introducing a flaky pattern and, once rebased, developers would be running python multiple times to get a passing build.

@adampalay

Copy link
Copy Markdown
Contributor Author

@benpatterson, good point. It looks like tests failed a second time soon anyway. @bderusha

@benpatterson

Copy link
Copy Markdown
Contributor

@adampalay @bderusha if this helps, I can reproduce locally by running paver test_system -s cms -t common/djangoapps/third_party_auth/tests/

@adampalay

Copy link
Copy Markdown
Contributor Author

@benpatterson oh, interesting. I couldn't reproduce by running paver test_system -t common/djangoapps/third_party_auth/tests/test_decorators.py:TestXFrameWhitelistDecorator. This also passes when I run paver test_system -t common/djangoapps/third_party_auth/tests/. So it looks like the problem is in running this in cms

@efischer19

Copy link
Copy Markdown
Contributor

jenkins run bokchoy

@efischer19

Copy link
Copy Markdown
Contributor

The failed bokchoy test is known to be flaky, and doesn't need to hold up this hotfix release: https://openedx.atlassian.net/browse/TNL-3489

Link to failure on previous run: https://build.testeng.edx.org/job/edx-platform-bok-choy-pr/6463/

@adampalay

Copy link
Copy Markdown
Contributor Author

Working with @bderusha , we discovered that the python test failures were because third_party_auth isn't configured in CMS, so we're going to skip these tests if 'third_party_auth' isn't an installed app. That way, when we add third_party_auth (sorry @waheedahmed !) to studio, this test will fail so we'll have to remove it.

@adampalay

Copy link
Copy Markdown
Contributor Author

Ok, in theory, everything should pass now!

adampalay added a commit that referenced this pull request Oct 16, 2015
@adampalay
adampalay merged commit 3a61cca into release Oct 16, 2015
@adampalay
adampalay deleted the hotfix/2015-10-15 branch March 4, 2016 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants