drizzle-discuss team mailing list archive
Mailing list archive
Re: New PBXT Drizzle-specific storage engine...
Can we turn on the subunit output and the junit filter so we can track
test failures in hudson too?
set -o pipefail
make -j16 distcheck TEST_RUN_EXTRA_OPTIONS='--subunit' | sed
's/^\([[:space:]]*test \)/;\1/' | subunit2junitxml -o
chmod -R +w . && exit $status
Is the snippet that turns it on on other jobs. Perhaps we need to
install subunit on the build hosts?
Lee Bieber wrote:
> I've created these two jobs in Hudson
> (build fails due to warnings)
> (only 3 test failures!)
> building off of the lp:~drizzle-pbxt/drizzle/drizzle-pbxt-2/ branch for
> I've added Paul and Vladimir to failure notifications, let me know if
> anyone else should be added or wants to be added.
> Thanks, Lee
> Jay Pipes wrote:
>> Hi Paul!
>> I've pushed a new branch up to Launchpad:
>> This branch removes the MySQL-specific plugin, handler, handlerton
>> stuff in favor of the Drizzle StorageEngine and Cursors. All #ifdefs
>> have been removed which makes reading the source files a heck of a lot
>> easier :)
>> I'll continue working on the branch. I've noticed (as have you I'm
>> sure) that most of the test failures are because EXPLAIN is returning
>> slightly different results (because the default result files are
>> specific to InnoDB or MyISAM) or that some InnoDB-specific warnings
>> don't appear in the results file. I'll work with Vlad to clear these up.
>> Mailing list: https://launchpad.net/~drizzle-discuss
>> Post to : drizzle-discuss@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~drizzle-discuss
>> More help : https://help.launchpad.net/ListHelp
> Mailing list: https://launchpad.net/~drizzle-discuss
> Post to : drizzle-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~drizzle-discuss
> More help : https://help.launchpad.net/ListHelp