-
Notifications
You must be signed in to change notification settings - Fork 0
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
23 add exclusivity operators #28
base: master
Are you sure you want to change the base?
Conversation
…dd inference rule for interfereWith and notInterfereWith operators for Hardware/Hardware type
…hasNonInterferingServices, raise error on priority of Interfere relation over NotInterfere relation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before merging it would be nice to add a test class that is checking that interfereWith update the hardwareInterfereRelation (and its not interfere countpart) on a simple example. Same request for the hasInterfering/hasNonInterfering services.
The CI is not working due to an external change in the available action to mount an SBT image. I will take care of that with a rebase of this branch on master once the patch from issue #20 has been merged
…dd inference rule for interfereWith and notInterfereWith operators for Hardware/Hardware type
…hasNonInterferingServices, raise error on priority of Interfere relation over NotInterfere relation
…nalyzer into 23-add-exclusivity-operators
Description
Add hasInterferingServices and hasNonInterferingServices as operators pour type Hardware.
Add inference rule for interfereWith and nonInterfereWith operators for Hardware/Hardware type.
Warning: There is a priority conflict between InterfereRelation and NonInterfereRelation, the first one seems to have priority over the second one.
What type of pull request is this? (check all applicable)
Related Tickets & Documents
If possible ensure that you have provided in your commit message the issue id (available here) this pull request fixes,
for instance to refer to issue #42 you can do:
git commit -m "solving issue #42 with ..."
Check here for more information
Added tests?
Added to documentation?
Do we need to update pml analyzer version?
Is this new version should be released as soon as possible?