- 13 1月, 2018 40 次提交
-
-
由 Heikki Linnakangas 提交于
I'm not sure if we're going to keep these tests in the end, but might as well fix this for now.
-
由 Heikki Linnakangas 提交于
-
由 Ashwin Agrawal 提交于
-
由 Ashwin Agrawal 提交于
-
由 Ashwin Agrawal 提交于
-
由 Ashwin Agrawal 提交于
-
由 Heikki Linnakangas 提交于
There are more in other tests, but I suspect those other tests are obsolete in whole, so I'm just patching this one that caused a failure in the concourse pipeline.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Jimmy Yih 提交于
The walreceiver test establishes a walrep connection to the master's walsender. With the recent change to start standby master by default on gpdemo cluster, the mock walreceiver will be unable to create a connection to the walsender since max_wal_senders is hardcoded to 1. Moving this to run only on mirrorless cluster makes more sense since the assumption is to have an available walrep connection.
-
由 Jimmy Yih 提交于
This reverts commit 3214d80fabf7c208e40b2ec4f7ec69c97a9e7dd6.
-
由 Jimmy Yih 提交于
This reverts commit f38f024d7d314ae8ac100d862307a228b212c70e.
-
由 C.J. Jameson 提交于
- use the new fact that datadirs are in the gp_segment_configuration - fix a few things with the gpperfmon behave tests (mostly for macOS) --> the change to mgmt_utils.py is to do the config file manipulation natively in python --> the change to the gp_bash_functions.sh is to use ASCII ' characters so that python string comparison is happier Author: C.J. Jameson <cjameson@pivotal.io>
-
由 Heikki Linnakangas 提交于
It just doesn't mean "filespace" anymore, just plain "datadir".
-
由 Heikki Linnakangas 提交于
Since persistent tables were removed, these were not used for anything.
-
由 Heikki Linnakangas 提交于
Plenty remains, but this is a start.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Ashwin Agrawal 提交于
These tests are very tightly coupled with filerep and persistent tables implemenation. We do need to have tests in replacement but these would be coded not in TINC and mostly much less scenarios as in general walreplication mirrors active for full ICW validates most of crashrecovery logic. What's missing mostly is real crash scenarios in middle of active workload like creating/dropping objects and all.
-
由 Heikki Linnakangas 提交于
After removing -s option from gpsegstart, this unit test started failing with curious error: Stderr: Usage: gpunit [--help] [options] gpunit: error: no such option: -s ====================================================================== ERROR: Test Suite Name|programs.test.unit.test_cluster_clsrecoversegment|Test Case Name|test_output_segments_in_change_tracking_disabled_should_print_failed_segments|Test Details| ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/heikki/git-sandbox-gpdb/master/gpMgmt/bin/gppylib/programs/test/unit/test_cluster_clsrecoversegment.py", line 16, in setUp (options, _) = raw_options.parse_args() File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args self.error(str(err)) File "/usr/lib/python2.7/optparse.py", line 1584, in error self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg)) File "/usr/lib/python2.7/optparse.py", line 1574, in exit sys.exit(status) SystemExit: 2 It turns out that the unit test was passing the command-line options from the gpunit invocation, to the options parser of the gpsegstart command. It was accidental that it ever worked, because gpsegstart also happened to have a -s option, like gpunit did. Now that the option was removed, the gpsegstart options parser started to fail. To fix, explicitly pass "no command-line arguments" to the gpsegstart options parser, so that it doesn't pick up the args from the gpunit invocation.
-
由 Heikki Linnakangas 提交于
Remove test code for check_persistent_tables function, which was removed earlier. Fix a few more initFromString() lines.
-
由 Ashwin Agrawal 提交于
Many times the `commit_blocking` test fails, its not clear if the problem happened during the test, or cluster was not in right state before we started. Hence adding expected state for the test at start which would help to easily know if this test failed or is just side-effect for previous test failure.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
I removed the filespaces arg earlier, but failed to update the format string accordingly.
-
由 Ashwin Agrawal 提交于
-
由 Ashwin Agrawal 提交于
- Special lock functions for RelationExtension - Special function ReadBuffer_Resync() - States related to CT and RESYNC - Xlog during PageInit() for vacuum lazy (upstream doesn't have it so removed it)
-
由 Ashwin Agrawal 提交于
This reverts commit 1a27788edfd2163cbfcb1dc30c5eb870eac77181. As should be passing now since FTS using uninitialized variable `fts_status` causing the failure has been fixed now.
-
由 Ashwin Agrawal 提交于
On QD start, FTS process can take sometime to start and initialize the `ftsProbeInfo->fts_status`. So, check against the same only if its initialized and avoid incorrectly reporting segment as down and failing queries.
-
由 Ashwin Agrawal 提交于
-
由 Heikki Linnakangas 提交于
Leftovers from removal of filespaces and replication ports. Caught by unit tests.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
On second thoughts, let's keep the QD mirror running. I'm not sure why we disabled it originally, but now that I went through the trouble of fixing subsequent tests to pass with a QD mirror, let's keep it enabled.
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
The setup script for the walrep tests disables the standby for the QD node. That used to not work, and therefore the mirror was still running, but now that I fixed "gpinitstandby -ra", it is disabled again. I'm not convinced that we should disable the mirror, and leave it disabled, in the walrep tests. But that's the way it was.
-
由 Heikki Linnakangas 提交于
-