[Gluster-devel] Quick Update: a cleanup patch and subsequent build failures

2019-06-14 Thread Amar Tumballi Suryanarayan
I just merged a larger cleanup patch, which I felt is good to get in, but
due to the order of its parents when it passed the regression and smoke,
and the other patches which got merged in same time, we hit a compile issue
for 'undefined functions'.

Below patch fixes it:

glfs: add syscall.h after header cleanup

in one of the recent patches, we cleaned-up the unneccesary header
file includes. In the order of merging the patches, there cropped
up an compile error.

updates: bz#1193929
Change-Id: I2ad52aa918f9c698d5273bb293838de6dd50ac31
Signed-off-by: Amar Tumballi 

diff --git a/api/src/glfs.c b/api/src/glfs.c
index b0db866441..0771e074d6 100644
--- a/api/src/glfs.c
+++ b/api/src/glfs.c
@@ -45,6 +45,7 @@
 #include 
 #include "rpc-clnt.h"
 #include 
+#include 

 #include "gfapi-messages.h"
 #include "glfs.h"

-
The patch has been pushed to repository, as it is causing critical compile
error right now. and if you have a build error, please fetch the latest
master to fix the the issue.

Regards,
Amar
___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel



[Gluster-devel] Project Update: Containers-based distributed tests runner

2019-06-14 Thread Aravinda
**gluster-tester** is a framework to run existing "*.t" test files in
parallel using containers.

Install and usage instructions are available in the following
repository.

https://github.com/aravindavk/gluster-tester

## Completed:
- Create a base container image with all the dependencies installed.
- Create a tester container image with requested refspec(or latest
master) compiled and installed.
- SSH setup in containers required to test Geo-replication
- Take `--num-parallel` option and spawn the containers with ready
infra for running tests
- Split the tests based on the number of parallel jobs specified.
- Execute the tests in parallel in each container and watch for the
status.
- Archive only failed tests(Optionally enable logs for successful tests
using `--preserve-success-logs`)

## Pending:
- NFS related tests are not running since the required changes are
pending while creating the container image. (To know the failures run
gluster-tester with `--include-nfs-tests` option)
- Filter support while running the tests(To enable/disable tests on the
run time)
- Some Loop based tests are failing(I think due to shared `/dev/loop*`)
- A few tests are timing out(Due to this overall test duration is more)
- Once tests are started, showing real-time status is pending(Now
status is checked in `/regression-.log` for example
`/var/log/gluster-tester/regression-3.log`
- If the base image is not built before running tests, it gives an
error. Need to re-trigger the base container image step if not built.
(Issue: https://github.com/aravindavk/gluster-tester/issues/11)
- Creating an archive of core files
- Creating a single archive from all jobs/containers
- Testing `--ignore-from` feature to ignore the tests
- Improvements to the status output
- Cleanup(Stop test containers, and delete)

I opened an issue to collect the details of failed tests. I will
continue to update that issue as and when I capture failed tests in my
setup.
https://github.com/aravindavk/gluster-tester/issues/9

Feel free to suggest any feature improvements. Contributions are
welcome.
https://github.com/aravindavk/gluster-tester/issues

--
Regards
Aravinda
http://aravindavk.in


___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel



Re: [Gluster-devel] Seems like Smoke job is not voting

2019-06-14 Thread Amar Tumballi Suryanarayan
Ok, guessed the possible cause.

The same possible DNS issue with review.gluster.org could have prevented
the patch fetching in smoke, and hence would have not triggered the job.

Those of you who have patches not getting a smoke, please run 'recheck
smoke' through comment.

-Amar

On Fri, Jun 14, 2019 at 5:16 PM Amar Tumballi Suryanarayan <
atumb...@redhat.com> wrote:

> I see patches starting from 10:45 AM IST (7hrs before) are not getting
> smoke votes.
>
> For one of my patch, the smoke job is not triggered at all IMO.
>
> https://review.gluster.org/#/c/22863/
>
> Would be good to check it.
>
> Regards,
> Amar
>
>

-- 
Amar Tumballi (amarts)
___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel



[Gluster-devel] Seems like Smoke job is not voting

2019-06-14 Thread Amar Tumballi Suryanarayan
I see patches starting from 10:45 AM IST (7hrs before) are not getting
smoke votes.

For one of my patch, the smoke job is not triggered at all IMO.

https://review.gluster.org/#/c/22863/

Would be good to check it.

Regards,
Amar
___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel



Re: [Gluster-devel] [Gluster-infra] DNS issue on review.gluster.org, causing outage

2019-06-14 Thread Michael Scherer
Le vendredi 14 juin 2019 à 10:10 +0200, Michael Scherer a écrit :
> Hi,
> 
> there is a ongoing issue regarding review.gluster.org, with some
> people
> being directed to the wrong server. 
> 
> A quick fix is to add: 
> 8.43.85.171  review.gluster.org 
> 
> to /etc/hosts (on Linux)
> 
> 
> 
> Adding a MX record yesterday (due to a RH IT request) do result into
> the domain name having 2 IP address, one pointing to supercolony (the
> MX), one to the gerrit server. That is neither the intention, nor
> what
> is supposed to happen, so I kinda suspect that's a bug somewhere (or
> a
> corner case, or me misreading the RFC).
> 
> Investigation is ongoing. 
> 
> Review.gluster.org may still work for some people (like, it work for
> me
> and still work for me), hence why it wasn't noticed while I tested,
> apology for that.

Ok so the issue should now be fixed. See 
https://bugzilla.redhat.com/show_bug.cgi?id=1720453 

(sorry forgot to send the email about the fix, too focused on the post
mortem)

-- 
Michael Scherer
Sysadmin, Community Infrastructure





signature.asc
Description: This is a digitally signed message part
___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel



[Gluster-devel] DNS issue on review.gluster.org, causing outage

2019-06-14 Thread Michael Scherer
Hi,

there is a ongoing issue regarding review.gluster.org, with some people
being directed to the wrong server. 

A quick fix is to add: 
8.43.85.171  review.gluster.org 

to /etc/hosts (on Linux)



Adding a MX record yesterday (due to a RH IT request) do result into
the domain name having 2 IP address, one pointing to supercolony (the
MX), one to the gerrit server. That is neither the intention, nor what
is supposed to happen, so I kinda suspect that's a bug somewhere (or a
corner case, or me misreading the RFC).

Investigation is ongoing. 

Review.gluster.org may still work for some people (like, it work for me
and still work for me), hence why it wasn't noticed while I tested,
apology for that.
-- 
Michael Scherer
Sysadmin, Community Infrastructure





signature.asc
Description: This is a digitally signed message part
___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel



[Gluster-devel] Gerrit is down

2019-06-14 Thread Deepshikha Khandelwal
Hello,

review.gluster.org is down since morning. We are looking into the issue.

Will update once it is back.
___

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel