Skip to content

Instantly share code, notes, and snippets.

@singingwolfboy
Created June 4, 2015 14:44
Show Gist options
  • Save singingwolfboy/031842be4469129440c0 to your computer and use it in GitHub Desktop.
Save singingwolfboy/031842be4469129440c0 to your computer and use it in GitHub Desktop.
14:37:38 Setting up for cms acceptance using draft
14:37:38 ---> pavelib.assets.update_assets
14:37:38 python manage.py cms --settings=acceptance preprocess_assets
14:37:41 xmodule_assets common/static/xmodule
14:37:43 ---> pavelib.assets.compile_coffeescript
14:37:43 node_modules/.bin/coffee --compile `find /home/jenkins/workspace/edx-platform-test-subset/lms /home/jenkins/workspace/edx-platform-test-subset/cms /home/jenkins/workspace/edx-platform-test-subset/common -type f -name "*.coffee"`
14:37:49 ---> pavelib.assets.compile_sass
14:37:49 sass --style compressed --cache-location /tmp/sass-cache --load-path ./common/static/sass --update -E utf-8 */static
14:37:58 write cms/static/sass/studio-main-rtl.css
14:38:05 write cms/static/sass/studio-main.css
14:38:06 DEPRECATION WARNING on line 46 of static/vendor/breakpoint/_breakpoint.scss:
14:38:06 Assigning to global variable "$breakpoint" by default is deprecated.
14:38:06 In future versions of Sass, this will create a new local variable.
14:38:06 If you want to assign to the global variable, use "$breakpoint: breakpoint($query, false) !global" instead.
14:38:06 Note that this will be incompatible with Sass 3.2.
14:38:06
14:38:06 WARNING: The box-sizing mixin is deprecated and will be removed in the next major version release. This property can now be used un-prefixed.
14:38:06 on line 410 of static/vendor/bourbon/_bourbon-deprecated-upcoming.scss, in `box-sizing'
14:38:06 from line 12 of static/vendor/susy/susy/output/support/_box-sizing.scss, in `susy-box-sizing'
14:38:06 from line 40 of static/vendor/susy/susy/output/support/_support.scss, in `susy-support'
14:38:06 from line 12 of static/vendor/susy/susy/output/shared/_output.scss, in `output'
14:38:06 from line 28 of static/vendor/susy/susy/language/susy/_span.scss, in `span'
14:38:06 from line 110 of lms/static/certificates/sass/_layouts.scss, in `@content'
14:38:06 from line 24 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `@content'
14:38:06 from line 36 of static/vendor/susy/susy/language/susy/_grids.scss, in `with-layout'
14:38:06 from line 23 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `@content'
14:38:06 from line 75 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `@content'
14:38:06 from line 66 of static/vendor/breakpoint/_breakpoint.scss, in `breakpoint'
14:38:06 from line 74 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `susy-media-router'
14:38:06 from line 21 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `susy-breakpoint'
14:38:06 from line 109 of lms/static/certificates/sass/_layouts.scss
14:38:06 from line 38 of lms/static/certificates/sass/_build.scss
14:38:06 from line 24 of lms/static/certificates/sass/main-ltr.scss
14:38:06
14:38:06 WARNING: The box-sizing mixin is deprecated and will be removed in the next major version release. This property can now be used un-prefixed.
14:38:06 on line 410 of static/vendor/bourbon/_bourbon-deprecated-upcoming.scss, in `box-sizing'
14:38:06 from line 12 of static/vendor/susy/susy/output/support/_box-sizing.scss, in `susy-box-sizing'
14:38:06 from line 40 of static/vendor/susy/susy/output/support/_support.scss, in `susy-support'
14:38:06 from line 12 of static/vendor/susy/susy/output/shared/_output.scss, in `output'
14:38:06 from line 28 of static/vendor/susy/susy/language/susy/_span.scss, in `span'
14:38:06 from line 118 of lms/static/certificates/sass/_layouts.scss, in `@content'
14:38:06 from line 24 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `@content'
14:38:06 from line 36 of static/vendor/susy/susy/language/susy/_grids.scss, in `with-layout'
14:38:06 from line 23 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `@content'
14:38:06 from line 75 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `@content'
14:38:06 from line 66 of static/vendor/breakpoint/_breakpoint.scss, in `breakpoint'
14:38:06 from line 74 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `susy-media-router'
14:38:06 from line 21 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `susy-breakpoint'
14:38:06 from line 117 of lms/static/certificates/sass/_layouts.scss
14:38:06 from line 38 of lms/static/certificates/sass/_build.scss
14:38:06 from line 24 of lms/static/certificates/sass/main-ltr.scss
14:38:06
14:38:07 write lms/static/certificates/sass/main-ltr.css
14:38:08 DEPRECATION WARNING on line 46 of static/vendor/breakpoint/_breakpoint.scss:
14:38:08 Assigning to global variable "$breakpoint" by default is deprecated.
14:38:08 In future versions of Sass, this will create a new local variable.
14:38:08 If you want to assign to the global variable, use "$breakpoint: breakpoint($query, false) !global" instead.
14:38:08 Note that this will be incompatible with Sass 3.2.
14:38:08
14:38:08 WARNING: The box-sizing mixin is deprecated and will be removed in the next major version release. This property can now be used un-prefixed.
14:38:08 on line 410 of static/vendor/bourbon/_bourbon-deprecated-upcoming.scss, in `box-sizing'
14:38:08 from line 12 of static/vendor/susy/susy/output/support/_box-sizing.scss, in `susy-box-sizing'
14:38:08 from line 40 of static/vendor/susy/susy/output/support/_support.scss, in `susy-support'
14:38:08 from line 12 of static/vendor/susy/susy/output/shared/_output.scss, in `output'
14:38:08 from line 28 of static/vendor/susy/susy/language/susy/_span.scss, in `span'
14:38:08 from line 110 of lms/static/certificates/sass/_layouts.scss, in `@content'
14:38:08 from line 24 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `@content'
14:38:08 from line 36 of static/vendor/susy/susy/language/susy/_grids.scss, in `with-layout'
14:38:08 from line 23 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `@content'
14:38:08 from line 75 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `@content'
14:38:08 from line 66 of static/vendor/breakpoint/_breakpoint.scss, in `breakpoint'
14:38:08 from line 74 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `susy-media-router'
14:38:08 from line 21 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `susy-breakpoint'
14:38:08 from line 109 of lms/static/certificates/sass/_layouts.scss
14:38:08 from line 38 of lms/static/certificates/sass/_build.scss
14:38:08 from line 24 of lms/static/certificates/sass/main-rtl.scss
14:38:08
14:38:08 WARNING: The box-sizing mixin is deprecated and will be removed in the next major version release. This property can now be used un-prefixed.
14:38:08 on line 410 of static/vendor/bourbon/_bourbon-deprecated-upcoming.scss, in `box-sizing'
14:38:08 from line 12 of static/vendor/susy/susy/output/support/_box-sizing.scss, in `susy-box-sizing'
14:38:08 from line 40 of static/vendor/susy/susy/output/support/_support.scss, in `susy-support'
14:38:08 from line 12 of static/vendor/susy/susy/output/shared/_output.scss, in `output'
14:38:08 from line 28 of static/vendor/susy/susy/language/susy/_span.scss, in `span'
14:38:08 from line 118 of lms/static/certificates/sass/_layouts.scss, in `@content'
14:38:08 from line 24 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `@content'
14:38:08 from line 36 of static/vendor/susy/susy/language/susy/_grids.scss, in `with-layout'
14:38:08 from line 23 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `@content'
14:38:08 from line 75 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `@content'
14:38:08 from line 66 of static/vendor/breakpoint/_breakpoint.scss, in `breakpoint'
14:38:08 from line 74 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `susy-media-router'
14:38:08 from line 21 of static/vendor/susy/susy/language/susy/_breakpoint-plugin.scss, in `susy-breakpoint'
14:38:08 from line 117 of lms/static/certificates/sass/_layouts.scss
14:38:08 from line 38 of lms/static/certificates/sass/_build.scss
14:38:08 from line 24 of lms/static/certificates/sass/main-rtl.scss
14:38:08
14:38:09 write lms/static/certificates/sass/main-rtl.css
14:38:10 DEPRECATION WARNING on line 43 of lms/static/sass/multicourse/_courses.scss:
14:38:10 Assigning to global variable "$layout-direction" by default is deprecated.
14:38:10 In future versions of Sass, this will create a new local variable.
14:38:10 If you want to assign to the global variable, use "$layout-direction: "RTL" !global" instead.
14:38:10 Note that this will be incompatible with Sass 3.2.
14:38:10
14:38:10 DEPRECATION WARNING on line 13 of lms/static/sass/views/_login-register.scss:
14:38:10 Assigning to global variable "$grid-columns" by default is deprecated.
14:38:10 In future versions of Sass, this will create a new local variable.
14:38:10 If you want to assign to the global variable, use "$grid-columns: 12 !global" instead.
14:38:10 Note that this will be incompatible with Sass 3.2.
14:38:10
14:38:11 DEPRECATION WARNING on line 150 of lms/static/sass/views/_homepage.scss:
14:38:11 Assigning to global variable "$layout-direction" by default is deprecated.
14:38:11 In future versions of Sass, this will create a new local variable.
14:38:11 If you want to assign to the global variable, use "$layout-direction: "RTL" !global" instead.
14:38:11 Note that this will be incompatible with Sass 3.2.
14:38:11
14:38:17 write lms/static/sass/application-rtl.css
14:38:18 DEPRECATION WARNING on line 13 of lms/static/sass/views/_login-register.scss:
14:38:18 Assigning to global variable "$grid-columns" by default is deprecated.
14:38:18 In future versions of Sass, this will create a new local variable.
14:38:18 If you want to assign to the global variable, use "$grid-columns: 12 !global" instead.
14:38:18 Note that this will be incompatible with Sass 3.2.
14:38:18
14:38:24 write lms/static/sass/application.css
14:38:28 write lms/static/sass/course-rtl.css
14:38:33 write lms/static/sass/course.css
14:38:33 write lms/static/sass/lms-footer-edx-rtl.css
14:38:33 write lms/static/sass/lms-footer-edx.css
14:38:33 python manage.py cms --settings=acceptance collectstatic --noinput > /dev/null
14:38:39 DEFAULT_STORE=draft ./manage.py cms --settings acceptance harvest --traceback --debug-mode --verbosity 3 --with-xunit --xunit-file /home/jenkins/workspace/edx-platform-test-subset/reports/acceptance/cms.xml -v 3
14:38:39 ========================================
14:38:39 Running tests for cms acceptance using draft
14:38:39 ========================================
14:38:42 Preparing to serve django's admin site static files...
14:38:58 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:39:09 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:39:19 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:39:33 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:39:49 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:40:02 Django's builtin server is running at 0.0.0.0:8003
14:40:02
14:40:02 Feature: CMS.Advanced (manual) course policy # cms/djangoapps/contentstore/features/advanced_settings.feature:2
14:40:02 In order to specify course policy settings for which no custom user interface exists # cms/djangoapps/contentstore/features/advanced_settings.feature:3
14:40:02 I want to be able to manually enter JSON key /value pairs # cms/djangoapps/contentstore/features/advanced_settings.feature:4
14:40:02
14:40:02 @shard_1
14:40:02 Scenario: A course author sees default advanced settings # cms/djangoapps/contentstore/features/advanced_settings.feature:7
14:40:02 Given I have opened a new course in Studio # cms/djangoapps/contentstore/features/common.py:56
14:40:02 When I select the Advanced Settings # cms/djangoapps/contentstore/features/advanced_settings.py:17
14:40:02 Then I see default advanced settings # cms/djangoapps/contentstore/features/advanced_settings.py:61
14:40:02
14:40:02 @shard_1
14:40:02 Scenario: Add new entries, and they appear alphabetically after save # cms/djangoapps/contentstore/features/advanced_settings.feature:12
14:40:02 Given I am on the Advanced Course Settings page in Studio # cms/djangoapps/contentstore/features/advanced_settings.py:35
14:40:02 Then the settings are alphabetized # cms/djangoapps/contentstore/features/advanced_settings.py:68
14:40:02
14:40:02 @skip_sauce @shard_1
14:40:02 Scenario: Test cancel editing key value # cms/djangoapps/contentstore/features/advanced_settings.feature:18
14:40:02 Given I am on the Advanced Course Settings page in Studio # cms/djangoapps/contentstore/features/advanced_settings.py:35
14:40:02 When I edit the value of a policy key # cms/djangoapps/contentstore/features/advanced_settings.py:41
14:40:02 And I press the "Cancel" notification button # cms/djangoapps/contentstore/features/common.py:87
14:40:02 Then the policy key value is unchanged # cms/djangoapps/contentstore/features/advanced_settings.py:96
14:40:02 And I reload the page # common/djangoapps/terrain/steps.py:36
14:40:02 Then the policy key value is unchanged # cms/djangoapps/contentstore/features/advanced_settings.py:96
14:40:02
14:40:02 @skip_sauce @shard_1
14:40:02 Scenario: Test editing key value # cms/djangoapps/contentstore/features/advanced_settings.feature:28
14:40:02 Given I am on the Advanced Course Settings page in Studio # cms/djangoapps/contentstore/features/advanced_settings.py:35
14:40:02 When I edit the value of a policy key and save # cms/djangoapps/contentstore/features/advanced_settings.py:46
14:40:02 Then the policy key value is changed # cms/djangoapps/contentstore/features/advanced_settings.py:101
14:40:02 And I reload the page # common/djangoapps/terrain/steps.py:36
14:40:02 Then the policy key value is changed # cms/djangoapps/contentstore/features/advanced_settings.py:101
14:40:02
14:40:02 @skip_sauce @shard_1
14:40:02 Scenario: Test how multi-line input appears # cms/djangoapps/contentstore/features/advanced_settings.feature:37
14:40:02 Given I am on the Advanced Course Settings page in Studio # cms/djangoapps/contentstore/features/advanced_settings.py:35
14:40:02 When I create a JSON object as a value for "Discussion Topic Mapping" # cms/djangoapps/contentstore/features/advanced_settings.py:51
14:40:02 Then it is displayed as formatted # cms/djangoapps/contentstore/features/advanced_settings.py:78
14:40:07 And I reload thERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:40:18 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:40:32 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:40:41 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:40:54 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:41:13 e page # common/djangoapps/terrain/steps.py:36
14:41:13 Then it is displayed as formatted # cms/djangoapps/contentstore/features/advanced_settings.py:78
14:41:13
14:41:13 @skip_sauce @shard_1
14:41:13 Scenario: Test error if value supplied is of the wrong type # cms/djangoapps/contentstore/features/advanced_settings.feature:46
14:41:13 Given I am on the Advanced Course Settings page in Studio # cms/djangoapps/contentstore/features/advanced_settings.py:35
14:41:13 When I create a JSON object as a value for "Course Display Name" # cms/djangoapps/contentstore/features/advanced_settings.py:51
14:41:13 Then I get an error on save # cms/djangoapps/contentstore/features/advanced_settings.py:83
14:41:13 And I reload the page # common/djangoapps/terrain/steps.py:36
14:41:13 Then the policy key value is unchanged # cms/djangoapps/contentstore/features/advanced_settings.py:96
14:41:13
14:41:13 @skip_sauce @shard_1
14:41:13 Scenario: Test automatic quoting of non-JSON values # cms/djangoapps/contentstore/features/advanced_settings.feature:56
14:41:13 Given I am on the Advanced Course Settings page in Studio # cms/djangoapps/contentstore/features/advanced_settings.py:35
14:41:13 When I create a non-JSON value not in quotes # cms/djangoapps/contentstore/features/advanced_settings.py:56
14:41:13 Then it is displayed as a string # cms/djangoapps/contentstore/features/advanced_settings.py:91
14:41:13 And I reload the page # common/djangoapps/terrain/steps.py:36
14:41:13 Then it is displayed as a string # cms/djangoapps/contentstore/features/advanced_settings.py:91
14:41:13
14:41:13 @skip_sauce @shard_1
14:41:13 Scenario: Confirmation is shown on save # cms/djangoapps/contentstore/features/advanced_settings.feature:65
14:41:13 Given I am on the Advanced Course Settings page in Studio # cms/djangoapps/contentstore/features/advanced_settings.py:35
14:41:13 When I edit the value of a policy key # cms/djangoapps/contentstore/features/advanced_settings.py:41
14:41:13 And I press the "Save" notification button # cms/djangoapps/contentstore/features/common.py:87
14:41:13 Then I see a confirmation that my changes have been saved # cms/djangoapps/contentstore/features/common.py:124
14:41:13
14:41:13 @shard_1
14:41:13 Scenario: Deprecated Settings are not shown by default # cms/djangoapps/contentstore/features/advanced_settings.feature:71
14:41:13 Given I am on the Advanced Course Settings page in Studio # cms/djangoapps/contentstore/features/advanced_settings.py:35
14:41:13 Then deprecated settings are not shown # cms/djangoapps/contentstore/features/advanced_settings.py:106
14:41:13
14:41:13 @shard_1
14:41:13 Scenario: Deprecated Settings can be toggled # cms/djangoapps/contentstore/features/advanced_settings.feature:75
14:41:13 Given I am on the Advanced Course Settings page in Studio # cms/djangoapps/contentstore/features/advanced_settings.py:35
14:41:13 When I toggle the display of deprecated settings # cms/djangoapps/contentstore/features/advanced_settings.py:115
14:41:13 Then deprecated settings are then shown # cms/djangoapps/contentstore/features/advanced_settings.py:106
14:41:13 And I toggle the display of deprecated settings # cms/djangoapps/contentstore/features/advanced_settings.py:115
14:41:15 Then deprecated settings are not shown # cms/djangoapps/contentstore/featERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:41:19 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:41:27 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:41:33 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Not a gzipped file
14:41:41 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:41:54 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:42:04 ures/advanced_settings.py:106
14:42:04
14:42:04 Feature: CMS.Course checklists # cms/djangoapps/contentstore/features/checklists.feature:2
14:42:04
14:42:04 @shard_1
14:42:04 Scenario: A course author sees checklists defined by edX # cms/djangoapps/contentstore/features/checklists.feature:4
14:42:04 Given I have opened a new course in Studio # cms/djangoapps/contentstore/features/common.py:56
14:42:04 When I select Checklists from the Tools menu # cms/djangoapps/contentstore/features/checklists.py:12
14:42:04 Then I see the four default edX checklists # cms/djangoapps/contentstore/features/checklists.py:26
14:42:04
14:42:04 @shard_1
14:42:04 Scenario: A course author can mark tasks as complete # cms/djangoapps/contentstore/features/checklists.feature:9
14:42:04 Given I have opened Checklists # cms/djangoapps/contentstore/features/checklists.py:20
14:42:04 Then I can check and uncheck tasks in a checklist # cms/djangoapps/contentstore/features/checklists.py:36
14:42:04 And I reload the page # common/djangoapps/terrain/steps.py:36
14:42:04 Then the tasks are correctly selected # cms/djangoapps/contentstore/features/checklists.py:50
14:42:04
14:42:04 @skip_firefox @skip_internetexplorer @skip_safari @shard_1
14:42:04 Scenario: A task can link to a location within Studio# cms/djangoapps/contentstore/features/checklists.feature:19
14:42:04 Given I have opened Checklists # cms/djangoapps/contentstore/features/checklists.py:20
14:42:04 When I select a link to the course outline # cms/djangoapps/contentstore/features/checklists.py:59
14:42:04 Then I am brought to the course outline page # cms/djangoapps/contentstore/features/checklists.py:64
14:42:04 And I press the browser back button # common/djangoapps/terrain/steps.py:43
14:42:04 Then I am brought back to the course outline in the correct state # cms/djangoapps/contentstore/features/checklists.py:70
14:42:04
14:42:04 @skip_firefox @skip_internetexplorer @skip_safari @shard_1
14:42:04 Scenario: A task can link to a location outside Studio# cms/djangoapps/contentstore/features/checklists.feature:30
14:42:04 Given I have opened Checklists # cms/djangoapps/contentstore/features/checklists.py:20
14:42:04 When I select a link to help page # cms/djangoapps/contentstore/features/checklists.py:78
14:42:04 Then I am brought to the help page in a new window # cms/djangoapps/contentstore/features/checklists.py:83
14:42:04
14:42:04 Feature: CMS.Component Adding # cms/djangoapps/contentstore/features/component.feature:2
14:42:04 As a course author, I want to be able to add a wide variety of components # cms/djangoapps/contentstore/features/component.feature:3
14:42:04
14:42:04 @shard_1
14:42:04 Scenario: I can add single step components # cms/djangoapps/contentstore/features/component.feature:5
14:42:04 Given I am in Studio editing a new unit # cms/djangoapps/contentstore/features/common.py:265
14:42:04 When I add this type of single step component: # cms/djangoapps/contentstore/features/component.py:15
14:42:04 | Component |
14:42:04 | Discussion |
14:42:04 | Video |
14:42:04 Then I see this type of single step component: # cms/djangoapps/contentstore/features/component.py:27
14:42:04 | Component |
14:42:04 | Discussion |
14:42:04 | Video |
14:42:04
14:42:04 @shard_1
14:42:04 Scenario: I can add HTML components # cms/djangoapps/contentstore/features/component.feature:16
14:42:04 Given I am in Studio editing a new unit # cms/djangoapps/contentstore/features/common.py:265
14:42:07 When I add this typeERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:42:23 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:42:39 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:42:49 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:42:59 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:43:09 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:43:18 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:43:27 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:43:37 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:43:47 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:43:54 of HTML component: # cms/djangoapps/contentstore/features/component.py:37
14:43:54 | Component |
14:43:54 | Text |
14:43:54 | Announcement |
14:43:54 | Zooming Image Tool |
14:43:54 | Raw HTML |
14:43:54 Then I see HTML components in this order: # cms/djangoapps/contentstore/features/component.py:48
14:43:54 | Component |
14:43:54 | Text |
14:43:54 | Announcement |
14:43:54 | Zooming Image Tool |
14:43:54 | Raw HTML |
14:43:54
14:43:54 @shard_1
14:43:54 Scenario: I can add Latex HTML components # cms/djangoapps/contentstore/features/component.feature:31
14:43:54 Given I am in Studio editing a new unit # cms/djangoapps/contentstore/features/common.py:265
14:43:54 Given I have enabled latex compiler # cms/djangoapps/contentstore/features/problem-editor.py:246
14:43:54 When I add this type of HTML component: # cms/djangoapps/contentstore/features/component.py:37
14:43:54 | Component |
14:43:54 | E-text Written in LaTeX |
14:43:54 Then I see HTML components in this order: # cms/djangoapps/contentstore/features/component.py:48
14:43:54 | Component |
14:43:54 | E-text Written in LaTeX |
14:43:54
14:43:54 @shard_1
14:43:54 Scenario: I can add Common Problem components # cms/djangoapps/contentstore/features/component.feature:41
14:43:54 Given I am in Studio editing a new unit # cms/djangoapps/contentstore/features/common.py:265
14:43:54 When I add this type of Problem component: # cms/djangoapps/contentstore/features/component.py:37
14:43:54 | Component |
14:43:54 | Blank Common Problem |
14:43:54 | Checkboxes |
14:43:54 | Dropdown |
14:43:54 | Multiple Choice |
14:43:54 | Numerical Input |
14:43:54 | Text Input |
14:43:54 Then I see Problem components in this order: # cms/djangoapps/contentstore/features/component.py:48
14:43:54 | Component |
14:43:54 | Blank Common Problem |
14:43:54 | Checkboxes |
14:43:54 | Dropdown |
14:43:54 | Multiple Choice |
14:43:54 | Numerical Input |
14:43:54 | Text Input |
14:43:54
14:43:54 @shard_1
14:43:54 Scenario Outline: I can add Advanced Problem components # cms/djangoapps/contentstore/features/component.feature:60
14:43:54 Given I am in Studio editing a new unit # cms/djangoapps/contentstore/features/common.py:265
14:43:54 When I add a "<Component>" "Advanced Problem" component # cms/djangoapps/contentstore/features/component.py:82
14:43:54 Then I see a "<Component>" Problem component # cms/djangoapps/contentstore/features/component.py:71
14:43:54 And I reset the database # cms/djangoapps/contentstore/features/common.py:110
14:43:54
14:43:54 Examples:
14:43:54 | Component |
14:43:54 | Blank Advanced Problem |
14:43:54 | Circuit Schematic Builder |
14:43:54 | Custom Python-Evaluated Input |
14:43:54 | Drag and Drop |
14:43:54 | Image Mapped Input |
14:43:54 | Math Expression Input |
14:43:54 | Problem with Adaptive Hint |
14:43:54
14:43:54 @shard_1
14:43:54 Scenario: I see a prompt on delete # cms/djangoapps/contentstore/features/component.feature:92
14:43:54 Given I am in Studio editing a new unit # cms/djangoapps/contentstore/features/common.py:265
14:43:58 AndERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:44:17 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:44:30 ERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
14:44:38 I add a "Discussion" "single step" component # cms/djangoapps/contentstore/features/component.py:82
14:44:38 And I delete a component # cms/djangoapps/contentstore/features/component.py:125
14:44:38 Then I am shown a prompt # cms/djangoapps/contentstore/features/common.py:321
14:44:38
14:44:38 @shard_1
14:44:38 Scenario: I can delete Components # cms/djangoapps/contentstore/features/component.feature:98
14:44:38 Given I am in Studio editing a new unit # cms/djangoapps/contentstore/features/common.py:265
14:44:38 And I add a "Discussion" "single step" component # cms/djangoapps/contentstore/features/component.py:82
14:44:38 And I add a "Text" "HTML" component # cms/djangoapps/contentstore/features/component.py:82
14:44:38 And I add a "Blank Common Problem" "Problem" component # cms/djangoapps/contentstore/features/component.py:82
14:44:38 And I add a "Blank Advanced Problem" "Advanced Problem" component # cms/djangoapps/contentstore/features/component.py:82
14:44:38 And I delete all components # cms/djangoapps/contentstore/features/component.py:89
14:44:38 Then I see no components # cms/djangoapps/contentstore/features/component.py:120
14:44:38
14:44:38 @shard_1
14:44:38 Scenario: I can duplicate a component # cms/djangoapps/contentstore/features/component.feature:107
14:44:38 Given I am in Studio editing a new unit # cms/djangoapps/contentstore/features/common.py:265
14:44:38 And I add a "Blank Common Problem" "Problem" component # cms/djangoapps/contentstore/features/component.py:82
14:44:38 And I add a "Multiple Choice" "Problem" component # cms/djangoapps/contentstore/features/component.py:82
14:44:38 And I duplicate the first component # cms/djangoapps/contentstore/features/component.py:136
14:44:38 Then I see a Problem component with display name "Duplicate of 'Blank Common Problem'" in position "1" # cms/djangoapps/contentstore/features/component.py:148
14:44:38 And I reload the page # common/djangoapps/terrain/steps.py:36
14:44:38 Then I see a Problem component with display name "Blank Common Problem" in position "0" # cms/djangoapps/contentstore/features/component.py:148
14:44:38 And I see a Problem component with display name "Duplicate of 'Blank Common Problem'" in position "1" # cms/djangoapps/contentstore/features/component.py:148
14:44:38 And I see a Problem component with display name "Multiple Choice" in position "2" # cms/djangoapps/contentstore/features/component.py:148
14:44:38
14:44:38 @shard_1
14:44:38 Scenario: I can set the display name of a component # cms/djangoapps/contentstore/features/component.feature:118
14:44:38 Given I am in Studio editing a new unit # cms/djangoapps/contentstore/features/common.py:265
14:44:38 When I add a "Text" "HTML" component # cms/djangoapps/contentstore/features/component.py:82
14:44:38 Then I see the display name is "Text" # cms/djangoapps/contentstore/features/component.py:158
14:44:40 When I change the display name to "I'm the CERROR:util.models:String decompression failed. There may be corrupted data in the database: Incorrect padding
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment