[SERVER-36579] Test for dump_scons_config_on_failure in evergreen.yml needs to be fixed Created: 10/Aug/18  Updated: 06/Dec/22  Resolved: 11/May/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: stm, tig-evgconfig
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Tooling & Methods
Operating System: ALL
Participants:

 Description   

The following test can error if dump_scons_config_on_failure is not defined:

          if [ ${dump_scons_config_on_failure} = 'true' ]; then
            echo "Dumping build/scons/config.log"
            cat build/scons/config.log
          fi

[2018/08/09 17:28:34.937] scons: *** [build\cached\mongo\db\storage\biggie\store_test.obj] Error 2
[2018/08/09 17:28:34.937] exit_status=$?
[2018/08/09 17:28:34.937] # If compile fails we do not run any tests
[2018/08/09 17:28:34.937] if [ $exit_status -ne 0 ]; then
[2018/08/09 17:28:34.937]   if [  = 'true' ]; then
[2018/08/09 17:28:34.937]     echo "Dumping build/scons/config.log"
[2018/08/09 17:28:34.937]     cat build/scons/config.log
[2018/08/09 17:28:34.937]   fi
[2018/08/09 17:28:34.937]   touch skip_test-mongodb_mongo_master_enterprise_windows_64_2k8_compile_all_patch_2e69710b5bf058dae6d04ada3cb003cbf872c3a8_5b6ca4aae3c33143c9426311_18_08_09_20_33_54
[2018/08/09 17:28:34.979] fi
sh: line 37: [: =: unary operator expected
exit $exit_status
[2018/08/09 17:28:34.979] Command failed: command [pid=4916] encountered problem: exit status 2



 Comments   
Comment by Ryan Timmons [ 11/May/20 ]

Major changes to evergreen.yml coming via INIT-57.

Comment by Jonathan Abrahams [ 10/Aug/18 ]

Either quote it or add a default value, i.e., false

Comment by Max Hirschhorn [ 10/Aug/18 ]

Should we just put quotes around the expansion's usage?

Generated at Thu Feb 08 04:43:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.