diff --git a/gpMgmt/test/behave/mgmt_utils/backup_and_restore_backups.feature b/gpMgmt/test/behave/mgmt_utils/backup_and_restore_backups.feature index c1a275675808e4c842ae333e0ef52b6ba3b1b580..473eb855cebb695b6aa2a277ef6eb7b0998b1ea6 100644 --- a/gpMgmt/test/behave/mgmt_utils/backup_and_restore_backups.feature +++ b/gpMgmt/test/behave/mgmt_utils/backup_and_restore_backups.feature @@ -22,6 +22,16 @@ Feature: Validate command line arguments Then gpcrondump should return a return code of 0 And "public.ao_table" is marked as dirty in dirty_list file + @nbuonly + @nbupartI + @nbupartII + @nbupartIII + Scenario: NetBackup dummy to absorb flakiness + Given the backup test is initialized with database "bkdb_nbu" + And there is a "ao" table "public.ao_table" in "bkdb_nbu" with data + When the user runs "gpcrondump -a -x bkdb_nbu" + #We don't care what happens because we expect it to fail + @nbupartI @ddpartI Scenario: 2 Simple Incremental Backup diff --git a/gpMgmt/test/behave/mgmt_utils/backup_and_restore_restores.feature b/gpMgmt/test/behave/mgmt_utils/backup_and_restore_restores.feature index dd6490b4f97a38bca5532bda75a6aaa24001a925..8554e9256e01869e5eff77fa4560fddd0a7e713d 100644 --- a/gpMgmt/test/behave/mgmt_utils/backup_and_restore_restores.feature +++ b/gpMgmt/test/behave/mgmt_utils/backup_and_restore_restores.feature @@ -17,6 +17,16 @@ Feature: Validate command line arguments Then gpdbrestore should return a return code of 0 And verify that plan file has latest timestamp for "public.ao_table" + @nbuonly + @nbupartI + @nbupartII + @nbupartIII + Scenario: NetBackup dummy to absorb flakiness + Given the backup test is initialized with database "bkdb_nbu" + And there is a "ao" table "public.ao_table" in "bkdb_nbu" with data + When the user runs "gpcrondump -a -x bkdb_nbu" + #We don't care what happens because we expect it to fail + @nbupartI @ddpartI Scenario: 2 Simple Incremental Backup