ci/flaky runners

[juliusknorr]

ready to merge changes from tests in #4350

• use postgres for cypress which seems to stabilize the random failures a bit
• Change step order in mysql setup to give it some more time to be ready
• Use only github runners for oci for now

[cypress]

2 flaky tests on run #10513 ↗︎

0

147

1

0

2

Details:

ci/flaky runners
Project: Text	Commit: 55903fbc48
Status: Passed	Duration: 04:06 💡
Started: Jun 24, 2023 8:07 AM	Ended: Jun 24, 2023 8:11 AM

  sync.spec.js • 1 flaky test

View Output Video

Test		Artifacts
Sync > recovers from a lost connection		Output Screenshots

  api/UsersApi.spec.js • 1 flaky test

View Output Video

Test		Artifacts
The user mention API > fetches users with valid session		Output Screenshots

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[juliusknorr]

Will merge already to see how well this works during dependable updates. Reviews still welcome in case there is feedback I'll follow up.

[juliusknorr]

/backport to stable27

[juliusknorr]

/backport to stable26

[juliusknorr]

/backport to stable25

[backportbot-nextcloud]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b fix/foo-stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[backportbot-nextcloud]

The backport to stable26 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable26
git pull origin stable26

# Create the new backport branch
git checkout -b fix/foo-stable26

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable26

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[backportbot-nextcloud]

The backport to stable25 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable25
git pull origin stable25

# Create the new backport branch
git checkout -b fix/foo-stable25

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable25

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[mejo-]

Thanks, looks good to me 👌

[mejo-]

@juliushaertl shall we do manual backports of this to stable27/26/25?

[juliusknorr]

Yes, maybe combined with the cypress rework once merged