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

random test order fixes for PostgreSQL #12939

Closed
wants to merge 1 commit into from

Conversation

hegyi
Copy link

@hegyi hegyi commented Nov 18, 2013

I fixed some failing test cases (not ALL) while running the tests in random order.

@schneems
Copy link
Member

Can you please squash these commits into one, do you have a copy of the output of failing tests in random order?

@hegyi
Copy link
Author

hegyi commented Nov 18, 2013

output: https://gist.github.com/hegyi/7531605
line 6 shows the test order

@schneems
Copy link
Member

Thanks, sorry about the rebase comment I meant to ask you to squash the commits to one.


Sent from Mailbox for iPhone

On Mon, Nov 18, 2013 at 11:22 AM, Adam Hegyi notifications@github.com
wrote:

output: https://gist.github.com/hegyi/7531605

line #6 shows the test order

Reply to this email directly or view it on GitHub:
#12939 (comment)

resetting columns

skipping temporary destroy callback

restoring old Owner class after assertion

restoring original sequence

remove puts
@@ -35,6 +35,8 @@ def test_multiline_default_text
# older postgres versions represent the default with escapes ("\\012" for a newline)
assert( "--- []\n\n" == Default.columns_hash['multiline_default'].default ||
"--- []\\012\\012" == Default.columns_hash['multiline_default'].default)
ensure
Default.reset_column_information
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what line modifies the column information so that we need to reset it?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about this one, I need to check it

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I put the reset in the wrong test case. I created a gist where you can see the problem: https://gist.github.com/hegyi/7547694

reset column information seems to work but I have no idea why.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did this ever get figured out @hegyi / @senny ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JonRowe not yet.

@senny
Copy link
Member

senny commented May 30, 2014

I'm going to close this out of inactivity. Our Google Summer of Code student @zuhao is working to run all our tests in random order. I'm sure he will find this patch useful.

@hegyi thank you for your work 💛

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants