# Testing for the v8.17 release

**URL:** <https://racket.discourse.group/t/testing-for-the-v8-17-release/3698>\
**Category:** Internals\
**Tags:** release-management, release\
**Created:** [April 22, 2025, 4:51am UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698 "2025-04-22T04:51:52Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![jbclements](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/jbclements/32/11_2.png) [@jbclements](https://racket.discourse.group/u/jbclements)\
**Post date:** [April 22, 2025, 4:51am UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/1 "2025-04-22T04:51:52Z")

</div>

Testing for the v8.17 release  
(using the v8.16.900 release candidate build)

```
Search for your name on the checklist page to find relevant items, either
reply when you finish an item (please indicate which item/s is/are done),
or check it off yourself on the checklist page. Also, if you have any
commits that should have been picked, make sure that the changes are in.

Be sure to finish your testing by the 27th. Otherwise the release
will move on without your input.

The checklist page is at:
     https://github.com/racket/racket/wiki/Release-Checklist-8.17

Release candidates are at:
     https://pre-release.racket-lang.org

Please use these installers (or source bundles) -- don't test from
your own git clone (don't test the `master' branch by mistake!).
To get the tests, you can do this:

  cd ...racket-root...
  ./bin/raco pkg install -i --auto main-distribution-test

```

---

<div class="post-metadata">

**Author:** ![EmEf](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@EmEf](https://racket.discourse.group/u/EmEf)\
**Post date:** [April 22, 2025, 3:32pm UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/2 "2025-04-22T15:32:57Z")

</div>

@mike When I run 'racket-tests' in 'htdp-test/tests/test-engine' in drracket, I get three test failures. Can you check these out please? Thanks.

@jbclements I don't think this is a show-stopper but we should wait for a reply from @mike

---

<div class="post-metadata">

**Author:** ![EmEf](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@EmEf](https://racket.discourse.group/u/EmEf)\
**Post date:** [April 22, 2025, 3:43pm UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/3 "2025-04-22T15:43:49Z")

</div>

1. When I close all windows and use cmd-N to open a new one, I don’t get a new window. (I see this in the drracket @ HEAD too.)  
— I do get a new window via a mouse gesture and the drop-down menu.

2a. Using F1 for docs fails. It does bring up a page with a search window using a file URL.

2b. Searching the docs fails. When I enter `big-bang` in the search window of my browser, it seems to do something for perhsp a second or two and then switches from the “home page” to the “results page” but shows no results.

2c. Some of the links on the right menu work (e.g. the Release Notes link (local) and Report Bug link (global) ) and some don’t (e.g. Acknowledgment and License).

1. I separately reported a problem with one test-engine file to @mike via Discourse,

(I don’t think either one of these is a show-stopper but all of them are annoying.)

---

<div class="post-metadata">

**Author:** ![robby](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/robby/32/7_2.png) [@robby](https://racket.discourse.group/u/robby)\
**Post date:** [April 23, 2025, 12:26am UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/4 "2025-04-23T00:26:37Z")

</div>

> [@EmEf](#):
>
> When I close all windows and use cmd-N to open a new one, I don’t get a new window. (I see this in the drracket @ HEAD too.)  
> — I do get a new window via a mouse gesture and the drop-down menu.

This has been a bug for a while now. I see that in v8.8 it behaves that way (beeping when you type cmd-n after closing the last drracket window) and in v8.3 it does something worse, not letting you close the last window at all.

---

<div class="post-metadata">

**Author:** ![jbclements](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/jbclements/32/11_2.png) [@jbclements](https://racket.discourse.group/u/jbclements)\
**Post date:** [May 3, 2025, 6:53pm UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/5 "2025-05-03T18:53:03Z")

</div>

I opened an issue (on racket/racket) for the inability to create a window using cmd-N. I also checked to see whether this issue was already present in racket/draw, didn't find anything.

---

<div class="post-metadata">

**Author:** ![jbclements](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/jbclements/32/11_2.png) [@jbclements](https://racket.discourse.group/u/jbclements)\
**Post date:** [May 3, 2025, 6:55pm UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/6 "2025-05-03T18:55:24Z")

</div>

> [@EmEf](#):
>
> 2a. Using F1 for docs fails. It does bring up a page with a search window using a file URL.

I'm not able to reproduce this. Specifically, when I open a new file in the Racket language, enter

```scheme
#lang racket

+

```

... place the cursor on the plus, and hit F1, I get a browser window that does show results for +.

I'm running macOS Sonoma 14.6.1, in case that's relevant.

---

<div class="post-metadata">

**Author:** ![jbclements](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/jbclements/32/11_2.png) [@jbclements](https://racket.discourse.group/u/jbclements)\
**Post date:** [May 3, 2025, 6:56pm UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/7 "2025-05-03T18:56:52Z")

</div>

Oh... actually, the search term is part of the file URL. I ran it again with a more ascii-friendly name (string-append), and it took me to this url:

`file:///Users/clements/Library/Racket/8.16.900/doc/search/index.html?q=string-append`

Is yours different? This could easily be messiness at the URL/browser/OS layer?

---

<div class="post-metadata">

**Author:** ![jbclements](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/jbclements/32/11_2.png) [@jbclements](https://racket.discourse.group/u/jbclements)\
**Post date:** [May 3, 2025, 7:00pm UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/8 "2025-05-03T19:00:19Z")

</div>

... and, unsurprisingly, @EmEf I'm not seeing 2b or 2c either; definitely sounds like it's all the same problem somehow. What browser/OS are you using? I'm using Firefox 137.0.2 + macOS Sonoma 14.6.1.

---

<div class="post-metadata">

**Author:** ![jbclements](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/jbclements/32/11_2.png) [@jbclements](https://racket.discourse.group/u/jbclements)\
**Post date:** [May 3, 2025, 7:16pm UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/9 "2025-05-03T19:16:01Z")

</div>

> [@EmEf](#):
>
> I separately reported a problem with one test-engine file to @mike via Discourse,

Are you referring to a different thread, or the mention you made earlier in this thread? :

> [@EmEf](#):
>
> When I run 'racket-tests' in 'htdp-test/tests/test-engine' in drracket, I get three test failures. Can you check these out please? Thanks.

---

<div class="post-metadata">

**Author:** ![EmEf](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@EmEf](https://racket.discourse.group/u/EmEf)\
**Post date:** [May 5, 2025, 1:16pm UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/10 "2025-05-05T13:16:44Z")

</div>

Yes, we know that this is an intermittent bug. But this behavior has shown up for a year now on laptops of people I was trying to help, and it now affects mine. (It seems browser-independent, and by creating a new account on my machine I was able to replicate it.)

---

<div class="post-metadata">

**Author:** ![EmEf](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@EmEf](https://racket.discourse.group/u/EmEf)\
**Post date:** [May 5, 2025, 1:17pm UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/11 "2025-05-05T13:17:55Z")

</div>

On May 3, 2025, at 2:26 PM, John Clements via Racket Discourse [notifications@racket.discoursemail.com](mailto:notifications@racket.discoursemail.com) wrote "Are you referring to a different thread, or the mention you made earlier in this thread? “

Yes, I pinged him directly.

---

<div class="post-metadata">

**Author:** ![jbclements](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/jbclements/32/11_2.png) [@jbclements](https://racket.discourse.group/u/jbclements)\
**Post date:** [May 8, 2025, 9:34pm UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/12 "2025-05-08T21:34:47Z")

</div>

Perhaps I missed it: did you say what OS this was? Also, have you tried manually entering a URL such as `file:///Users/clements/Library/Racket/8.16.900/doc/search/index.html?q=string-append` (mutatis mutandis) to see whether that works? My guess is that the OS is blocking URLs that are file pointers into the user's Library folder, I recall a problem like this before.

---

<div class="post-metadata">

**Author:** ![EmEf](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@EmEf](https://racket.discourse.group/u/EmEf)\
**Post date:** [May 9, 2025, 1:56am UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/13 "2025-05-09T01:56:41Z")

</div>

John, I re-built my workday Racket from source .. and these issues disappeared, including for the release candidate.  
This is clearly a strange issue, which I knew and which is why I didn’t think it was a show-stopper. Having said that,  
I have encountered other people (students) who had the exact problem and got pretty frustrated because of it.

---

<div class="post-metadata">

**Author:** ![jbclements](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/jbclements/32/11_2.png) [@jbclements](https://racket.discourse.group/u/jbclements)\
**Post date:** [May 11, 2025, 5:01am UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/14 "2025-05-11T05:01:01Z")

</div>

Did you hear back from @mike about the test-engine failures? I will write to him, I'd love to start the final build.

---

<div class="post-metadata">

**Author:** ![EmEf](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@EmEf](https://racket.discourse.group/u/EmEf)\
**Post date:** [May 11, 2025, 12:05pm UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/15 "2025-05-11T12:05:59Z")

</div>

No, I have not.

---

<div class="post-metadata">

**Author:** ![jbclements](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/jbclements/32/11_2.png) [@jbclements](https://racket.discourse.group/u/jbclements)\
**Post date:** [May 13, 2025, 4:31pm UTC](https://racket.discourse.group/t/testing-for-the-v8-17-release/3698/16 "2025-05-13T16:31:13Z")

</div>

I'm making a note here that this was successfully resolved via email, and that the errors we're seeing are a consequence of the difference between running the tests at the command line and running them in DrRacket.
