On 11/18/2016 02:41 AM, Fam Zheng wrote:
On Thu, 11/17 20:02, Ramon Medeiros wrote:OK
Hi,Fixed by defaulting the EDITOR to 'vi' if empty, please try again.
just got a minor issue while installing the slave, opened a issue
https://github.com/patchew-project/patchew/issues/12.
Added patchew to wheel groupAfter that, when tried to add a test, i was unable to do it, receivingFixed an ACL bug in server, please try again. The "PATCHEW_UESR" and
forbiden as error. I tried to add my Unit tests, that must be run by root or
by user with sudo privilege, and i need to run:
# autogen files and run unit tests (make check)
autogen.sh --system && make && make check
What i did wrong? Just put root as user
"PATCHEW_PASS" are for authentication with patchew.org, the local user to run
test scripts are always patchew, please add it to sudoers manually if you want
passwordless sudo.
On 11/17/2016 04:34 PM, Fam Zheng wrote:
On Thu, 11/17 15:00, Ramon Medeiros wrote:--
Nice, i want it.Thanks, I'll look into supporting subprojects in patchew!
About the subprojects, they have separated repos, some of them share the
same ML:
github.com/kimchi-project/kimchi/ ->
http://lists.ovirt.org/pipermail/kimchi-devel/ Tag [Kimchi]
github.com/kimchi-project/wok/ ->
http://lists.ovirt.org/pipermail/kimchi-devel/ Tag [Wok]
github.com/kimchi-project/ginger/ ->
https://groups.google.com/forum/#!forum/ginger-dev-list Tag [ginger]
github.com/kimchi-project/gingerbase ->
https://groups.google.com/forum/#!forum/ginger-dev-list Tag [gingerbase]
I'll create an account for you shortly and send you the initial password
How i can proceed to create the testing machine?
off-list. With that, login here:
http://patchew.org/login/
Then change the password yourself:
http://patchew.org/admin/password_change/
Then goto checkout the Kimchi project config page:
[*] http://patchew.org/Kimchi/info
There will be two sections only visible after you login, "Email notifications"
and "Testing configuration". We'll get back to them after setting up the tester.
Setting up tester machine is as easy as:
$ git clone https://github.com/patchew-project/patchew
$ cd patchew
# $machine_name is as in your ssh config
$ ./scripts/deploy-tester $machine_name
It will prompt you to edit a tester config file template, fill in
username/password of the tester account (which I'll send you off-list too),
like:
# Patchew tester deploy config:
PATCHEW_SERVER=http://patchew.org
PATCHEW_UESR=
PATCHEW_PASS=
PATCHEW_TESTER_PROJECT=Kimchi
Save and quit the editor, the script will go on to scp files, create user and
systemd service on the remote machine. BTW it is better use a VM or a dedicated
test machine because the deploy-tester messes arond with root privilege,
although the testing code will run as an unprivileged user), and start the
tester.
You can then login to $machine_name and check the status with:
# systemctl status patchew-tester
The daemon runs "patchew tester -p Kimchi" in background for you, which
periodically polls patchew.org for new patches to test. Once there are any, it
will download and execute whatever commands as configured at [*] page.
With the tester started, we can go back to [*] page and add a test. Under
"Testing configuration", click "Add Test", and fill in a name for the test, the
new test will be created in the pad.
The only necessary change to make is "Test script" which is what to execute by
the tester for each applied patch. The default script is "exit 0" but you can
change to anything you want the tester to run. Other options can be left
default.
Once you are done, click "Save" and watch the patchew-tester fetching and
executing tests. When tests are done, results will be visible on the web.
Let me know if you have any trouble doing above, I'll try my best to help you
out.
Fam
On 11/17/2016 02:52 PM, Fam Zheng wrote:
On Thu, 11/17 14:22, Ramon Medeiros wrote:--
I want to use Patchew for it. My propose with patchew was:Yes and no. Patchew currently assumes each mailing list has only one repo, so I
Every patch sent to Kimchi mailing list and subprojects (see wok, ginger and
gingerbase) will be merged in a branch and run make check (unit tests).
As I saw, the merging part is working yet:
http://patchew.org/Kimchi/1479226967-13054-1-git-send-email-archus@xxxxxxxxxxxxxxxxxx/
need to know how subprojects are distinguished (e.g. subject prefix [wok]?) in
Kimchi, and then implement a subproject-aware logic. For example:
http://patchew.org/Kimchi/1477404741-17641-1-git-send-email-dhbarboza82@xxxxxxxxx/
An email from patchew will be sent to verify if patch is working or notYes, running tests and sending emails are already supported and we are using it
Do you think patchew can handle this? I know that patchew has a
customization for adding a script to run tests.
for qemu:
https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg03409.html
So without waiting for patchew support of subproject, we can already start
testing patches for the main Kimchi repo. To do that you'd need to prepare a
test machine that runs "patchew-cli tester -p Kimchi" which polls patchew server
for newly indexed patches and execute the distributed tests.
Fam
Ramon Nunes Medeiros
Kimchi Developer
Linux Technology Center Brazil
IBM Systems & Technology Group
Phone : +55 19 2132 7878
ramonn@xxxxxxxxxx
Ramon Nunes Medeiros
Kimchi Developer
Linux Technology Center Brazil
IBM Systems & Technology Group
Phone : +55 19 2132 7878
ramonn@xxxxxxxxxx