# Ppc64le: An error occurred while generating the build script **URL:** \ **Category:** Travis CI Discussions & Feedback\ **Tags:** travis-build\ **Created:** [December 22, 2019, 5:10pm UTC](https://travis-ci.community/t/ppc64le-an-error-occurred-while-generating-the-build-script/6598 "2019-12-22T17:10:32Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![akimd](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/akimd/32/2949_2.png) [@akimd](https://travis-ci.community/u/akimd)\ **Post date:** [December 22, 2019, 5:10pm UTC](https://travis-ci.community/t/ppc64le-an-error-occurred-while-generating-the-build-script/6598/1 "2019-12-22T17:10:32Z")
There are no clear messages, I have no idea what I’m doing wrong. Thanks a lot for Travis! [https://travis-ci.org/akimd/bison/jobs/628401970?utm\_medium=notification&utm\_source=email](https://travis-ci.org/akimd/bison/jobs/628401970?utm_medium=notification&utm_source=email) ---
**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\ **Post date:** [December 23, 2019, 1:44am UTC](https://travis-ci.community/t/ppc64le-an-error-occurred-while-generating-the-build-script/6598/2 "2019-12-23T01:44:22Z")
Bottom line: the contents of `env: global:` must be a list: ```auto env: global: - secure: "" ``` If you enable [build config validation](https://docs.travis-ci.com/user/build-config-validation), it might detect and/or fix this automatically. * * * Running `travis-build` (the component responsible for generating a build script from `.travis.yml`) locally as explained in [https://github.com/travis-ci/travis-build/blob/master/README.md](https://github.com/travis-ci/travis-build/blob/master/README.md) shows the exception: ``` E Travis::Build::EnvVarDefinitionError: Environment variables definition is incorrect. /home/vmuser/travis-build/lib/travis/build/env/var.rb:30:in `rescue in parse' /home/vmuser/travis-build/lib/travis/build/env/var.rb:23:in `parse' /home/vmuser/travis-build/lib/travis/build/env/config.rb:20:in `block in env_vars' /home/vmuser/travis-build/lib/travis/build/env/config.rb:20:in `each' ``` I had to patch the appropriate source line to include the offending `line` in message. Which turned out to be ``` [:secure, "B3manbbi0anCAGDJTdAa9TlodzRHeiYD87FKmFzS877dPm8Cm0BDvtUhKBUpBvP8+nbHOWFGrgDmLugSZjTGU+mAxtuQpamUFHvinu0BIk3qtjlqouwvbtIqUu8iiZ3Uqu+xKeAANKRy0YVZGLlEb9F3N119tJ/Fxp1p9bXL1qph+CZ25OFbUgZ2s4F+/AyHMUxJlNXKFe3Qean65hC6edhU3zoaKzr/g/wtbhRmcyWbkOa1dJqzr2yKotcPvrnApGhDzgMKFtohg/t7xfMADDVv6sGS5XNpt25Z+MUCmLg4Z9eD7u109jvRV1eu/jgVafqsthWEhXbuMiFgFhKBKGCNZ0dACIfKZSkFZI6FdM7ovJ6aNhSlxZ2169Ybd22rN1UTHeCQWySPcVVOg5taLVpqe+E8Xhnv4hBO5NrzElWwCMLxIdPUSwVStYvtDr8ZytHWzfot50vSnFKIFpTOr9hP4+AJMVmmqJfaJo2MLBft/q2xkztrMv3lQSj3m4+ma9kPDwXIu9uCutjlnhc00jNx9qegi5VfpAjxcG1R+pX4T20az6ByHk/7LPQsANkT31RJq/jAeD9LEuMOy8miha83q4QuvbFaqPK3PY0el/O1LZaXqLsV2aQ0uqH8YX0l4r5NzHdhb+3lYgvpMBO5ytr/EWJiEyNYV518050IUDE="] ``` ---
**Author:** ![pevik](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/pevik/32/3497_2.png) [@pevik](https://travis-ci.community/u/pevik)\ **Post date:** [December 25, 2019, 7:22am UTC](https://travis-ci.community/t/ppc64le-an-error-occurred-while-generating-the-build-script/6598/3 "2019-12-25T07:22:12Z")
I also experienced this issue: ppc64le started occasionally fail with `An error occurred while generating the build script.`, for no obvious reason after some time working without problems. It looks like to be a travis issue. [https://travis-ci.org/linux-test-project/ltp/jobs/627357455](https://travis-ci.org/linux-test-project/ltp/jobs/627357455) ---
**Author:** ![akimd](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/akimd/32/2949_2.png) [@akimd](https://travis-ci.community/u/akimd)\ **Post date:** [December 25, 2019, 3:32pm UTC](https://travis-ci.community/t/ppc64le-an-error-occurred-while-generating-the-build-script/6598/4 "2019-12-25T15:32:17Z")
Hi Pevik, Thanks for your message. Yes, I don’t think native-api’s answer is the full story: I’ve had this definition of my secure variable for ages, and it always worked (meaning: the value was taken into account). And as could be seen in that build, it worked on the other architectures. Yet, for some reason, it worked once on PPC64le ([https://travis-ci.org/akimd/bison/jobs/628598485?utm\_medium=notification&utm\_source=email](https://travis-ci.org/akimd/bison/jobs/628598485?utm_medium=notification&utm_source=email)) _without_ native-api’s fix for the secure var, and failed again since then ([https://travis-ci.org/akimd/bison/jobs/628606198?utm\_medium=notification&utm\_source=email](https://travis-ci.org/akimd/bison/jobs/628606198?utm_medium=notification&utm_source=email)) with no clear error message, although I did add “version: ~\> 1.0”. That’s _with_ native-api’s fix for the syntax for the secure var. Finally, in [https://travis-ci.org/akimd/bison/jobs/629406118](https://travis-ci.org/akimd/bison/jobs/629406118) I completely removed the definition of the secure var, to no avail. So I also do believe the problem is rather on Travis’ side. FWIW though, I kinda sad: I was hoping one of these architectures would have char being unsigned, but it appears that it’s not. Cheers! And Merry Christmas! ---
**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\ **Post date:** [December 25, 2019, 4:01pm UTC](https://travis-ci.community/t/ppc64le-an-error-occurred-while-generating-the-build-script/6598/5 "2019-12-25T16:01:23Z")
For @pevik’s config, `travis compile` runs without error, so this must the in the proprietary part of the machinery thus I cannot help here any further. ---
**Author:** ![Cyan4973](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/cyan4973/32/3516_2.png) [@Cyan4973](https://travis-ci.community/u/Cyan4973)\ **Post date:** [December 27, 2019, 11:54pm UTC](https://travis-ci.community/t/ppc64le-an-error-occurred-while-generating-the-build-script/6598/6 "2019-12-27T23:54:22Z")
Same thing here: all projects using ppc64le are failing currently, precisely and only on the ppc64le test, with the same message : > An error occurred while generating the build script. ---
**Author:** ![Damian](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/damian/32/3625_2.png) [@Damian](https://travis-ci.community/u/Damian)\ **Post date:** [December 30, 2019, 9:06am UTC](https://travis-ci.community/t/ppc64le-an-error-occurred-while-generating-the-build-script/6598/7 "2019-12-30T09:06:19Z")
Hi, Builds on ppc64le .org are back to normal. We are sorry for the inconvenience. ---
**Author:** ![ghatwala](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/ghatwala/32/4342_2.png) [@ghatwala](https://travis-ci.community/u/ghatwala)\ **Post date:** [December 30, 2019, 9:06am UTC](https://travis-ci.community/t/ppc64le-an-error-occurred-while-generating-the-build-script/6598/8 "2019-12-30T09:06:37Z")
@akimd - I think there was a back-end issue , please retry job deployment now , its back to working normally now - [https://travis-ci.org/ghatwala/python-testing/builds/612015314](https://travis-ci.org/ghatwala/python-testing/builds/612015314) ---
**Author:** ![akimd](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/akimd/32/2949_2.png) [@akimd](https://travis-ci.community/u/akimd)\ **Post date:** [December 30, 2019, 3:49pm UTC](https://travis-ci.community/t/ppc64le-an-error-occurred-while-generating-the-build-script/6598/9 "2019-12-30T15:49:36Z")
Hi Damian, Yes, it’s back. Thanks a lot! FTR, the syntax check for travis.yml does not know about git: clone: false. See [https://travis-ci.org/akimd/bison/builds/630957210/config](https://travis-ci.org/akimd/bison/builds/630957210/config) for instance: Build config validation `jobs.include.git` : unknown key `clone` ( `true` ) `git` : unknown key `clone` ( `false` ) `root` : missing `os` , using the default `linux` `language` : value `minimal` is an alias for `shell` , using `shell`