-
Notifications
You must be signed in to change notification settings - Fork 205
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
Also show "investigation" tabs for incomplete jobs #3981
Also show "investigation" tabs for incomplete jobs #3981
Conversation
d576a05
to
171999f
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.
# Failed test 'previous job identified as last good and it is a hash'
# at t/10-jobs.t line 473.
# got: ''
# expected: 'HASH'
# Looks like you failed 1 test of 4.
# Failed test 'additional investigation notes provided on new failed'
# at t/10-jobs.t line 489.
# Looks like you failed 1 test of 10.
# Failed test 'carry over, including soft-fails'
171999f
to
85498ce
Compare
85498ce
to
926f616
Compare
926f616
to
4d3c745
Compare
4d3c745
to
d9bf1c4
Compare
d9bf1c4
to
8bbabcb
Compare
I split out #4300 to narrow down on any failing parts (if any) |
Codecov Report
@@ Coverage Diff @@
## master #3981 +/- ##
=======================================
Coverage 97.95% 97.95%
=======================================
Files 374 374
Lines 34006 34010 +4
=======================================
+ Hits 33312 33316 +4
Misses 694 694
Continue to review full report at Codecov.
|
8bbabcb
to
e72b3ac
Compare
e72b3ac
to
2558727
Compare
Ready for review, waiting for second approval |
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.
Code looks nice.
Would you please also add a test for it?
On 12/01/2022 14.10, kalikiana wrote:
***@***.**** requested changes on this pull request.
Code looks nice.
Would you please also add a test for it?
I don't want to
|
If this is a joke I don't get it. |
It's no joke. We already have sufficient statement coverage and the only risk I see is that the investigation tab does not show up which I covered manually |
Also in case of incomplete jobs the problem can be caused by something that the investigation tab could reveal, e.g. invalid test code that causes the job to abort prematurely with incomplete. Also this commit changes the hard-coded job state decision in OpenQA::Schema::Result::Jobs to use constant function based decisions. Related progress issue: https://progress.opensuse.org/issues/94792
2558727
to
daedcfb
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.
In sub investigate
your version of should_show_investigation
would likely make more sense but I suppose it doesn't matter because the client won't show the tab anyways until a final job state is reached.
Yes. That's why it's called "should show" not "will most definitely do show" ;) |
You didn't mention anything about why tests can't be added, or manual testing, in the description, commit message or ticket. Is it difficult to add? I would guess |
Oli took me up on my offer in chat, so I'll provide one shortly. |
You can just accept this PR as is :) |
I added a test. Probably shouldn't review it myself.
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.
@kalikiana your changes LGTM, you can approve again
Also in case of incomplete jobs the problem can be caused by something
that the investigation tab could reveal, e.g. invalid test code that
causes the job to abort prematurely with incomplete.
Related progress issue: https://progress.opensuse.org/issues/94792