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

Comments

Projects
None yet
1 participant
@reteprelief
Contributor

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

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