github_actions: Stop logging timestamp.

Timestamps are logged automatically by GitHub Actions and can be
made visible using log settings easily. Hence we remove the
unnecessary timestamps here to make the logs look much cleaner.

.github/workflows/production-suite.yml

@@ -90,7 +90,7 @@ jobs:
           sudo sed -i '/^bind/s/bind.*/bind 0.0.0.0/' /etc/redis/redis.conf
 
       - name: Build production tarball
-        run: mispipe "./tools/ci/production-build 2>&1" ts
+        run: ./tools/ci/production-build 2>&1
 
       - name: Upload production build artifacts for install jobs
         uses: actions/upload-artifact@v2
@@ -171,23 +171,23 @@ jobs:
           sudo sed -i '/^bind/s/bind.*/bind 0.0.0.0/' /etc/redis/redis.conf
 
       - name: Production extract tarball
-        run: mispipe "/tmp/production-extract-tarball 2>&1" ts
+        run: /tmp/production-extract-tarball 2>&1
 
       - name: Install production
         run: |
           sudo service rabbitmq-server restart
-          sudo mispipe "/tmp/production-install 2>&1" ts
+          sudo /tmp/production-install 2>&1
 
       - name: Verify install
-        run: sudo mispipe "/tmp/production-verify 2>&1" ts
+        run: sudo /tmp/production-verify 2>&1
 
       - name: Upgrade postgresql
         if: ${{ matrix.is_bionic }}
-        run: sudo mispipe "/tmp/production-upgrade-pg 2>&1" ts
+        run: sudo /tmp/production-upgrade-pg 2>&1
 
       - name: Verify install after upgrading postgresql
         if: ${{ matrix.is_bionic }}
-        run: sudo mispipe "/tmp/production-verify 2>&1" ts
+        run: sudo /tmp/production-verify 2>&1
 
       - name: Report status
         if: failure()

.github/workflows/zulip-ci.yml

@@ -98,28 +98,28 @@ jobs:
       - name: Install dependencies
         run: |
           # This is the main setup job for the test suite
-          mispipe "tools/ci/setup-backend --skip-dev-db-build" ts
+          ./tools/ci/setup-backend --skip-dev-db-build
 
           # Cleaning caches is mostly unnecessary in GitHub Actions, because
           # most builds don't get to write to the cache.
-          # mispipe "scripts/lib/clean-unused-caches --verbose --threshold 0 2>&1" ts
+          # scripts/lib/clean-unused-caches --verbose --threshold 0 2>&1
 
       - name: Run backend tests
         run: |
           . /srv/zulip-py3-venv/bin/activate && \
-          mispipe "./tools/ci/backend 2>&1" ts
+          ./tools/ci/backend 2>&1
 
       - name: Run frontend tests
         if: ${{ matrix.include_frontend_tests }}
         run: |
           . /srv/zulip-py3-venv/bin/activate
-          mispipe "./tools/ci/frontend 2>&1" ts
+          ./tools/ci/frontend 2>&1
 
       - name: Test locked requirements
         if: ${{ matrix.is_bionic }}
         run: |
           . /srv/zulip-py3-venv/bin/activate && \
-          mispipe "./tools/test-locked-requirements 2>&1" ts
+          ./tools/test-locked-requirements 2>&1
 
       - name: Upload coverage reports
 
@@ -153,7 +153,7 @@ jobs:
 
       - name: Check development database build
         if: ${{ matrix.is_focal }}
-        run: mispipe "tools/ci/setup-backend" ts
+        run: ./tools/ci/setup-backend
 
       - name: Report status
         if: failure()

docs/testing/continuous-integration.md

@@ -26,9 +26,11 @@ run to iteratively debug something.
 
 ### Useful debugging tips and tools
 
-* Zulip uses the `ts` tool to log the current time on every line of
-the output in our GitHub Action scripts.  You can use this output to
-determine which steps are actually consuming a lot of time.
+* GitHub Actions stores timestamps for every line in the logs. They
+are hidden by default; you can see them by toggling the `Show
+timestamps` option in the menu on any job's log page.  (You can get
+this sort of timestamp in a development environemnt by piping output
+to `ts`).
 
 * GitHub Actions runs on every branch you push on your Zulip fork.
 This is helpful when debugging something complicated.