GITHUB PRIVATE OCTERNSHIP ERROR ON TESTING FUNCTION !

[ManoBharathi93]

Did anyone who applied for github octernship have completed the task with 100 % test passed if so kindly reply to msg so that we get to know whether issue is from our side or not !

In github assigned private repo

• Does your implementation passes 100% of test in local development ?
• Does Your PR passes 100 % of test in GitHub CI/CD test coverage ?

If yes, then kindly shows us How do you setup the repo in local development.

[ManoBharathi93]

If anyone facing the same issue kindly acknowledge here...

[SumantxD]

@ManoBharathi93 Gald someone asked, I am facing similar issue, After i solved a ToDo list task i sent a PR to the public ivy repo, all the tests passed in the GitHub CI/CD, but when i send PR to private octernship repo none of the tests passes, i think it is due to the fact that , running CI/CD tests in a private repo will require spending limit to be increased under 'Billing & plans' which will require github pro membership , Really confused what to do 😞
I don't know if my application will be considered or not this way, should i like the PR in the description of the private PR , so that the team can see that the code works fine?
Or i can submit it the way it is?
PLZ respond if you are able to figure out any of these.

[bilal-aamer]

Well said @SumantxD, I am facing the same problem, however, how i understand it, our private repo as part of our GitHub Classroom assignment doesnt have the billing plan as in Ivy's public repo so thats why the said "Billings & plans" note.

Regarding the procedure to sumbit the private PR, looking for a review.

[Shourya742]

Hello Everyone, I am getting this specific error while running pytest ivy_tests/test_ivy/test_functional/test_experimental/test_core/test_manipulation.py::function_name. But the same works well with actual repository. If anyone can point out what might be the error. I have setup codebase via codespace.

Error Image

[ManoBharathi93]

This error is not caused by your Implementation. This is common error which occurs mainly on the private repo.

[Shourya742]

Any idea how to overcome this and test the implementation. Would be a great help!!!

[ManoBharathi93]

try to pass all the test using ivy main repo . then push that code in GitHub assigned private repo and merge it. this is what i done so far.

[bilal-aamer]

Any vote of confirmation or review by the Ivy staff yet @ManoBharathi93 for your private merged PR?

[ManoBharathi93]

KINDLY CHECK THE IVY DISCORD -> GENERAL SECTION.

[AlexandraPosta]

Hey guys!

There is no issue with your local setups. As mentioned here, it is an integration problem on our side. It is not related to the payment method, just test integration and out-of-date version of repositories.

[Aarsh2001]

Just a follow up on this, we'll soon implement CI testing on your repositories as well 🙂

[Shivam7-1]

Hii I am new to Octernships program
I am unable to apply for IVY Octernships Program getting Error Like this
" Oh oh, looks like you need to contribute a bit more to the GitHub community before you’re eligible for an Octernship. Check out our guide on how to contribute to open-source projects to learn how you can make a meaningful impact! Keep up the great work and you’ll be a perfect fit in no time! "
Can Anyone Tell me how much Should I Contribute to GitHub for Become Eligible For Octernship Program ?

[AlexandraPosta]

Please check here: #1 (comment)

[AKACHI-4]

I have a doubt that if two contributors contribute one single common frontend function so what will be happen ? like both of there contributions are accepted as octernship task or else ??

Please reply

[AlexandraPosta]

The contribution is made in your private Octernship repository, so technically you should not be able to see other implementations. As long as you reference one of the open tasks (green dot rather then purple) your implementation will be taken into consideration (please do not open PRs for hflip/vflip/sort/add_ , implementations for these functions will only be considered if the PR was made before the functions were merged in our codebase).