Skip to content

Conversation

@jakob-fritz
Copy link
Collaborator

As I cannot push to master (which makes sense), this PR removes the cupy-test in gitlab, so that CI now succeeds again. Then failures can be detected easier.

Once, the cupy-tests are fixed, the updated code shall be merged in master and also the tests will be added again.

@jakob-fritz
Copy link
Collaborator Author

Updated the CI-file, so that the gitlab-ci is also triggered, when a new label is added (e.g. the label to start Gitlab-CI)

Combined in this PR, as both work on CI in general and gitlab-CI in particular

@brownbaerchen
Copy link
Contributor

Actually, I was planning to port some new things to GPU and make use of the cupy tests today. I would rather we skip the single test that runs in parallel and run the other tests for now.

@jakob-fritz
Copy link
Collaborator Author

@brownbaerchen we can also do that. I just readded the general tests and commented out the one test, that got stuck. So now it (hopefully) succeeds.

@brownbaerchen
Copy link
Contributor

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants