client
client copied to clipboard
owncloud
Scenario "Syncing a file from the server and creating a conflict" fails intermittently
The test failed in nightly build on step Then the table of conflict warnings should include file "conflict.txt though it is passing locally.
LookupError: Object '{column='1' container={container={container={container={name='stack' type='QStackedWidget' visible='1' window={name='Settings' type='OCC::SettingsDialog' visible='1'}} name='qt_tabwidget_stackedwidget' type='QStackedWidget' visible='1'} name='OCC__IssuesWidget' type='OCC::IssuesWidget' visible='1'} name='_tableView' type='QTableView' visible='1'} text~='conflict \\(conflicted copy \\d{4}-\\d{2}-\\d{2} \\d{6}\\)\\.txt' type='QModelIndex'}' not found. Could not match properties:
container for object name: '{column='1' container={container={container={container={name='stack' type='QStackedWidget' visible='1' window=:settings_OCC_SettingsDialog} name='qt_tabwidget_stackedwidget' type='QStackedWidget' visible='1'} name='OCC__IssuesWidget' type='OCC::IssuesWidget' visible='1'} name='_tableView' type='QTableView' visible='1'} text~='conflict \\(conflicted copy \\d{4}-\\d{2}-\\d{2} \\d{6}\\)\\.txt' type='QModelIndex'}'
container for object name: '{container={container={container={name='stack' type='QStackedWidget' visible='1' window=:settings_OCC_SettingsDialog} name='qt_tabwidget_stackedwidget' type='QStackedWidget' visible='1'} name='OCC__IssuesWidget' type='OCC::IssuesWidget' visible='1'} name='_tableView' type='QTableView' visible='1'}'
visible for object name: '{container={container={name='stack' type='QStackedWidget' visible='1' window=:settings_OCC_SettingsDialog} name='qt_tabwidget_stackedwidget' type='QStackedWidget' visible='1'} name='OCC__IssuesWidget' type='OCC::IssuesWidget' visible='1'}'
This scenario was skipped in client version 2.10. After the release of the client version 3.0, we unskipped the scenario to check if it fails on version 3.0 too or not. On the first run on the CI, the test was passing but later on, the test started failing so we again skipped the scenario so that we could focus more on other intermittently appearing failures as they were of high priority.
