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

Flow latency analysis runs with synchronous setting when the preference is asynchonous and vice versa #1394

Closed
reteprelief opened this issue Jul 22, 2018 · 0 comments
Assignees
Milestone

Comments

@reteprelief
Copy link
Contributor

@reteprelief reteprelief commented Jul 22, 2018

This problem did not exist in 2.3.3. It was introduced when we reworked how we pass on preference setting into the analysis.
see for example https://github.com/osate/examples/tree/master/latency-case-study

@reteprelief reteprelief added this to the 2.3.5 milestone Jul 22, 2018
@ghost ghost assigned reteprelief Jul 22, 2018
@ghost ghost added the in progress label Jul 22, 2018
@ghost ghost added review and removed in progress labels Jul 22, 2018
@lwrage lwrage closed this in #1395 Jul 23, 2018
@ghost ghost removed the review label Jul 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.