# 2.7.0.beta7에서 2.7.0.beta9로 업그레이드할 때 「\_theme\_qunit\_helper에서 구문 오류」 발생
**URL:** https://meta.discourse.org/t/parse-error-at-theme-qunit-helper-when-upgrading-from-2-7-0-beta7-to-2-7-0-beta9/190120
**Category:** Support
**Created:** [5월 11, 2021, 9:56오후 UTC](https://meta.discourse.org/t/parse-error-at-theme-qunit-helper-when-upgrading-from-2-7-0-beta7-to-2-7-0-beta9/190120 "2021-05-11T21:56:42Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@mig5](https://meta.discourse.org/u/mig5)
#### Post date: [5월 11, 2021, 9:56오후 UTC](https://meta.discourse.org/t/parse-error-at-theme-qunit-helper-when-upgrading-from-2-7-0-beta7-to-2-7-0-beta9/190120/1 "2021-05-11T21:56:42Z")
정기적인 Discourse 업그레이드 실패가 또 발생했습니다..
2.7.0.beta7에서 2.7.0.beta9로
웹 콘솔을 통해 Docker Manager 앱을 문제 없이 업그레이드했습니다.
그 후 메인 앱 업그레이드를 시작했는데, 이 오류가 발생하기 전까지는 잘 진행되고 있었습니다:
```plaintext
2417659.54670619 Compressing: discourse/tests/theme_qunit_helper-205cf3e536cd4118ac1b02aec22cd3f45e8f74826fa96abeb697c0243882e5d2.js
uglifyjs '/var/www/discourse/public/assets/discourse/tests/_theme_qunit_helper-205cf3e536cd4118ac1b02aec22cd3f45e8f74826fa96abeb697c0243882e5d2.js' -m -c -o '/var/www/discourse/public/assets/discourse/tests/theme_qunit_helper-205cf3e536cd4118ac1b02aec22cd3f45e8f74826fa96abeb697c0243882e5d2.js' --source-map "base='/var/www/discourse/public/assets/discourse/tests',root='/assets/discourse/tests',url='/assets/discourse/tests/theme_qunit_helper-205cf3e536cd4118ac1b02aec22cd3f45e8f74826fa96abeb697c0243882e5d2.js.map'"
Parse error at _theme_qunit_helper-205cf3e536cd4118ac1b02aec22cd3f45e8f74826fa96abeb697c0243882e5d2.js:27887,17
define("sinon", () => {
^
ERROR: Unexpected token: punc «)»
at JS_Parse_Error.get (eval at (/usr/lib/node_modules/uglify-js/tools/node.js:18:1), :71:23)
at fatal (/usr/lib/node_modules/uglify-js/bin/uglifyjs:409:27)
at run (/usr/lib/node_modules/uglify-js/bin/uglifyjs:347:9)
at Object. (/usr/lib/node_modules/uglify-js/bin/uglifyjs:261:5)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:30)
at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
rake aborted!
Errno::ENOENT: No such file or directory @ rb_file_s_size - /var/www/discourse/public/assets/discourse/tests/theme_qunit_helper-205cf3e536cd4118ac1b02aec22cd3f45e8f74826fa96abeb697c0243882e5d2.js
/var/www/discourse/lib/tasks/assets.rake:290:in `size'
/var/www/discourse/lib/tasks/assets.rake:290:in `block (4 levels) in '
/var/www/discourse/lib/tasks/assets.rake:181:in `block in concurrent?'
/var/www/discourse/lib/tasks/assets.rake:281:in `block (3 levels) in '
/var/www/discourse/lib/tasks/assets.rake:272:in `each'
/var/www/discourse/lib/tasks/assets.rake:272:in `block (2 levels) in '
/var/www/discourse/lib/tasks/assets.rake:181:in `concurrent?'
/var/www/discourse/lib/tasks/assets.rake:269:in `block in '
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rake-13.0.3/exe/rake:27:in `'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `'
Tasks: TOP => assets:precompile
(See full trace by running task with --trace)
Docker Manager: FAILED TO UPGRADE
#
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:196:in `run'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:104:in `upgrade'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:19:in `block in '
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `fork'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.7.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:59:in `load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.7.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:59:in `load'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.0.3.5/lib/rails/commands/runner/runner_command.rb:42:in `perform'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.1.0/lib/thor/command.rb:27:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.1.0/lib/thor/invocation.rb:127:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.1.0/lib/thor.rb:392:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.0.3.5/lib/rails/command/base.rb:69:in `perform'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.0.3.5/lib/rails/command.rb:46:in `invoke'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.0.3.5/lib/rails/commands.rb:18:in `'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.7.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.7.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.7.3/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.7.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.7.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
bin/rails:17:in `'
Spinning up 2 Unicorn worker(s) that were stopped initially
```
이 문제를 해결하는 방법에 대한 팁을 주실 분이 계신가요? 웹 인터페이스에서 지원되는 것처럼 보이지만, 실제로는 CLI를 통해 수행해야 하는 업그레이드 중 하나였나요? (이전에 그런 문제로 곤란을 겪은 적이 있습니다)
감사합니다!
---
### Author:  [@mig5](https://meta.discourse.org/u/mig5)
#### Post date: [5월 11, 2021, 10:09오후 UTC](https://meta.discourse.org/t/parse-error-at-theme-qunit-helper-when-upgrading-from-2-7-0-beta7-to-2-7-0-beta9/190120/2 "2021-05-11T22:09:05Z")
아 네, 맞습니다. [2.7.0.beta8: Share Topic Modal Improvements, Searchable User Fields, Pause Animated Images, and more](https://meta.discourse.org/t/2-7-0-beta8-share-topic-modal-improvements-searchable-user-fields-pause-animated-images-and-more/188564) 에 언급된 대로 2.7.0.beta8 버전에서 수동 재빌드가 필요했던 것 같습니다.
웹 인터페이스를 통해 업그레이드를 시도해 보게 허용받은 _이후_에야 /admin/upgrade 페이지에서 'Discourse 이미지의 구버전을 실행 중입니다. 최신 이미지를 실행할 때까지 웹 UI를 통한 업그레이드는 비활성화됩니다.'라는 메시지가 표시되는 것이 이상합니다. 만약 처음부터 이렇게 표시되었다면 시도해 보지도(못했을 것입니다!) 않았을 텐데요. 예전에는 이런 방식으로 작동한다고 확신했는데… 어쨌든, 이제 모두 해결되었습니다 🙂