Skip to content

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

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.

Sign up for GitHub

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

Jump to bottom
Closed
reteprelief opened this issue Jul 22, 2018 · 0 comments
Closed

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

reteprelief opened this issue Jul 22, 2018 · 0 comments
Assignees
@reteprelief
Labels
analyses analyses from plugins category:bug importance:high
Milestone
2.3.5

Comments

@reteprelief
Copy link
Contributor

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
@reteprelief reteprelief mentioned this issue Jul 22, 2018
Merged
@ghost ghost added review and removed in progress labels Jul 22, 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
Assignees

@reteprelief reteprelief

Labels
analyses analyses from plugins category:bug importance:high
Projects
None yet
Milestone
2.3.5
Development

No branches or pull requests
1 participant
@reteprelief