[freetds] Fwd: [Still Failing] FreeTDS/freetds#61 (master - 03b8a23)
freddy77 at gmail.com
Mon May 19 02:39:58 EDT 2014
It's an utility I wrote similar to annotate one. You can find at
It help separating the streams (output/error).
2014-05-12 16:16 GMT+01:00 Marc Abramowitz <msabramo at gmail.com>:
> Where does the "classifier" program come from? A lot of the scripts rely on
> On Sat, Mar 1, 2014 at 2:00 PM, Frediano Ziglio <freddy77 at gmail.com> wrote:
>> 2014-03-01 21:04 GMT+00:00 Marc Abramowitz <msabramo at gmail.com>:
>> > On Sat, Mar 1, 2014 at 11:19 AM, Frediano Ziglio <freddy77 at gmail.com>
>> >> 2014-03-01 18:27 GMT+00:00 Marc Abramowitz <msabramo at gmail.com>:
>> >> > Not sure if folks are seeing the test failures or not.
>> >> >
>> >> > Should I set the Travis CI email to this list?
>> >> >
>> >> No. Perhaps would be better to have another mailing list so people can
>> >> decide to not subscribe if not want to receive these kind of mails.
>> > OK. If you create the mailing list and let me know the address, I'll
>> > it. Or you can just commit it in .travis.yml.
>> I actually don't know the account for mail stuff, James will create it.
>> >> Honestly however the report does not help that much to fix the
>> >> problem. Considering
>> >> https://travis-ci.org/FreeTDS/freetds/builds/18948700 well... why does
>> >> t0004 test fail ? Where is the output ? Where is the dump ? Anyway, I
>> >> fixed the problem... seems that some extra checks hidden more errors
>> >> that what they should reveal!
>> > Agreed. I don't see anything too helpful there for fixing the problem.
>> > you get more helpful info when you run the tests locally? Because if you
>> > do, then I can look into why Travis isn't showing anything helpful. If
>> > running the tests locally doesn't pinpoint the problem, then that is
>> > probably more of an issue with the tests.
>> output will look something like
>> http://freetds.sourceforge.net/up/out92/test/dblib_t0016.2.html (red
>> is the error stream the fixed black characters is the normal stdout
>> The script I use (misc/full-test.sh) produce also output with
>> valgrind, see
>> for an example.
>> misc/test-auto.sh script configure, build and run tests using
>> misc/full-test.sh as a wrapper for every test (defining
>> TESTS_ENVIRONMENT). The output mainly get a single file you can split
>> in multiple ones. misc/online.pl then split this output to produce
>> something like http://freetds.sourceforge.net/up/out92/test/
>> FreeTDS mailing list
>> FreeTDS at lists.ibiblio.org
> FreeTDS mailing list
> FreeTDS at lists.ibiblio.org
More information about the FreeTDS