What is GIL?
GIL (Global interpreter Lock) is a mutex. Mutex is an mutual exclusion object used to prevent from two threads or more, to access the same piece of code. This piece of code also called ‘critical section’.
So GIL is Python’s way to ensure only one thread is running the code at any given time. It serializes the access to the interpreter and ensures that each thread gets exclusive access to the interpreter internals when running.
What is CSIT?
Continuous System Integration Tests. Basically, Suites of integration tests for testing OpenDaylight components (alone or with other projects as OpenStack for example).
If you are familiar with OpenStack testing, then you can say it’s very similar to Tempest scenario tests.
The tests are executed automatically by OpenDaylight’s Jenkins on the lab provided by the Linux Foundation and can also be executed manually be any user, using Robot framework the integration/test repository.
This post should help you to execute the tests in your environment and publish the results with Jenkins Robot plugin.
You can also find small section of common failures in the bottom of this post.
To obtain the tests, run:
git clone https://git.opendaylight.org/gerrit/integration/test
Hello. It’s been ages since my last post, sorry for that. Looks like my work and studies took over most of my time. But let’s not dwell in the past and move to the purpose of this post!
I have quite a lot of interaction with Jenkins lately and to be honest, I really don’t like using the Jenkins web interface. I’m always in favor of using good working CLI.
Unfortunately I couldn’t find any client that was good enough for what I’ve been doing with Jenkins. My requirements are pretty basic – 1. it should work, 2. it should cover enough of the different tasks I’m doing on Jenkins. I have been trying couple of clients, but each was either too basic, missing a lot of commands or either not working at some point.
One of the common questions I get from new Github users is: “How to send pull request for one commit?”
Common questions are great chance for a new post 🙂 So let’s see how we do it from the very beginning.
1. Clone your forked project:
git clone https://github.com/<your_username>/Dummy.git
A few days ago, while adding a new job to OpenStack Infra, I realized how difficult it must be for newcomers ( to OpenStack) to understand how OpenStack CI works and make new changes. The OpenStack Infra documentation coverage of each project is great and very detailed , but connecting the dots, which assembles the complete work-flow can be a complex task for anyone.
Hopefully this post can help for those who unfamiliar with OpenStack Infra. This is written in a form of ‘Q & A’. If you read this and find yourself still wondering about additional subjects, please let me know and I’ll make sure to add it here.