In CI, Journey Test failing to iterate over exercises
See original GitHub issueWhen I run bin/journey_test.sh
locally, it works perfectly.
However, reviewing the logs in Travis, in the solve_all_exercises()
function, the for-loop that would iterate over the exercises simply does not execute… as if the exercises
variable were empty.
Issue Analytics
- State:
- Created 7 years ago
- Comments:17 (17 by maintainers)
Top Results From Across the Web
A Breakdown of Continuous Integration Testing - Harness
A Breakdown of Continuous Integration Testing. Continuous Integration Testing is testing that is focused and executed during the CI process.
Read more >Cypress - Iterate over each element and perform some action ...
I ran a simple app with modal and toast. If you fix the toast part of the test it's possible to iterate the...
Read more >For Each test step - Provar
Continue On Failure: Tick this checkbox if the for-each should continue after failure of any iteration within the loop. Then save the test...
Read more >How to use iterations and conditions activities in Azure Data ...
In this article, we will show how to use the Iterations and Conditions activities in Azure Data factory.
Read more >Pandas Iterate Over Rows - Machine Learning Plus
Using a for loop, we can iterate over the rows of the DataFrame . The below example prints the 'Name' column value of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Great, thank you! It works! 😄 I did have a look at that section of https://stedolan.github.io/jq/download/ before, but I wasn’t sure whether that was something we were allowed to do. But it all works now so happy days 😄
Travis looks to have a global version (not sure what that is), but I wonder if we could override that with a
before_install
instruction?https://docs.travis-ci.com/user/installing-dependencies/