Skip to content

Conversation

@cderv
Copy link
Collaborator

@cderv cderv commented Aug 29, 2025

  • Add _ to .qmd file so that they are not picked up by test suite as test files. We don't delete them because we plan to recreate the missing repo and update the test
  • Add a README in the folder to explain the situation
  • Remove the test from list of tests in timing-for-ci.txt so that they are not run in CI as part of parallel testing.

Our test suites was failing because one repo used in test has been removed from Github.
It was using some giscus-examples and I don't have a copy of it.

So we'll need to look into those tests, recreate or remove.

For now I believe the following will help ignore the test

- Add `_` to .qmd file so that they are not picked up by test suite as test files. We don't delete them because we plan to recreate the missing repo and update the test
- Add a README in the folder to explain the situation
- Remove the test from list of tests in `timing-for-ci.txt` so that they are not run in CI as part of parallel testing.
@posit-snyk-bot
Copy link
Collaborator

posit-snyk-bot commented Aug 29, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

@cderv cderv force-pushed the tests/fix-giscus-example-tests branch from fefdc12 to d76810f Compare August 29, 2025 11:15
@cderv
Copy link
Collaborator Author

cderv commented Aug 29, 2025

FYI @gordonwoodhull @cscheid

Those test will need to be reactivated in some manner. They are related to giscus. I know we added more, since but still.

Anyhow, this PR is meant to unblock the failure due to the example repo being 404 now.

I don't have a copy of its content, so I can't just change the url.

@cderv cderv merged commit f9726e2 into main Aug 29, 2025
100 checks passed
@cderv cderv deleted the tests/fix-giscus-example-tests branch August 29, 2025 11:46
@cscheid
Copy link
Collaborator

cscheid commented Sep 2, 2025

Which repository specifically disappeared?

@cderv
Copy link
Collaborator Author

cderv commented Sep 2, 2025

Sorry I should have mentioned. This one

website:
comments:
giscus:
repo: allenmanning/giscus-examples

@gordonwoodhull
Copy link
Contributor

gordonwoodhull commented Sep 2, 2025

These seem to be just smoke tests, so the content doesn't matter.

The pages preview fine when I substitute quarto-dev/quarto-cli.

I'm not sure how the 404 in the giscus iframe is detected. It's not a render failure. I think I saw the error once, but I'm not finding it in the logs.

#13319 passes CI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants