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

tests: fix failing header acceptance test #20347

Merged
merged 1 commit into from
Apr 8, 2020

Conversation

azul
Copy link
Contributor

@azul azul commented Apr 7, 2020

The username is listed in a div with class fullname now.

The username is listed in a div with class `fullname` now.

Signed-off-by: Azul <azul@riseup.net>
@azul azul force-pushed the test/fix-failing-acceptance branch from 951ed57 to 62f7e6b Compare April 7, 2020 12:57
@azul
Copy link
Contributor Author

azul commented Apr 7, 2020

Looks like there are acceptance tests in 3 files failing right now:

    /nextcloud/tests/acceptance/features/app-comments.feature:21
    /nextcloud/tests/acceptance/features/app-comments.feature:233
    /nextcloud/tests/acceptance/features/app-comments.feature:288
    /nextcloud/tests/acceptance/features/app-comments.feature:308
    /nextcloud/tests/acceptance/features/app-files-sharing-link.feature:26
    /nextcloud/tests/acceptance/features/app-files-sharing-link.feature:135
    /nextcloud/tests/acceptance/features/header.feature:24
    /nextcloud/tests/acceptance/features/header.feature:31
    /nextcloud/tests/acceptance/features/header.feature:44
    /nextcloud/tests/acceptance/features/header.feature:65

This one fixes the last.

I'm happy to continue working on these to get a green CI.
Is there a way to get screenshots or html dumps of failing acceptance tests?
I'm currently running them with

tests/acceptance/run.sh features/app-comments.feature

Is there a faster way that keeps the docker containers up or runs them in the main system?

@gary-kim
Copy link
Member

gary-kim commented Apr 7, 2020

You're probably not going to get reliable green CI. There seem to be some agents on the CI system that are really slow for some reason so @nextcloud/infrastructure probably has to deal with that. Of course, nothing bad about trying to get the tests we have to be correct!

BTW, I also host drone instances so let me know if I can be of help with that?

Is there a faster way that keeps the docker containers up or runs them in the main system?

Take a look at the drone exec command in the Drone CLI

@gary-kim gary-kim added 3. to review Waiting for reviews bug labels Apr 7, 2020
@skjnldsv
Copy link
Member

skjnldsv commented Apr 8, 2020

You're probably not going to get reliable green CI.

We improved a lot lately on lowering the load on our CI infrastructure :)
We got some green before, no reason it should not again 🙈

Thanks a lot for the fix on header! Works nicely!!

@skjnldsv skjnldsv requested a review from danxuliu April 8, 2020 05:08
@gary-kim
Copy link
Member

gary-kim commented Apr 8, 2020

We got some green before, no reason it should not again see_no_evil

It's basically like a betting game. If you do it wrong, of course you lose. If you do it right, then maybe, just maybe, you'll get green ✔️ . :)

@skjnldsv skjnldsv merged commit bb93799 into nextcloud:master Apr 8, 2020
@welcome
Copy link

welcome bot commented Apr 8, 2020

Thanks for your first pull request and welcome to the community! Feel free to keep them coming! If you are looking for issues to tackle then have a look at this selection: https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22

@skjnldsv skjnldsv added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Apr 8, 2020
@azul azul deleted the test/fix-failing-acceptance branch April 8, 2020 07:50
@rullzer rullzer mentioned this pull request Apr 8, 2020
80 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4. to release Ready to be released and/or waiting for tests to finish bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants