action #25862
closed
[sle][functional]pressing alt+N too fast so we skip preselected modules step during scc_registration
Added by asmorodskyi over 6 years ago.
Updated over 6 years ago.
Category:
Bugs in existing tests
- Subject changed from pressing alt+N too fast so we skip preselected modules step during scc_registration to [sle][functional]pressing alt+N too fast so we skip preselected modules step during scc_registration
- Priority changed from Normal to Urgent
- Due date set to 2017-10-25
adding to sprint 3 backlog 'cause it's urgent. Approved by PO
- Status changed from New to In Progress
- Assignee set to jorauch
I could not reproduce it locally so far
- Status changed from In Progress to Feedback
- Status changed from Feedback to In Progress
- Status changed from In Progress to Resolved
Since one week the issue described here didn't appear. Now scc_registration fails because of other reason.
- Status changed from Resolved to In Progress
I started 10 times verification testrun, and all passed. Now I have started 50 runs and will wait for the results and then update here.
- Assignee changed from jorauch to Anonymous
On my local machine, the same issue appeared once out of 30 testruns. http://f146.suse.detests/1567
I did a fix on it, will test it multiple times before I submit it.
- Status changed from In Progress to Resolved
PR merged. Very diligent investigation and verification. Thank you. I guess a verification run on production is not helpful here as we would need to run another 50 jobs on production and you did that already locally and the change is not invasive -> resolved.
- Status changed from Resolved to In Progress
yxu, the link you pasted is broken. I cannot find the same issue in the build 321.1
Right Oliver, with build 321.5 the issue didn't appear, however I doubt to close the ticket now.
I'm verifying the testcase in comment#19 for 100 times now on osd: job #1238407 till job #1238506
- Status changed from In Progress to Resolved
The problem observed in the description is actually resolved. Another issue that I observed and that appeared 1-10% of the time is different. If it appears again, we'll need to open a new ticket for it.
Also available in: Atom
PDF