<sb0>
oooh cool another travis python import clusterfuck. i love those.
ylamarre1 has joined #m-labs
<sb0>
cr1901_modern, i assume the tests work on your machine, right?
<cr1901_modern>
I've never run them tbh lol
<sb0>
can you try?
ylamarre has quit [Ping timeout: 240 seconds]
ylamarre1 is now known as ylamarre
<sb0>
latest new branch should pass all tests
<cr1901_modern>
Yea sure. Is this b/c travis is being a fuckup?
<sb0>
yes
<cr1901_modern>
is there a global script I can run, or just run them individually?
<sb0>
cd migen/test && python3 -m unittest
<cr1901_modern>
ahhh, right
<cr1901_modern>
I don't have verilator installed, but 41 tests passed before that
<cr1901_modern>
I'll compile/install that now
ylamarre1 has joined #m-labs
ylamarre has quit [Ping timeout: 240 seconds]
<cr1901_modern>
(this takes a bit of time on Windows b/c POSIX emulation in general is crap)
ylamarre1 has quit [Ping timeout: 272 seconds]
ylamarre has joined #m-labs
<cr1901_modern>
sb0: While I'm waiting for Verilator to compile... is the new VPI going to essentially be a top level module that has an instance of every single external module that was instantiated by Migen, and the relevant set of signals as regs?
<cr1901_modern>
Okay, verilator is installed. The verilator test passes when I run it manually (0 return code), but Python claims non-zero return code when I run python3 -m unittest
<cr1901_modern>
Running that command manually, and then "echo $?" results in 0 printed to stdout
<sb0>
can you get the verilator log somehow?
<cr1901_modern>
I'm not sure... I don't see anything suggesting that verilator has a log
<cr1901_modern>
wait nevermind
ylamarre has quit [Remote host closed the connection]
ylamarre has joined #m-labs
<cr1901_modern>
I retract the former statement; that was verilator complaining about bad command line parameters (I've never used Verilator)
nicksydney has quit [Remote host closed the connection]
ylamarre has quit [Remote host closed the connection]
ylamarre has joined #m-labs
<cr1901_modern>
sb0: I'm not sure what information you want: running verilator --cc produces a number of C++ objects, and compiling them with the resulting Makefile outputs an archive file
<cr1901_modern>
haven't figured out how to get a binary yet
<sb0>
well why that test fails
<GitHub17>
[migen] sbourdeauducq pushed 2 new commits to new: http://git.io/vnnEE
<GitHub17>
migen/new 1767eef Sebastien Bourdeauducq: fhdl/visit: support Constant
<GitHub17>
migen/new 74b0cfc Sebastien Bourdeauducq: doc: remove outdated or moved parts, cleanup
<sb0>
anyhow, that's not what travis is whining about
travis-ci has joined #m-labs
<travis-ci>
m-labs/migen#98 (new - 74b0cfc : Sebastien Bourdeauducq): The build is still failing.
<cr1901_modern>
sb0: I think personally think the verilator test should be skipped on Windows, b/c it depends on a bash shell existing, which is no guarantee for a Windows user >>
<cr1901_modern>
However, changing line 43 of test_syntax.py to the following fixes the test: