[libre-riscv-dev] [Bug 316] bperm TODO

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Wed May 20 02:04:12 BST 2020


--- Comment #62 from Jacob Lifshay <programmerjake at gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #58)
> (In reply to Jacob Lifshay from comment #55)
> > (In reply to Cole Poirier from comment #54)
> > > Ah yes, appreciated, I will grep first in the future. For clarification, the
> > > way to run the tests is by cd'ing to the soc/decoder directory then running
> > > 'python3 test/{test_file.py}' for each of the files in the tests directory?
> because i run ctags in one directory (usually the top level or close to it)
> and stay there.
> i generally run e.g. python3 fu/alu/test/test_pipe_caller.py or something.
> constantly doing "cd" i find very annoying.
> to find previously-run commands is a matter of running "history" followed by
> !inserthistorynumber
> this saves typing the command out repeatedly - also very annoying.
> lots of annoyingness... :)

At the bash prompt, type Ctrl-R then some portion of the previous command, it's
the readline shortcut for search through history from most to least recent. You
can also keep pressing Ctrl-R to go to the previous occurrence.

> however *after* that fast-iterative cycle (explicitly running only the
> relevant
> test), it is kinda important to run more (nosetests3, python3 setup.py test)
> just
> to make absolutely sure you didn't break anything unrelated.  don't tell
> no-one
> i tend not to do that very often... :)

should do it more often, since otherwise stuff never gets fixed. Part of why I
went to lots of effort to get CI setup and working (which still needs someone
to finish setting up the CI mailing list and the sendmail script for use with

You are receiving this mail because:
You are on the CC list for the bug.

More information about the libre-riscv-dev mailing list