Unverified Commit e8f8c8e2 authored by Tim Neutkens's avatar Tim Neutkens Committed by GitHub

Add additional logs to next-integration-stat (#64169)

## What?

We're currently seeing a failure on this action but it's unclear why it
happens so this PR introduces additional logs.

Current failure:
https://github.com/vercel/next.js/actions/runs/8550039767/job/23427388195#step:4:110

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->


Closes NEXT-3024
parent 8c6532fa
import { context, getOctokit } from '@actions/github' import { context, getOctokit } from '@actions/github'
import { info, getInput } from '@actions/core' import { info, getInput } from '@actions/core'
const { default: stripAnsi } = require('strip-ansi') const { default: stripAnsi } = require('strip-ansi')
const { default: nodeFetch } = require('node-fetch')
const fs = require('fs') const fs = require('fs')
const path = require('path') const path = require('path')
const semver = require('semver') const semver = require('semver')
...@@ -43,7 +42,7 @@ async function findNextJsVersionFromBuildLogs( ...@@ -43,7 +42,7 @@ async function findNextJsVersionFromBuildLogs(
) )
// fetch the actual logs // fetch the actual logs
const jobLogsResponse = await nodeFetch(jobLogRedirectResponse.url, { const jobLogsResponse = await fetch(jobLogRedirectResponse.url, {
headers: { headers: {
Accept: 'application/vnd.github.v3+json', Accept: 'application/vnd.github.v3+json',
// [NOTE] we used to attach auth token, but seems this can cause 403 // [NOTE] we used to attach auth token, but seems this can cause 403
...@@ -83,8 +82,7 @@ async function fetchJobLogsFromWorkflow( ...@@ -83,8 +82,7 @@ async function fetchJobLogsFromWorkflow(
job: Job job: Job
): Promise<{ logs: string; job: Job }> { ): Promise<{ logs: string; job: Job }> {
console.log( console.log(
'fetchJobLogsFromWorkflow: Checking test results for the job ', `fetchJobLogsFromWorkflow ${job.name}: Checking test results for the job`
job.name
) )
// downloadJobLogsForWorkflowRun returns a redirect to the actual logs // downloadJobLogsForWorkflowRun returns a redirect to the actual logs
...@@ -96,18 +94,21 @@ async function fetchJobLogsFromWorkflow( ...@@ -96,18 +94,21 @@ async function fetchJobLogsFromWorkflow(
}) })
console.log( console.log(
'fetchJobLogsFromWorkflow: Trying to get logs from redirect url ', `fetchJobLogsFromWorkflow ${job.name}: Trying to get logs from redirect url ${jobLogRedirectResponse.url}`
jobLogRedirectResponse.url
) )
// fetch the actual logs // fetch the actual logs
const jobLogsResponse = await nodeFetch(jobLogRedirectResponse.url, { const jobLogsResponse = await fetch(jobLogRedirectResponse.url, {
headers: { headers: {
Accept: 'application/vnd.github.v3+json', Accept: 'application/vnd.github.v3+json',
//Authorization: `token ${token}`, //Authorization: `token ${token}`,
}, },
}) })
console.log(
`fetchJobLogsFromWorkflow ${job.name}: Logs response status ${jobLogsResponse.status}`
)
if (!jobLogsResponse.ok) { if (!jobLogsResponse.ok) {
throw new Error( throw new Error(
`Failed to get logsUrl, got status ${jobLogsResponse.status}` `Failed to get logsUrl, got status ${jobLogsResponse.status}`
...@@ -285,6 +286,8 @@ async function getJobResults( ...@@ -285,6 +286,8 @@ async function getJobResults(
) )
) )
console.log('Logs downloaded for all jobs')
const testResultManifest: TestResultManifest = { const testResultManifest: TestResultManifest = {
nextjsVersion, nextjsVersion,
buildTime, buildTime,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment