Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1551879

Summary: ERROR: test_it (bkr.inttest.server.selenium.test_job_matrix.TestJobMatrix)
Product: [Retired] Beaker Reporter: Roman Joost <rjoost>
Component: testsAssignee: Martin Styk <mastyk>
Status: CLOSED CURRENTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: developCC: mastyk
Target Milestone: 28.0   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-25 10:35:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1550312    
Attachments:
Description Flags
Failure log with captured output
none
Last screen shot from the browsers point of view none

Description Roman Joost 2018-03-06 04:26:10 UTC
Description of problem:

An integration test is intermittently failing in our dogfood test suite:
======================================================================
ERROR: test_it (bkr.inttest.server.selenium.test_job_matrix.TestJobMatrix)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/bkr/inttest/server/selenium/test_job_matrix.py", line 270, in test_it
    '//div[@class="dataTables_scrollHeadInner"]/table[1]/thead')
  File "/usr/lib64/python2.7/site-packages/selenium/webdriver/remote/webdriver.py", line 290, in find_element_by_xpath
    return self.find_element(by=By.XPATH, value=xpath)
  File "/usr/lib64/python2.7/site-packages/selenium/webdriver/remote/webdriver.py", line 744, in find_element
    {'using': by, 'value': value})['value']
  File "/usr/lib64/python2.7/site-packages/selenium/webdriver/remote/webdriver.py", line 233, in execute
    self.error_handler.check_response(response)
  File "/usr/lib64/python2.7/site-packages/selenium/webdriver/remote/errorhandler.py", line 194, in check_response
    raise exception_class(message, screen, stacktrace)
NoSuchElementException: Message: Unable to locate element: {"method":"xpath","selector":"//div[@class=\"dataTables_scrollHeadInner\"]/table[1]/thead"}
Stacktrace:
    at FirefoxDriver.prototype.findElementInternal_ (file:///tmp/tmpUXGp8S/extensions/fxdriver/components/driver-component.js:10770)
    at fxdriver.Timer.prototype.setTimeout/<.notify (file:///tmp/tmpUXGp8S/extensions/fxdriver/components/driver-component.js:625)

Version-Release number of selected component (if applicable):
develop

How reproducible:
not sure

Steps to Reproduce:
1.
2.
3.

Actual results:
fail

Expected results:
pass

Additional info:

Comment 1 Roman Joost 2018-03-06 04:39:07 UTC
This failing test seems to be occurring only on RHEL7. At least I'm having trouble finding a RHEL6 job with this failing test for now.

Comment 2 Dan Callaghan 2018-03-19 05:30:42 UTC
Something else interesting I noticed on the known issues graph:

https://beaker-project.org/~dcallagh/dogfoodstats/known-issues.html

The issue occurred very occasionally before October 2017 but then the frequency suddenly increased. Around the very same time, the overall running time of dogfood jobs dramatically increased (either Beaker itself, or some of the tests in the test suite, got a lot slower):

https://beaker-project.org/~dcallagh/dogfoodstats/running-time.html

It would be possible to schedule dogfood with a few selected builds of Beaker, and compare them, to isolate which change caused the slow-down around October 2017. However since it happened during the 25.0 development cycle, the most likely culprit is bug 911515 or, maybe more likely, the supporting changes in the scheduler in bug 1519589.

Comment 3 Roman Joost 2018-07-26 22:25:58 UTC
Created attachment 1470899 [details]
Failure log with captured output

Comment 4 Roman Joost 2018-07-26 22:29:11 UTC
Created attachment 1470900 [details]
Last screen shot from the browsers point of view

I added code in the cleanup for Firefox to snap a screen shot, which should be the last view the browser has seen before it has gotten cleaned up.

The list the test filters seems to be unfiltered. No error is shown and no table has been generated. So either it is not the last screen shot the browser saw, or something else happened on the browser side ...