search for: test_modules

This is request made from the client: new Ajax.Updater("sip_tab_content", "/rails/test_modules/show/"+$F"boardid"), {method :''get'', onFailure:displaySIPTabFailure, onComplete:displaySIPTabFailure }); This is controller from the ROR controller acting as server: class TestModul...

First, yes, I have read the piece on chroot.... Trying to get an AIX (5.3) to run rsync 2.6.2 as a daemon I have tried every possibly usage to stop chroot, used no and false, as on the web it has showed up as either. Also dropped flag --numeric-ids when running.... Here is my test config--- # Simple test config file log file = /tmp/rsync.log [test] use chroot = no path = /tmp/rsync_test/

On Sun, 2005-04-10 at 19:47 -0500, Chris Lattner wrote: > On Mon, 11 Apr 2005, Paul wrote: > > I'm trying to pass an array pointer to my run-time generated module, and > > after a long time of searching for the answer, the only thing I got was > > a headache. Basically I have a few arrays (few megabytes which will > > sometimes be accessed as 8 / 16 / 32 / 64 bit

...ood lit will run and collect all metrics, but there is no opportunity to make any settings for choosing what metrics I would like to collect. Test reports files allow to choose what report I would like. One time I can use one, second time I can use another. I can do this with cmake only by changing test_modules in file. So I can’t group some metrics and give them some name. Am I right? Thanks, Elena. From: Matthias Braun [mailto:matze at braunis.de] Sent: Friday, May 20, 2016 8:03 PM To: Elena Lepilkina <Elena.Lepilkina at synopsys.com> Cc: Daniel Dunbar <daniel at zuster.org>; llvm-dev &l...

I'm new to rsync and trying to configure it to run through either the daemon or rsh (ssh is not avalilable). Doing an 'rlogin production' results in a password prompt - which I want rid of, as we're basically going to have a robot user running a cron job that utilises rsync. I'm at a loss as to why I can't configure rlogin to user hosts.equiv or similar - any help on this

...ood lit will run and collect all metrics, but there is no opportunity to make any settings for choosing what metrics I would like to collect. Test reports files allow to choose what report I would like. One time I can use one, second time I can use another. I can do this with cmake only by changing test_modules in file. > So I can’t group some metrics and give them some name. The test_modules flag does indeed allow some customisation in what metrics are collected, my main usage for this has been do setup things to just collect codesize but not run the benchmark, a setup in which benchmarks are cross co...

On Mon, 11 Apr 2005, dummy1 at boxpl.com wrote: >> There are many possible ways to do this, can you be a bit more specific >> about what you're trying to do? > Here is a basic example: Ah, ok, I see what you're trying to do. Below is some *pseudo* code for the basic idea: > ============================================ > unsigned int buff[4096]; > > int main

...ood lit will run and collect all metrics, but there is no opportunity to make any settings for choosing what metrics I would like to collect. Test reports files allow to choose what report I would like. One time I can use one, second time I can use another. I can do this with cmake only by changing test_modules in file. So I can’t group some metrics and give them some name. The test_modules flag does indeed allow some customisation in what metrics are collected, my main usage for this has been do setup things to just collect codesize but not run the benchmark, a setup in which benchmarks are cross compile...

...the user has the testsuite in whatever configuration he wanted. I started a patch for this here: http://reviews.llvm.org/D19949 <http://reviews.llvm.org/D19949> but I need to find some time to rework it. If you run the test-suite manually: Just remove the "run" module in the config.test_modules list in the lit.site.cfg of your builddir. The benchmarks will no longer be executed but the codesize, hash and compiletime modules will still collect those metrics. We can add a cmake configuration parameter for this if this is a generally useful configuration. > 3. Before each group of...

...collect all metrics, but there is no > opportunity to make any settings for choosing what metrics I would like to > collect. Test reports files allow to choose what report I would like. One > time I can use one, second time I can use another. I can do this with cmake > only by changing test_modules in file. > > So I can’t group some metrics and give them some name. > > > > Am I right? > > > > Thanks, > > Elena. > > > > > > *From:* Matthias Braun [mailto:matze at braunis.de] > *Sent:* Friday, May 20, 2016 8:03 PM > *To:* Elena Lepilki...

On Mon, 11 Apr 2005, Paul wrote: > I'm trying to pass an array pointer to my run-time generated module, and > after a long time of searching for the answer, the only thing I got was > a headache. Basically I have a few arrays (few megabytes which will > sometimes be accessed as 8 / 16 / 32 / 64 bit binary / fp values), that > will be modified by both the generated module, and my

I'm trying to pass an array pointer to my run-time generated module, and after a long time of searching for the answer, the only thing I got was a headache. Basically I have a few arrays (few megabytes which will sometimes be accessed as 8 / 16 / 32 / 64 bit binary / fp values), that will be modified by both the generated module, and my main c program, so I would like to put those into global

> On May 12, 2016, at 11:21 PM, Elena Lepilkina via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all, > > As we understood great changes will be done in LNT, so we are waiting to new LNT version and stopped our work in LNT. > > One more question about using test-suite separately with cmake. Cmake can only build all tests and generate lit tests. After that we

Hi all, As we understood great changes will be done in LNT, so we are waiting to new LNT version and stopped our work in LNT. One more question about using test-suite separately with cmake. Cmake can only build all tests and generate lit tests. After that we can run LIT and get report which is not equal with report (simple) got with make. Cmake test-suite version has no features to run custom