Skip to content

Conversation

@IsaacYangSLA
Copy link
Contributor

This is to verify if all CI tasks work as expected. Please don't merge it. Will close it once everything is verified.

@IsaacYangSLA
Copy link
Contributor Author

Please review and verify if details of two checks can be viewed. I am pretty sure the first one works without any issue. The second one, from gitlab.com, requires confirmation.

@anfeng
Copy link

anfeng commented Jan 31, 2020

@ericspod @atbenmurray @wyli can you review this PR? This allow all contributors to see detailed integration tests. Our runner machine has 2+ GPUs

Copy link
Contributor

@wyli wyli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks! it looks good and I only have two minor issues:

  • what happens to the GPU runner if we have concurrent push/PR events triggered?
  • is the Jenkinsfile in this PR unused? (please remove if that's the case)

@IsaacYangSLA
Copy link
Contributor Author

IsaacYangSLA commented Feb 3, 2020

There is a queue in gitlab for all CI jobs. So when there are more than one CI jobs with the same 'tag,' currently we only have 'test' and one runner handles that, jobs will be queued.

I will remove that Jenkinsfile. But this PR is not supposed to be merged. It's to demonstrate the CI jobs work in this configuration.

@IsaacYangSLA IsaacYangSLA changed the title This is just for test if public gitlab CI works. Please ignore this. PR to demonstrate that CI jobs work on gitlab.com w/ GPU runners. Please comment. Thank you. Feb 3, 2020
Include integration tests to see if GPU runner works.
@IsaacYangSLA IsaacYangSLA force-pushed the test_ci_please_ignore branch from a3bc9c8 to f517ea1 Compare February 3, 2020 17:28
@wyli
Copy link
Contributor

wyli commented Feb 4, 2020

changes included in #36

@wyli wyli closed this Feb 4, 2020
@wyli wyli mentioned this pull request Feb 4, 2020
@wyli wyli deleted the test_ci_please_ignore branch May 21, 2020 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants