summaryrefslogtreecommitdiff
path: root/spec
diff options
context:
space:
mode:
authorFabio Pitino <fpitino@gitlab.com>2019-05-07 07:52:53 +0100
committerFabio Pitino <fpitino@gitlab.com>2019-05-07 08:07:16 +0100
commitc75b8ad4dadfa8f9676e0339e06408af3281f512 (patch)
tree34b287af35682e19db655af9b98eab1b56f18b2c /spec
parent673ea5d2ac50e17a1839d0db83641e6851422f88 (diff)
downloadgitlab-ce-c75b8ad4dadfa8f9676e0339e06408af3281f512.tar.gz
Remove workaround by upgrading Fugit gem
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/58241 * Upgrade Fugit gem to 1.2.1 which recognizes cron expressions for invalid days * Reverted previously implemented workaround * Leave test case which previously exposed the bug
Diffstat (limited to 'spec')
-rw-r--r--spec/lib/gitlab/ci/cron_parser_spec.rb7
1 files changed, 0 insertions, 7 deletions
diff --git a/spec/lib/gitlab/ci/cron_parser_spec.rb b/spec/lib/gitlab/ci/cron_parser_spec.rb
index a228334d53e..491e3fba9d9 100644
--- a/spec/lib/gitlab/ci/cron_parser_spec.rb
+++ b/spec/lib/gitlab/ci/cron_parser_spec.rb
@@ -181,13 +181,6 @@ describe Gitlab::Ci::CronParser do
it { expect(subject).to be_nil }
end
-
- context 'when cron is scheduled to a non existent day' do
- let(:cron) { '0 12 31 2 *' }
- let(:cron_timezone) { 'UTC' }
-
- it { expect(subject).to be_nil }
- end
end
describe '#cron_valid?' do