1# Azure Pipelines configuration for Exhaustive Tests for ICU. 2# 3# Note: The exhaustive test configuration is in a separate file 4# so that it can be run independently from the regular builds. 5# 6# Only run the exhaustive tests on the master and maint branches, and 7# also batch up any pending changes so that we will only have at most 8# one build running at a given time (since they take a long time). 9trigger: 10 batch: true 11 branches: 12 include: 13 - master 14 - maint/maint-* 15 16jobs: 17#------------------------------------------------------------------------- 18# Note: The exhaustive tests for J take longer than the C tests. They 19# take roughly 85 min to complete on the Azure VMs. 20- job: ICU4J_OpenJDK_Ubuntu_1604 21 displayName: 'J: Linux OpenJDK (Ubuntu 16.04)' 22 timeoutInMinutes: 100 23 pool: 24 vmImage: 'Ubuntu 16.04' 25 demands: ant 26 steps: 27 - checkout: self 28 lfs: true 29 fetchDepth: 1 30 - script: | 31 echo "Building ICU4J" && cd icu4j && ant init && ant exhaustiveCheck 32 displayName: 'Build and Exhaustive Tests' 33 env: 34 BUILD: ICU4J 35 - script: | 36 [ -d icu4j/out/junit-results ] && cd icu4j && cat `find out/junit-results -name "*.txt" -exec grep -l FAILED {} \;` 37 condition: failed() # only run if the build fails. 38 displayName: 'List failures (if any)' 39 timeoutInMinutes: 2 40#------------------------------------------------------------------------- 41# Note: The exhaustive tests take roughly 65 mins to complete on the 42# Azure VMs. 43- job: ICU4C_Clang_Exhaustive_Ubuntu_1604 44 displayName: 'C: Linux Clang Exhaustive Tests (Ubuntu 16.04)' 45 timeoutInMinutes: 80 46 pool: 47 vmImage: 'Ubuntu 16.04' 48 steps: 49 - checkout: self 50 lfs: true 51 fetchDepth: 1 52 - script: | 53 cd icu4c/source && ./runConfigureICU Linux && make -j2 54 displayName: 'Build' 55 - script: | 56 cd icu4c/source && make check-exhaustive 57 displayName: 'Exhaustive Tests' 58 env: 59 CC: clang 60 CXX: clang++ 61#------------------------------------------------------------------------- 62 63