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
Add always_rolllback doc and flag icon #1812
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1812 +/- ##
==========================================
- Coverage 90.3% 90.28% -0.02%
==========================================
Files 140 140
Lines 10065 10065
==========================================
- Hits 9089 9087 -2
- Misses 976 978 +2
Continue to review full report at Codecov.
|
docs/WritingTests.asciidoc
Outdated
@@ -79,6 +80,7 @@ sub test_flags { | |||
# 'ignore_failure' - if this module fails, it will not affect the overall result at all | |||
# 'milestone' - after this test succeeds, update 'lastgood' | |||
# 'norollback' - don't roll back to 'lastgood' snapshot if this fails | |||
# 'force_reset' - roll back to 'lastgood' snapshot even if test was successful (supported on QEMU backend only) |
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 wonder if we shouldn't name 'QEMU backend' the default - sounds less scary :)
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.
Right, we don't mention it above as well. I will replace with something like "if supported by backend"
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.
It didn't bother me on the first review - but I just had the thought that force_reset sounds a lot like a boot of the SUT. In the light of 'norollback', how about always_rollback (and possibly renaming norollback to no_rollback).
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 also thought about different name, but grabbed one from the progress ticket. As we use norollback just in a single place, it's easy change. So +1 here.
docs/WritingTests.asciidoc
Outdated
@@ -40,8 +40,9 @@ openQA tests need to implement at least the *run* subroutine to | |||
contain the actual test code and the test needs to be loaded in the distribution's | |||
main.pm. | |||
|
|||
The *test_flags* subroutine specifies what happens when the test | |||
fails. | |||
The *test_flags* subroutine specifies what should happen when test execution is finished. |
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.
In before it stated "if test fails" which would refer to each failure within a job. Now it states "when test execution is finished" which I consider ambiguous. How about "when the execution of the current test module finishes depending on the result …"
11aff4a
to
35b151e
Compare
3ec364b
to
c690d54
Compare
Test for the change is in progress. Looking for a suiting place for it. |
4f4631e
to
279ffb1
Compare
279ffb1
to
8e13bc1
Compare
af6dc3d
to
4969be6
Compare
|
||
; | ||
ALTER TABLE job_modules ADD COLUMN always_rollback integer DEFAULT 0 NOT NULL; |
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.
this doesn't work - you need a new schema version
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.
Unfortunately, I was able only to find the documentation to introduce changes to the DB this way. Do you think @Martchus can give me a hand here?
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 can, but I usually just go through these steps myself: https://github.com/os-autoinst/openQA/blob/master/docs/Contributing.asciidoc#managing-the-database
You forgot step 1. here (updating the schema version number) and instead overwrote the previous migration files.
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.
Ah, I see. Will fix that. Thanks a lot!
2465bab
to
c2cf168
Compare
I'm still missing a commit in Schema.pm |
6bd2c94
to
499200e
Compare
@coolo sorry, messed up this PR with reverts, so now it can be looked at. |
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 good now.
It conflicts with #1835 so the PR which is merged last needs to rebase.
@Martchus your call then in which order. 1835 is more urgent, but I expect you to be more fluent in rebaing |
@coolo as this PR is not urgent, I can also take my time for rebasing, so no issue with that. |
Rebasing should be quite easy in this case so it doesn't really matter - I've just noted it. |
499200e
to
dd4ac14
Compare
Conflict resolved. Should be fine now. |
Please, merge only after os-autoinst change.
See poo#30775.