Fix time.Time not equals bug

[senyast4745]

Adding test

Summary

Fix assert.ObjectsAreEqual bug with not equals time.Time before and after serializing\deserializing

Changes

Added a check in ObectsAreEqual in case the arguments are a time object

Motivation

Fix bug to use test in docker

Related issues

Closes #950

[boyan-soubachov]

Thank you for your contribution. You still need to run go generate as I don't see the auto-generated files in this PR.

I also think you have made some mistake with the _codegen sub-module as there have been changes to its module files.

[boyan-soubachov]

Thank you for your time and effort. This looks great now :)

[boyan-soubachov]

I've had to fix the TravisCI config. Do you mind rebasing the branch and then I can merge it?

[senyast4745]

Of course I do not mind

[senyast4745]

I can merge the master in my branch pulling up new changes

[boyan-soubachov]

Thank you, there still seem to be some conflicts, do you mind having a look again?

[senyast4745]

Sorry, upstream has not been updated. The last commit pulled all the changes from testify

[senyast4745]

Thanks in advance for the opportunity to contribute))

[boyan-soubachov]

Something is very weird, still getting errors due to conflicts:

Are you able to rebase and squash maybe? I promise I will merge it as soon as you do :)

[senyast4745]

Hi, very sorry, I was very busy. I merge the latest changes from master to my branch. Unfortunately, the commits could not be squashed, I'm afraid to do a hard push or rebase

[boyan-soubachov]

Hi, very sorry, I was very busy. I merge the latest changes from master to my branch. Unfortunately, the commits could not be squashed, I'm afraid to do a hard push or rebase

If you rebase, resolve any conflicts and then force-push your branch you should be fine.

We can't merge this PR while there are conflicts :)

[senyast4745]

Please show me in which files the conflicts occur, I will solve them locally, because I still don't understand a little how and where I can rebase and force-push

[senyast4745]

should i rebase my branch to master?

[boyan-soubachov]

should i rebase my branch to master?

Yes, you'd rebase on master, something along the lines of

git rebase master
<resolve conflicts with your editor>
git push -f fork

where fork is the remote set-up to your fork.

This is a good and thorough guide on the general flow: https://blog.scottlowe.org/2015/01/27/using-fork-branch-git-workflow/

[senyast4745]

I did rebase and force-push, as you asked

[leoleoasd]

It seems that the fork branch's commit is still messy. Maybe consider check out a new branch from master branch of stretchr's repo locally, re-do your changes on fork branch and force-push your new branch to origin/fork?

[leoleoasd]

Should we close this given that #979 fixed the git history issue?