-
Notifications
You must be signed in to change notification settings - Fork 49
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
Correct writeback_state sequence test #450
Conversation
8fe6571
to
40fa743
Compare
@grafnu what needs to be done to fix the generated.md as below: Looking at the other sequences, it should at least include the change config, e.g.:
And ideally it would include some of the metadata around the tests
|
When you say "include some of the metadata" -- do you mean that the values
are showing up in the config sent to the device, but not in the
generated.md? Or is it that the values aren't even showing up in the
config? Basically, what is "it" in that sentence?
…On Mon, Sep 12, 2022 at 5:34 AM Noureddine ***@***.***> wrote:
@grafnu <https://github.com/grafnu> what needs to be done to fix the
generated.md as below:
Looking at the other sequences, it should at least include the change
config, e.g.:
1. Update config for writeback
* Set "pointset.points.filter_alarm_pressure_status.set_value" = false
* Set "pointset.points.filter_differential_pressure_setpoint.set_value" = 60
* Set "pointset.points.filter_differential_pressure_sensor.set_value" = 15
And ideally it would include some of the metadata around the tests
invalidTarget.target_point = invalidTarget.target_value
failureTarget.target_point = failureTarget.target_value
appliedTarget.target_point = appliedTarget.target_value
—
Reply to this email directly, view it on GitHub
<#450 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIEPD37QGJ6HEEK5SSNIRTV54PMHANCNFSM6AAAAAAQIR7MNM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
At the moment the values/config diffs don't show up in generated.md at all. The specific values would not be documented (as they're device specific), rather what they represent should So looking at one line from the example in my comment, Instead of showing something like The point Ideally, we would document in generated.md something generic e.g. |
The fact that they aren't showing up at all is the first problem. The
config diff should show all the differences. Let me pull the branch down
and I'll take a look directly...
…On Mon, Sep 12, 2022 at 8:56 AM Noureddine ***@***.***> wrote:
At the moment the values/config diffs don't show up in generated.md at all.
The specific values would not be documented (as they're device specific),
rather what they represent should
So looking at one line from the example in my comment, Instead of showing
something like
* Set "pointset.points.filter_alarm_pressure_status.set_value" = false.
The point filter_alarm_pressure_status.set_value and the value false both
come from invalidTarget.target_point and invalidTarget.target_value in
the Java code respectively.
Ideally, we would document in generated.md something generic e.g. * Set
"pointset.points.INVALID_POINT.set_value" = INVALID_VALUE instead
—
Reply to this email directly, view it on GitHub
<#450 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIEPDZUIQOJCRXXLKSLOQLV55HDNANCNFSM6AAAAAAQIR7MNM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks Trevor for you PR, seems to have fixed the bug so But it's introduce an error with the |
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.
Oy, I think this needs a merge with master before review! (GitHub algorithms seem to be bad??!)
c9a0697
to
05b93a1
Compare
@grafnu made a mistake when I did a merge hence the issues you saw (I think GitHub's algos were fine) There are still 249 modified files, but the bulk of these are the sequencer outputs in |
bin/clone_model
Outdated
@@ -5,7 +5,7 @@ mkdir -p $ROOT_DIR/sites | |||
cd $ROOT_DIR/sites | |||
|
|||
MODEL_DIR=udmi_site_model | |||
MODEL_VER=1.7 | |||
MODEL_VER=808aa06fbe922b9f749d2a6b52ff03b6f9074b48 |
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.
needs 1.8 tag
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.
Will do, but you also need to create a 1.8 tag for that repo.
@@ -6,5 +6,5 @@ | |||
"subType" : "config", | |||
"category" : "commands", |
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.
I think these should be added to .gitattributes to ignore the diffs so it's clear to the reviewer!
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.
What files need to be included in this directory? Without any redaction, all the files will change with every run except for the sequence.md
? Should we only include sequence.md
and ignore the rest?
3fc5cad
to
04357df
Compare
Ok, tag 1.8 should be ready!
…On Wed, Sep 14, 2022 at 6:03 AM Noureddine ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In bin/clone_model
<#450 (comment)>:
> @@ -5,7 +5,7 @@ mkdir -p $ROOT_DIR/sites
cd $ROOT_DIR/sites
MODEL_DIR=udmi_site_model
-MODEL_VER=1.7
+MODEL_VER=808aa06fbe922b9f749d2a6b52ff03b6f9074b48
Will do, but you also need to create a 1.8 tag for that repo.
—
Reply to this email directly, view it on GitHub
<#450 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIEPDZPUHEIR4JRTSIK5JDV6HEK5ANCNFSM6AAAAAAQIR7MNM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The files only change if they're copied over... I'm not sure what/why
you're asking... ? They're just examples so it seems like the complete set
would be useful. I think you might be misinterpreting the impact of the
change I suggested...
…On Wed, Sep 14, 2022 at 6:05 AM Noureddine ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In validator/sequences/broken_config/config_pointset.attr
<#450 (comment)>:
> @@ -6,5 +6,5 @@
"subType" : "config",
"category" : "commands",
What files need to be included in this directory? Without any redaction,
all the files will change with every run except for the sequence.md?
Should we only include sequence.md and ignore the rest?
—
Reply to this email directly, view it on GitHub
<#450 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIEPDYBG2NKEPEEJ5JRX6LV6HEP7ANCNFSM6AAAAAAQIR7MNM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Great, CI test all clear now so should be mergeable. I've also made the requested to I was just stating all the files will be modified when they're copied over (because timestamps, etc), including for those tests which did not change. I was just wondering if all the files were needed or some redaction was needed, but as you said its good to have the complete set |
Nour, can you separate out all the "I don't care" log files into a separate PR and then either push that through or have this PR against that one? Even though they're not visible by default, it's near impossible to review this PR because of the sheer number of "must ignore" files, and there's ways around that! |
.github/workflows/testing.yml
Outdated
@@ -111,6 +111,9 @@ jobs: | |||
more /tmp/sequencer.out | |||
diff -u /tmp/sequencer.out etc/sequencer.out | |||
diff -u /tmp/generated.md docs/specs/sequences/generated.md | |||
ls -1 validator/sequences | xargs -I% diff -u \ |
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.
be warned, what I discovered the other day is that the shell in GitHub Actions doesn't always process failure conditions correctly. Did you check that this actually fails the run when there's a problem? ( You could quickly check by tweaking the validator/sequences/%/sequence.md file)
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.
Thanks, I've checked and it does fail when there is a difference or missing file.
d3cee30
to
5d1a6b7
Compare
Correct behaviour of writeback_state sequence test