-
Notifications
You must be signed in to change notification settings - Fork 44
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
fix: GH workflow test #635
Conversation
- This commit includes fixing typos, and reverting back to original way of extracting subsystem values
the reported error in yaml import/export cycle is fixed by correcting typos and reverting to original subsystem value extraction (e118e1d); while the issue with GH action remains, which might be resolved later? |
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 tested this PR by locally running testYamlConversion
and tandemly import/export the yaml file, everything is fine.
would be good to have checks for unknown keys (caused by typos) in yaml, but have no idea how to reactivate the "idling" action
I'm still working on getting the workflow to fail in a visible way. |
e9426a9
to
b247c0b
Compare
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.
LGTM!
could this be merged, how's going with the workflow test? @mihai-sysbio |
The workflow still appears as passing in the latest workflow run even though it clearly prints out an error. I am having difficulties relaying the |
yes, let's do so
this workflow problem can be temporarily substituted with checking these Matlab-based tasks locally before merging |
e822985
to
6ac87c4
Compare
6ac87c4
to
29113a1
Compare
Due to significant changes and slight scope creep, reviews will be re-requested. |
if I can re-introduce the bug happened in Yaml before and see what happens? |
good idea, please play around with different test cases |
Another idea, should the |
- Test if GH action really work
the bug re-troduced by 97d030b suppose to lead to failure of both yaml-validation and yaml-conversion actions. But the latter still gives a pass, therefore this workflow bug persists. |
@haowang-bioinfo the reintroduced but caused a failure higher up in the testing code, which was not caught by the same mechanism. The previous commit 6e5d66c address this. |
If there is any other bug you'd want to test with, please go ahead @haowang-bioinfo |
Oh how interesting, none of tests capture the bug introduced in 5f39c61. The actions are passing, because the tests are passing. I would be inclined to report this as separate bug - the workflows now seem to reflect the status of the tests, which was the original aim of this PR. |
go ahead please This type of bug (5f39c61) probably can be detected by Yaml lint checker by providing a finite set of keys, from which any unknown keys could thus be detected and reported. |
feat: add basic memote tests
@haowang-bioinfo the purposefully introduced bug has now been caught and may be removed. |
with #672, both |
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.
looks very good - the previously idle yaml-conversion
action in functioning, together with enhanced memote checks
Main improvements in this PR:
This PR is continuing #629 aimed to fix the GH workflow test of the import-export cycle, thus resolving #628.
I hereby confirm that I have:
develop
as a target branch