Hi,
Yes, I can easily add additional 2 second sleep.
But, the problem here is: irrespective of anything(especially these
timing changes), it should not create any additional changelog.
It is a test volume created for test purpose where no I/O is carried out.
So, we may end up putting band-aid to some other problem.
I will look into this, if we see this issue again as it seems spurious.
Please let me know if any issue.
PS:
Issue is actually in Centos, not in NetBSD.
Thanks,
Saravana
On 01/19/2016 12:08 PM, Ravishankar N wrote:
On 01/19/2016 12:01 PM, Venky Shankar wrote:
Saravanakumar Arumugam wrote:
Hi Ravi,
I can run this locally, seems like spurious.
Works fine on Linux for me too.Maybe its observed easily on BSD.
Let me know if you see again.
To be safe, it would benefit to have sleep(1) before the check.
yes, or " EXPECT_WITHIN $SOME_NEW_TIMEOUT 1 count_changelog_files
$B0/${V0}1"
Please correct my email id, you are addressing another Saravana :)
Sorry, noted. :)
Thanks,
Saravana
On 01/19/2016 09:42 AM, Venky Shankar wrote:
Ravishankar N wrote:
Hi Saravna,
./tests/bugs/changelog/bug-1208470.t seems to have failed a NetBSD
run:
https://build.gluster.org/job/rackspace-regression-2GB-triggered/17651/consoleFull
Not sure if it is spurious as it passed in the subsequent run. Please
have a look.
Might be too soon to check the presence of the changelog file after
enabling changelog.
Thanks,
Ravi
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
Venky
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
Venky
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
