https://bugzilla.redhat.com/show_bug.cgi?id=1381433
Nigel Babu changed:
What|Removed |Added
Status|MODIFIED|CLOSED
Resolution|---
https://bugzilla.redhat.com/show_bug.cgi?id=1381433
--- Comment #9 from Pranith Kumar K ---
Did that once, but didn't help. Since we anyway need smoke.sh to get better,
that seemed like a better approach for now. I will be submitting a pull request
today sometime. Let's see.
--
You are receiv
https://bugzilla.redhat.com/show_bug.cgi?id=1381433
--- Comment #8 from Nigel Babu ---
Hrm, have you thought of changing the gluster commit, rebuilding, and trying
smoke again? That seems to be difference between "first time" and later
attempts.
--
You are receiving this mail because:
You are
https://bugzilla.redhat.com/show_bug.cgi?id=1381433
--- Comment #7 from Pranith Kumar K ---
Created attachment 1211787
--> https://bugzilla.redhat.com/attachment.cgi?id=1211787&action=edit
Collect statedumps before bricks/mounts are killed in smoke.sh
Attaching the modified smoke.sh, Can we
https://bugzilla.redhat.com/show_bug.cgi?id=1170966
Niels de Vos changed:
What|Removed |Added
Status|NEW |CLOSED
Resolution|---
https://bugzilla.redhat.com/show_bug.cgi?id=1381433
--- Comment #6 from Pranith Kumar K ---
Nigel,
There is some peculiar behavior, like Milind was mentioning yesterday, it
happened only the first time and never after that. Wonder what the trigger is.
I think the best way forward for this
https://bugzilla.redhat.com/show_bug.cgi?id=1170966
Kaushal changed:
What|Removed |Added
CC||kaus...@redhat.com
--- Comment #3 from Kaus
https://bugzilla.redhat.com/show_bug.cgi?id=1231686
Niels de Vos changed:
What|Removed |Added
Flags||needinfo?(nig...@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1170966
Niels de Vos changed:
What|Removed |Added
Status|CLOSED |NEW
Resolution|WORKSFORME
https://bugzilla.redhat.com/show_bug.cgi?id=1170966
Nigel Babu changed:
What|Removed |Added
Status|NEW |CLOSED
CC|
https://bugzilla.redhat.com/show_bug.cgi?id=1231686
Nigel Babu changed:
What|Removed |Added
CC||nig...@redhat.com
--- Comment #7 from Ni
https://bugzilla.redhat.com/show_bug.cgi?id=1380247
--- Comment #1 from Nigel Babu ---
So, the statedumps are dumped to /var/run and there's no easy way to predict
the names of the files.
The best way to go about it:
0. At the start of the job remove any files older than 15 days from
/var/log
https://bugzilla.redhat.com/show_bug.cgi?id=1381433
Nigel Babu changed:
What|Removed |Added
Status|NEW |MODIFIED
--- Comment #5 from Nigel Babu
https://bugzilla.redhat.com/show_bug.cgi?id=1379209
Nigel Babu changed:
What|Removed |Added
Status|VERIFIED|CLOSED
Resolution|---
https://bugzilla.redhat.com/show_bug.cgi?id=1386132
Nigel Babu changed:
What|Removed |Added
Status|NEW |MODIFIED
--- Comment #1 from Nigel Babu
https://bugzilla.redhat.com/show_bug.cgi?id=1386132
Bug ID: 1386132
Summary: Need a NetBSD slave to debug a crash that is only seen
in netbsd
Product: GlusterFS
Version: mainline
Component: project-infrastructure
A
16 matches
Mail list logo