corejavascript/typeahead.js

Travis Not running Browser tests

Open

#20 opened on 2015年10月16日

GitHub で見る
 (5 comments) (0 reactions) (1 assignee)JavaScript (956 stars) (232 forks)batch import
bughelp wanted

説明

Hi, of the 12 jobs running upon every Pull-request commit, none of the browser specific tests run!

Only the unit-test runs.

For example on #18, the tests ran, but only travis build 26.1 actually ran the test suite.

The others (browser based) had the following line in the output:

Not running any tests

which you can see for instance in travis build 26.2 and all the others in the travis build list for #18.

The line in test/ci https://github.com/corejavascript/typeahead.js/blob/master/test/ci#L5

elif [ "$TRAVIS_SECURE_ENV_VARS" == "true" -a "$TEST_SUITE" == "integration" ]; then

evaluates to

+'[' false == true -a integration == integration ']'

which must mean that "$TRAVIS_SECURE_ENV_VARS" is not set.

Who can help setting up the browser tests again?? I'd like to help but am in doubt about who has access to setting it up?

コントリビューターガイド

技術スタック
javascript
領域
devopstesting
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Travis CI configurationbash scriptingrepository admin access
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
30
調査方針
Examine the test/ci script and the Travis CI configuration. The issue is that $TRAVIS SECURE ENV VARS is not set to true for pull requests from forks, causing the browser tests to be skipped. Check Travis CI documentation on secure environment variables and consider whether the repository requires admin intervention to set them. Look into alternative approaches that do not rely on secure vars.