Skip to content

Conversation

@PieterCappelle
Copy link
Contributor

@PieterCappelle PieterCappelle commented Oct 9, 2017

Was fixed in 2.0.8 branch. Never got into 2.1-develop and 2.2-develop. Cherry-pick from 9fc059b

#5726

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

Was fixed in 2.0.8 branch. Never got into 2.1-develop and 2.2-develop. Cherry-pick from 9fc059b
@okorshenko
Copy link
Contributor

Hi @PieterCappelle
Could you please check failed unit tests?

@PieterCappelle
Copy link
Contributor Author

Hi, one unittest failed because of execution limit, all other ones completed without errors. I think the problem is in travis and not in my code.

@okorshenko okorshenko added 2.2.x bug report Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Oct 16, 2017
*
* @param int $scopeId
* @return $this
*/
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Okay, and how should I fix that? This function is necessary for the complete workflow of this PR.

@okorshenko
Copy link
Contributor

Hi @PieterCappelle
QA team reported GitHub issue #5726 is still reproducible on that branch. (same as on PR to 2.1-develop). Could you please double check

@PieterCappelle
Copy link
Contributor Author

Can you tell me what could reproduced? Because I've edited multiple cases. Is it one specific case, because in my tests it's working like it should be.

@okorshenko
Copy link
Contributor

Sure, I requested detailed information from the QA department. Should be ready soon

@okorshenko
Copy link
Contributor

Hi @PieterCappelle
Here is video provided by our QA
https://youtu.be/ng4bWnkc5-Q

@PieterCappelle
Copy link
Contributor Author

So strange. Viewed the video and indeed same problem occurs. Will try this case. Will keep you updated.

@okorshenko okorshenko modified the milestones: October 2017, November 2017 Nov 1, 2017
@okorshenko
Copy link
Contributor

Hi @PieterCappelle I'm closing this PR for now. Please, reopen it once ready

@okorshenko okorshenko closed this Nov 6, 2017
@PieterCappelle PieterCappelle deleted the fix_2_2_issue_5726 branch December 21, 2017 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug report Release Line: 2.2 Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants