| 00:04.40 | *** join/#asterisk-dev snuff-work (~snuff-wor@210.9.148.102) |
| 00:04.40 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 00:19.02 | *** join/#asterisk-dev infobot (ibot@208.53.50.136) |
| 00:19.02 | *** topic/#asterisk-dev is Asterisk Development Discussion -=- http://www.asterisk.org/developers -=- Tier 2 and 3.14159265 support is in #asterisk -=- Check out our blog! blogs.asterisk.org -=- Follow on Twitter at @AsteriskDev |
| 05:23.57 | *** join/#asterisk-dev jkroon (~jkroon@197.184.50.21) |
| 05:56.02 | *** join/#asterisk-dev jkroon (~jkroon@165.16.203.57) |
| 06:47.21 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01:e0a:d:1111:9d6f:c41f:cfdd:993) |
| 07:08.20 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 09:47.55 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01cb0583d31d0049e0564f33d6e991.ipv6.abo.wanadoo.fr) |
| 12:00.31 | coreyfarrell | gtjoseph: I'm not sure what happened the first run of the testsuite asterisk-gate where I got 25 failed tests. I ran these tests locally and only 1 failed. I fixed the one failing test and no failures this run. |
| 12:00.48 | gtjoseph | hmmm |
| 12:01.22 | gtjoseph | different slave distros? |
| 12:01.57 | coreyfarrell | checking the pjsip test since that's what had 20 of the failures |
| 12:04.23 | coreyfarrell | both runs of pjsip were on centos7-64-slave4 |
| 12:04.59 | coreyfarrell | was weird too because all but the one legit failure looked like https://jenkins2.asterisk.org/view/Gates/job/gate-testsuite-ast-master-pjsip/1/testReport/junit/tests.channels/pjsip/acl_call/ |
| 12:05.18 | coreyfarrell | didn't print any error messages just said it failed. |
| 12:06.22 | gtjoseph | the log says core dumps detected |
| 12:07.15 | coreyfarrell | I don't see that |
| 12:07.43 | gtjoseph | maybe i'm looking at the wrong one |
| 12:09.35 | coreyfarrell | ah I do see one now for a different test. going to download the artifacts zip so I can search it easier. |
| 12:10.17 | gtjoseph | i've got too many jenkins windows open. i'm actually starting the migration to docker. :) |
| 12:11.04 | coreyfarrell | ok so that test run did have 3 backtraces, which is odd since this review doesn't actually touch Asterisk :/ |
| 12:14.45 | gtjoseph | maybe you uncovered something. :) |
| 12:17.50 | coreyfarrell | I just checked the 3 backtraces, none of them involved shutdown. no backtraces in the other tests, only pjsip crashes :/ |
| 12:17.54 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01:e0a:d:1111:5481:eb79:921d:e1b1) |
| 12:23.47 | coreyfarrell | gtjoseph: one of them says `Program terminated with signal 7, Bus error.`. is this a hardware failure? |
| 12:23.58 | gtjoseph | interesting |
| 12:24.08 | gtjoseph | maybe a VM issue |
| 12:24.20 | gtjoseph | let me look at slave4 |
| 12:24.39 | coreyfarrell | the other issues were legit (assuming that the crash wasn't caused by corrupted memory). |
| 12:25.10 | coreyfarrell | funny thing though the second run was on slave4 but ran fine. but that could just mean that it randomly ran in the part of ram that is not failing. |
| 12:25.51 | gtjoseph | the only things in dmesg I see are... |
| 12:25.51 | gtjoseph | [Jun26 14:08] traps: asterisk[28556] general protection ip:7f6ac864f7f9 sp:7f6a4cd68630 error:0 in libasteriskpj.so.2[7f6ac851b000+186000] |
| 12:25.52 | gtjoseph | [Jun26 14:34] traps: asterisk[48790] trap stack segment ip:7fec6fdf3e0f sp:7fec688db790 error:0 in res_pjsip_pubsub.so[7fec6fde8000+17000] |
| 12:26.52 | gtjoseph | i'm going to reboot it though just to be safe |
| 12:27.16 | coreyfarrell | it was res_pjsip_pubsub.so that got the signal 7 |
| 12:27.51 | gtjoseph | does the date/time match? |
| 12:29.05 | coreyfarrell | yes |
| 12:29.18 | gtjoseph | hmmm |
| 12:29.52 | gtjoseph | kick it off again and lets see what happens |
| 12:31.29 | gtjoseph | well, slave4 got pjsip again |
| 12:32.44 | coreyfarrell | is each slave a physical machine? |
| 12:32.50 | gtjoseph | no VM |
| 13:50.46 | *** join/#asterisk-dev jkroon (~jkroon@41.161.87.19) |
| 13:51.48 | coreyfarrell | the testsuite python3 changes aren't going into 14 unless the matcher.py changes get cherry-picked first. |
| 14:27.55 | *** join/#asterisk-dev kharwell (kharwell@nat/digium/x-cmtmpqfjbtengejt) |
| 14:27.55 | *** mode/#asterisk-dev [+o kharwell] by ChanServ |
| 14:33.33 | *** join/#asterisk-dev bford (uid283514@gateway/web/irccloud.com/x-imcfkttzxjdyfhrl) |
| 14:33.33 | *** mode/#asterisk-dev [+o bford] by ChanServ |
| 14:47.33 | *** join/#asterisk-dev snuff-work (~snuff-wor@210.9.148.102) |
| 14:47.33 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 14:53.47 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-uhvfvoypjbivvtlz) |
| 14:53.47 | *** mode/#asterisk-dev [+o rmudgett] by ChanServ |
| 16:01.10 | *** join/#asterisk-dev CELYA_1 (~Thunderbi@2a01:e0a:d:1111:5481:eb79:921d:e1b1) |
| 19:08.53 | *** join/#asterisk-dev malcolmd (malcolmd@pdpc/sponsor/digium/malcolmd) |
| 19:08.53 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
| 19:11.57 | *** join/#asterisk-dev cresl1n (uid299068@asterisk/libpri-and-libss7-expert/Cresl1n) |
| 19:11.57 | *** mode/#asterisk-dev [+o cresl1n] by ChanServ |
| 19:12.56 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.164) |
| 19:23.46 | coreyfarrell | I think the python3 testsuite review is ready, asterisk-gate was successful twice (8854 against asterisk master). I'd appreciate reviews. |
| 20:00.52 | cresl1n | yay! |
| 20:35.49 | *** join/#asterisk-dev tzafrir (~quassel@2001:4b98:dc0:47:216:3eff:feb8:126a) |
| 20:35.49 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 20:36.12 | seanbright | cresl1n: you game at all? |
| 20:36.37 | seanbright | if so, i recommend shenzhen i/o |
| 20:36.43 | seanbright | it's like work, but funner |
| 20:54.05 | cresl1n | Nice |
| 20:54.25 | cresl1n | Haven't gamed in a while though |
| 20:54.37 | cresl1n | Might still have to check it out |
| 22:02.53 | *** join/#asterisk-dev joshelson (~joshelson@67.214.249.12) |
| 22:14.28 | *** part/#asterisk-dev kharwell (kharwell@nat/digium/x-cmtmpqfjbtengejt) |