On 5/29/13 19:36 , andy pugh wrote: > In a fit of enthusiasm I set up a regression test for mux_generic. > (which is otherwise all ready to push). > > The test just sets up one of each type of mux (16 variants), sets the > inputs, does a "show pin", sets the selector bit, and "show pin" > again. > > All well and good, and actually did spot a mistake I made when tidying up.
That's great! > Then I tried it in --enable-simulator mode, and it fails. It fails > because the "owner" column in halcmd show pin is different. That's not great... > Is there a way round this? Sampler seems a bit inconvenient for this test. Take a look at the test for the multiclick component, it uses halsampler and halstreamer. It sets up a small HAL network with streamer connected to the component's input pins and sampler connected to the output pins, then streams in test patterns and records the outputs. Then when it's finished it compares the output to the expected. Pretty straight-forward to set up, and very easy and robust to use/tweak during development. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
