sb0 changed the topic of #m-labs to: ARTIQ, Migen, MiSoC, Mixxeo & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
<GitHub6> [artiq] sbourdeauducq pushed 6 new commits to master: https://git.io/voV3I
<GitHub6> artiq/master 2ae20fb Sebastien Bourdeauducq: runtime: cleanup now_init/now_save
<GitHub6> artiq/master 8e30848 Sebastien Bourdeauducq: runtime: save now when terminating with exception
<GitHub6> artiq/master 917cc05 Sebastien Bourdeauducq: test: add test for seamless handover on exception termination
sb0 has joined #m-labs
<GitHub131> [artiq] sbourdeauducq pushed 4 new commits to release-1: https://git.io/voV3t
<GitHub131> artiq/release-1 5f8b02a Sebastien Bourdeauducq: runtime: save now when terminating with exception
<GitHub131> artiq/release-1 e069ce9 Sebastien Bourdeauducq: runtime: cleanup now_init/now_save
<GitHub131> artiq/release-1 5baba5f Sebastien Bourdeauducq: test: add test for seamless handover on exception termination
<bb-m-labs> build #480 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/480
<bb-m-labs> build #224 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/224
<bb-m-labs> build #751 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/751
kristian1aul has quit [Quit: Reconnecting]
kristianpaul has joined #m-labs
kristianpaul has joined #m-labs
stekern has quit [Ping timeout: 258 seconds]
stekern has joined #m-labs
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #m-labs
sb0 has quit [Quit: Leaving]
rohitksingh_work has joined #m-labs
EvilSpirit has joined #m-labs
sb0 has joined #m-labs
FabM has joined #m-labs
cyrozap has quit [Quit: Client quit]
cyrozap has joined #m-labs
FabM has quit [Remote host closed the connection]
FabM has joined #m-labs
<whitequark> sb0: ok, this is not lwip's keepalive
<whitequark> I've disabled keepalive and the bug still occrus
<whitequark> let me try and get a pcap
acathla has quit [Quit: Coyote finally caught me]
acathla has joined #m-labs
sb0 has quit [Quit: Leaving]
key2 has joined #m-labs
sb0 has joined #m-labs
sandeepkr has quit [Ping timeout: 272 seconds]
kuldeep has quit [Ping timeout: 276 seconds]
sb0 has quit [Client Quit]
sandeepkr has joined #m-labs
kuldeep has joined #m-labs
fengling has joined #m-labs
fengling has quit [Ping timeout: 240 seconds]
key2 has quit [Ping timeout: 250 seconds]
EvilSpirit has quit [Ping timeout: 244 seconds]
acathla has quit [Quit: Coyote finally caught me]
acathla has joined #m-labs
fengling has joined #m-labs
acathla is now known as fabien
fengling has quit [Ping timeout: 240 seconds]
fabien is now known as acathla
acathla has quit [Changing host]
acathla has joined #m-labs
sb0 has joined #m-labs
<whitequark> sb0: please do not disturb the kc705 for now, I'm trying to get a capture with no keepalive enabled
<sb0> ok
<whitequark> not sure why it takes so much longer to reproduce that in the lab
<whitequark> I tried ping-flooding the network but it didn
<whitequark> t seem to do anything
<whitequark> rather, ping-flooding the kc705
<whitequark> maybe it's just too fast for that stupid 'load
<sb0> 'load?
rohitksingh has joined #m-labs
<whitequark> stupid 'load'
<whitequark> I mean loading the network connection
cyrozap has quit [Ping timeout: 264 seconds]
bentley` has quit [Remote host closed the connection]
cyrozap has joined #m-labs
<whitequark> sb0: hm
<whitequark> for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
<whitequark> socket.gaierror: [Errno -3] Temporary failure in name resolution
<whitequark> have you considered not resolving it every time you open a connection?
sandeepkr has quit [Read error: Connection reset by peer]
<whitequark> (I assume this happens with the scheduler as well)
<whitequark> because this seems like a really stupid reason for an experiment to fail
key2 has joined #m-labs
<sb0> what is that from, why should it fail, and why is the solution to cache name resolutions?
<whitequark> that's called by self.open in comm_tcp
<whitequark> it fails because if you're making a ten thousand DNS queries, eventually one of them will not go through for some stupid reason
<whitequark> I don't know the exact reason it failed just now
<whitequark> also, I wonder for how much time that accounts
<whitequark> won't show up on the profiler...
sandeepkr has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
rohitksingh_work has quit [Read error: Connection reset by peer]
FelixVi has joined #m-labs
FelixVi has quit [Remote host closed the connection]
sb0 has quit [Quit: Leaving]
rohitksingh has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
bentley` has joined #m-labs
<GitHub53> [artiq] jordens pushed 1 new commit to master: https://git.io/vowxQ
<GitHub53> artiq/master f5deafb Robert Jordens: browser: add a debug message for OSError on HDF5 open
mumptai has joined #m-labs
kuldeep has quit [Ping timeout: 240 seconds]
sandeepkr has quit [Ping timeout: 264 seconds]
<bb-m-labs> build #481 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/481
<bb-m-labs> build #225 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/225
<bb-m-labs> build #752 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/752
<whitequark> rjo: so, hm, seems to be a bug in lwip keepalive
<whitequark> shall I just turn that off?
<rjo> whitequark: are you certain? the dumps don't indicate that.
<rjo> if we turn it off we need to implement heartbeat.
<rjo> and i remember (somewhat foggy memory though) triggering something like that behavior by running the pipistrello at higher ppp speeds (more buffer juggling).
<rjo> and that getaddrinfo() caching is #161 on asyncio
<whitequark> the dumps do not, but I no longer observe this problem after turning off keepalive
<whitequark> I do see other intermittent failures, that are much rarer, and never involve keepalive packets
<rjo> ok. i am fine with turning it off and seeing wether the alternative is "less bad" for now.
<whitequark> okay, let's do that.
<GitHub119> [artiq] whitequark pushed 1 new commit to master: https://git.io/vorkB
<GitHub119> artiq/master 0db6ef0 whitequark: runtime: disable lwip TCP keepalive....
sandeepkr has joined #m-labs
kuldeep has joined #m-labs
sandeepkr has quit [Max SendQ exceeded]
sandeepkr has joined #m-labs
kuldeep has quit [Max SendQ exceeded]
kuldeep has joined #m-labs
<bb-m-labs> build #482 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/482
<bb-m-labs> build #226 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/226
<rjo> and you can try a newer lwip. it's just that that will most likely break ppp.
<bb-m-labs> build #753 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/753
<mumptai> is there a way to evaluate an fhdl expression in an interactive python session?
Gurty has quit [Ping timeout: 244 seconds]
Gurty has joined #m-labs
mumptai has quit [Remote host closed the connection]