Merge branch 'master' into kc/color_stuff

.buildkite-external-version

@@ -0,0 +1 @@
+main

.clang-format

@@ -109,7 +109,6 @@ StatementMacros:
   - checked_intrinsic_ctype
   - cvt_iintrinsic
   - fpiseq_n
-  - fpislt_n
   - ter_fintrinsic
   - ter_intrinsic_ctype
   - un_fintrinsic

.codecov.yml

@@ -0,0 +1,4 @@
+coverage:
+  status:
+    project: off
+    patch: off

.github/CODEOWNERS

@@ -0,0 +1,6 @@
+CODEOWNERS @JuliaLang/github-actions
+/.github/ @JuliaLang/github-actions
+/.buildkite/ @JuliaLang/github-actions
+
+/.github/workflows/retry.yml @DilumAluthge
+/.github/workflows/statuses.yml @DilumAluthge

.github/workflows/rerun_failed.yml

@@ -0,0 +1,92 @@
+# Please ping @DilumAluthge when making any changes to this file.
+
+# Here are some steps that we take in this workflow file for security reasons:
+# 1. We do not checkout any code.
+# 2. We only run actions that are defined in a repository in the `JuliaLang` GitHub organization.
+# 3. We do not give the `GITHUB_TOKEN` any permissions.
+# 4. We only give the Buildkite API token (`BUILDKITE_API_TOKEN_RETRY`) the minimum necessary
+#    set of permissions.
+
+# Important note to Buildkite maintainers:
+# In order to make this work, you need to tell Buildkite that it should NOT create a brand-new
+# build when someone closes and reopens a pull request. To do so:
+# 1. Go to the relevant pipeline (e.g. https://buildkite.com/julialang/julia-master).
+# 2. Click on the "Pipeline Settings" button.
+# 3. In the left sidebar, under "Pipeline Settings", click on "GitHub".
+# 4. In the "GitHub Settings", under "Build Pull Requests", make sure that the "Skip pull
+#    request builds for existing commits" checkbox is checked. This is the setting that tells
+#    Buildkite that it should NOT create a brand-new build when someone closes and reopens a
+#    pull request.
+# 5. At the bottom of the page, click the "Save GitHub Settings" button.
+
+name: Rerun Failed Buildkite Jobs
+
+# There are two ways that a user can rerun the failed Buildkite jobs:
+# 1. Close and reopen the pull request.
+#    In order to use this approach, the user must be in one of the following three categories:
+#        (i)   Author of the pull request
+#        (ii)  Commit permissions
+#        (iii) Triage permissions
+# 2. Post a comment on the pull request with exactly the following contents: /buildkite rerun failed
+#    In order to use this approach, the user must be in the following category:
+#        - A member of the JuliaLang GitHub organization (the membership must be publicized)
+
+on:
+  # When using the `pull_request_target` event, all PRs will get access to secret environment
+  # variables (such as the `BUILDKITE_API_TOKEN_RETRY` secret environment variable), even if
+  # the PR is from a fork. Therefore, for security reasons, we do not checkout any code in
+  # this workflow.
+  pull_request_target:
+    types: [ reopened ]
+  issue_comment:
+    types: [ created ]
+
+# We do not give the `GITHUB_TOKEN` any permissions.
+# Therefore, the `GITHUB_TOKEN` only has the same access as any member of the public.
+permissions:
+  contents: none
+
+jobs:
+  rerun-failed-buildkite-jobs:
+    name: Rerun Failed Buildkite Jobs
+    runs-on: ubuntu-latest
+    if: (github.repository == 'JuliaLang/julia') && ((github.event_name == 'pull_request_target' && github.event.action == 'reopened') || (github.event_name == 'issue_comment' && github.event.issue.pull_request && github.event.comment.body == '/buildkite rerun failed'))
+    steps:
+      # For security reasons, we do not checkout any code in this workflow.
+      - name: Check organization membership
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          if [[ "${{ github.event_name }}" == "pull_request_target" ]]; then
+            if [[ "${{ github.event.action }}" == "reopened" ]]; then
+              echo "This is a \"reopened\" event, so we do not need to check the user's organization membership."
+              echo "GOOD_TO_PROCEED=yes" >> ${GITHUB_ENV:?}
+              echo "PULL_REQUEST_NUMBER=${{ github.event.number }}" >> ${GITHUB_ENV:?}
+            else
+              echo "ERROR: The github.event_name is \"pull_request_target\", but the github.event.action is not \"reopened\"."
+              exit 1
+            fi
+          else
+            curl -H "Authorization: token ${GITHUB_TOKEN:?}" "https://api.github.com/users/${{ github.event.sender.login }}"
+            curl -H "Authorization: token ${GITHUB_TOKEN:?}" "https://api.github.com/users/${{ github.event.sender.login }}/orgs"
+            export USER_IS_ORGANIZATION_MEMBER=`curl -H "Authorization: token ${GITHUB_TOKEN:?}" "https://api.github.com/users/${{ github.event.sender.login }}/orgs" | jq '[.[] | .login] | index("JuliaLang") != null' | tr -s ' '`
+            if [[ "${USER_IS_ORGANIZATION_MEMBER:?}"   == "true" ]]; then
+              echo "The \"${{ github.event.sender.login }}\" user is a public member of the JuliaLang organization."
+              echo "GOOD_TO_PROCEED=yes" >> ${GITHUB_ENV:?}
+              echo "PULL_REQUEST_NUMBER=${{ github.event.issue.number }}" >> ${GITHUB_ENV:?}
+            else
+              echo "ERROR: the \"${{ github.event.sender.login }}\" user is NOT a public member of the JuliaLang organization."
+              echo "If you are a member, please make sure that you have publicized your membership."
+              exit 1
+            fi
+          fi
+      - run: |
+          echo "GOOD_TO_PROCEED: ${{ env.GOOD_TO_PROCEED }}"
+          echo "PULL_REQUEST_NUMBER: ${{ env.PULL_REQUEST_NUMBER }}"
+      - uses: JuliaLang/buildkite-rerun-failed@057f6f2d37aa29a57b7679fd2af0df1d9f9188b4
+        if: env.GOOD_TO_PROCEED == 'yes'
+        with:
+          buildkite_api_token: ${{ secrets.BUILDKITE_API_TOKEN_RETRY }}
+          buildkite_organization_slug: 'julialang'
+          buildkite_pipeline_slug: 'julia-master'
+          pr_number: ${{ env.PULL_REQUEST_NUMBER }}

.github/workflows/statuses.yml

@@ -0,0 +1,65 @@
+# Please ping @DilumAluthge when making any changes to this file.
+
+# This is just a short-term solution until we have migrated all of CI to Buildkite.
+#
+# 1. TODO: delete this file once we have migrated all of CI to Buildkite.
+
+# Here are some steps that we take in this workflow file for security reasons:
+# 1. We do not checkout any code.
+# 2. We do not run any external actions.
+# 3. We only give the `GITHUB_TOKEN` the minimum necessary set of permissions.
+
+name: Create Buildbot Statuses
+
+on:
+  push:
+    branches:
+      - 'master'
+      - 'release-*'
+  # When using the `pull_request_target` event, all PRs will get a `GITHUB_TOKEN` that has
+  # write permissions, even if the PR is from a fork.
+  # Therefore, for security reasons, we do not checkout any code in this workflow.
+  pull_request_target:
+    types: [opened, synchronize]
+    branches:
+      - 'master'
+      - 'release-*'
+
+# These are the permissions for the `GITHUB_TOKEN`.
+# We should only give the token the minimum necessary set of permissions.
+permissions:
+  statuses: write
+
+jobs:
+  create-buildbot-statuses:
+    name: Create Buildbot Statuses
+    runs-on: ubuntu-latest
+    if: github.repository == 'JuliaLang/julia'
+    steps:
+      # For security reasons, we do not checkout any code in this workflow.
+      - run: echo "SHA=${{ github.event.pull_request.head.sha }}" >> $GITHUB_ENV
+        if: github.event_name == 'pull_request_target'
+      - run: echo "SHA=${{ github.sha }}" >> $GITHUB_ENV
+        if: github.event_name != 'pull_request_target'
+      - run: echo "The SHA is ${{ env.SHA }}"
+
+      # As we incrementally migrate individual jobs from Buildbot to Buildkite, we should
+      # remove them from the `context_list`.
+      - run: |
+          declare -a CONTEXT_LIST=(
+                "buildbot/tester_freebsd64"
+                "buildbot/tester_win32"
+                "buildbot/tester_win64"
+                )
+          for CONTEXT in "${CONTEXT_LIST[@]}"
+          do
+            curl \
+              -X POST \
+              -H "Authorization: token $GITHUB_TOKEN" \
+              -H "Accept: application/vnd.github.v3+json" \
+              -d "{\"context\": \"$CONTEXT\", \"state\": \"$STATE\"}" \
+            https://api.github.com/repos/JuliaLang/julia/statuses/${{ env.SHA }}
+          done
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          STATE: "pending"

.gitignore

@@ -22,6 +22,7 @@
 *.so
 *.dylib
 *.dSYM
+*.h.gen
 *.jl.cov
 *.jl.*.cov
 *.jl.mem
@@ -31,3 +32,13 @@
 /perf*
 .DS_Store
 .idea/*
+.vscode/*
+
+# Buildkite: Ignore the entire .buildkite directory
+/.buildkite
+
+# Buildkite: Ignore the unencrypted repo_key
+repo_key
+
+# Buildkite: Ignore any agent keys (public or private) we have stored
+agent_key*

.mailmap

@@ -24,6 +24,8 @@ Viral B. Shah <viral@mayin.org> <viral@mayin.org>
 Viral B. Shah <viral@mayin.org> <viral@beowulf1.csail.mit.edu>
 Viral B. Shah <viral@mayin.org> <viral@neumann.cs.ucsb.edu>
 Viral B. Shah <viral@mayin.org> <viral@ubuntu-VirtualBox.(none)>
+Viral B. Shah <viral@mayin.org> <viral@juliacomputing.com>
+Viral B. Shah <viral@mayin.org> <ViralBShah@users.noreply.github.com>
 
 George Xing <gxing@mit.edu> <gxing@mit.edu>
 George Xing <gxing@mit.edu> <noobiecubie@gmail.com>
@@ -257,3 +259,27 @@ Curtis Vogt <curtis.vogt@gmail.com> <curtis.vogt@invenia.ca>
 
 Rafael Fourquet <fourquet.rafael@gmail.com> <fourquet.rafael@gmail.com>
 Rafael Fourquet <fourquet.rafael@gmail.com> <fourquet.rafael+github@gmail.com>
+
+Nathan Daly <NHDaly@gmail.com> <NHDaly@gmail.com>
+Nathan Daly <NHDaly@gmail.com> <nhDaly@gmail.com>
+
+Mosè Giordano <mose@gnu.org> <mose@gnu.org>
+Mosè Giordano <mose@gnu.org> <giordano@users.noreply.github.com>
+
+Andy Ferris <ferris.andy@gmail.com> <ferris.andy@gmail.com>
+Andy Ferris <ferris.andy@gmail.com> <andy.ferris@roames.com.au>
+
+David Varela <varela.david.dv@gmail.com> <00.varela.david@gmail.com>
+David Varela <varela.david.dv@gmail.com> <varela.david.dv@gmail.com>
+
+Arch D. Robison <arch.robison@intel.com> <arch.robison@intel.com>
+Arch D. Robison <arch.robison@intel.com> <ArchRobison@users.noreply.github.com>
+
+Matt Bauman <mbauman@gmail.com> <mbauman@gmail.com>
+Matt Bauman <mbauman@gmail.com> <mbauman@juliacomputing.com>
+
+Daniel Karrasch <Daniel.Karrasch@gmx.de> <Daniel.Karrasch@gmx.de>
+Daniel Karrasch <Daniel.Karrasch@gmx.de> <daniel.karrasch@posteo.de>
+
+Roger Luo <rogerluo.rl18@gmail.com> <rogerluo.rl18@gmail.com>
+Roger Luo <rogerluo.rl18@gmail.com> <hiroger@qq.com>