Skip to content
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

Folder/File wait to be synced steps fails intermittently #9783

Closed
2 tasks done
sushmita56 opened this issue Jun 9, 2022 · 8 comments
Closed
2 tasks done

Folder/File wait to be synced steps fails intermittently #9783

sushmita56 opened this issue Jun 9, 2022 · 8 comments
Labels

Comments

@sushmita56
Copy link
Contributor

sushmita56 commented Jun 9, 2022

Pre-submission Checks

  • I checked for similar issues, but could not find any. I also checked the closed issues. I could not contribute additional information to any existing issue.
  • I will take the time to fill in all the required fields. I know that the bug report may be dismissed otherwise due to lack of information.

Describe the bug

The following scenario from the tst_syncing suite is failing in CI on step And the user waits for folder "myFolder" to be synced but is passing locally.

    Scenario Outline: Syncing a folder to the server
        Given user "Alice" has set up a client with default settings
        When user "Alice" creates a folder <foldername> inside the sync folder
        And the user waits for folder <foldername> to be synced
        Then as "Alice" folder <foldername> should exist on the server
        Examples:
            | foldername                                                               |
            | "myFolder"                                                               |
            | "really long folder name with some spaces and special char such as $%ñ&" |
            | "folder with space at end "                                              |

Expected behavior

Expected folder '/tmp/client-bdd/Alice/myFolder' to be synced.

Steps to reproduce the issue

No response

Screenshots

No response

Logs

https://cache.owncloud.com/public/owncloud/client/12067/guiReportUpload/index.html
https://drone.owncloud.com/owncloud/client/12067

No response

Client version number

ubuntu version: 22.04
client version: 3.0
qt version: 5.15

Desktop environment (Linux only)

No response

Client package version and origin (Linux only)

No response

Installation path (Windows only)

No response

Server information

No response

Additional context

No response

@sushmita56
Copy link
Contributor Author

sushmita56 commented Jun 15, 2022

The error message in GUI log is something like this
Screenshot from 2022-06-15 11-04-00

@amrita-shrestha
Copy link
Contributor

failed in different scenarios due to the same reason

    Scenario: Syncing folders each having 500 files
        Given user "Alice" has set up a client with default settings
        And the user has created a folder "folder1" with "500" files each of size "1048576" bytes in temp folder
        And the user has created a folder "folder2" with "500" files each of size "1048576" bytes in temp folder
        When user "Alice" moves folder "folder1" from the temp folder into the sync folder
        And user "Alice" moves folder "folder2" from the temp folder into the sync folder
        And the user waits for folder "folder1" to be synced
        And the user waits for folder "folder2" to be synced
        Then as "Alice" folder "folder1" should exist on the server
        And as user "Alice" folder "folder1" should contain "500" items on the server
        And as "Alice" folder "folder2" should exist on the server
        And as user "Alice" folder "folder2" should contain "500" items on the server

GUI LOG: https://cache.owncloud.com/public/owncloud/client/12420/guiReportUpload/index.html

Server Logs: https://cache.owncloud.com/public/owncloud/client/12420/guiReportUpload/serverlog.log

Screenshot:
Screenshot from 2022-07-08 13-07-19

@amrita-shrestha amrita-shrestha changed the title Scenario Scenario Outline: Syncing a folder to the server fails intermittently Folder/File syncing steps fails intermittently Jul 8, 2022
@amrita-shrestha amrita-shrestha changed the title Folder/File syncing steps fails intermittently Folder/File wait to be synced steps fails intermittently Jul 8, 2022
@amrita-shrestha amrita-shrestha added the p2-high Escalation, on top of current planning, release blocker label Jul 11, 2022
@sushmita56 sushmita56 self-assigned this Jul 12, 2022
@sushmita56 sushmita56 removed the p2-high Escalation, on top of current planning, release blocker label Jul 13, 2022
@sushmita56
Copy link
Contributor Author

Not reproducible in CI #9914
Build: https://drone.owncloud.com/owncloud/client/12489

@sushmita56
Copy link
Contributor Author

Though the scenario passes in CI, it fails locally with the error Connect could not be established, try again later.

Screenshot from 2022-07-20 09-53-01

And on debugging we found that the failure was because the connection with the socket could not be established. If we add a wait of around 2 seconds, the test passes locally too. But as the test is not failing recently on CI, for now, we can stop investigating this issue.

@sushmita56 sushmita56 removed their assignment Jul 20, 2022
@sushmita56
Copy link
Contributor Author

sushmita56 commented Jul 22, 2022

The file syncing problem is found to be a reason behind the failure of this scenario.
Currently, the sync issue is under investigation so this issue is unassigned for now.

@amrita-shrestha
Copy link
Contributor

I think this issue is related to: #9952 (comment)

@sushmita56
Copy link
Contributor Author

This issue seems to be similar to the issue #9952 as the screenshot generated by this issue's debugging PR is exactly the same as the screenshot reported in the issue #9952. Previously the debugging PR was passing on CI but on the later run, it failed on step And the user waits for folder 'folder with space at end ' to be synced
Screenshot from 2022-08-01 13-02-38

Screenshot generated:

Screenshot from 2022-08-01 12-59-07

So I think this issue can now be closed in reference to #9952, however, the problem of socket connection is still there while running the scenario locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants