Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compare installed browser-ui-test version to the one used in CI #94848

Merged
merged 2 commits into from
Mar 19, 2022

Conversation

GuillaumeGomez
Copy link
Member

I happened a few times to run into (local) rustdoc GUI tests errors because I forgot to update my browser-ui-test version. I know at least two others who encountered the same problem so I think emitting a warning to let us know about this version mismatch would make it easier to figure out.

So now, I'm not too sure that this PR is the right approach because it requires to parse a Dockerfile, which feels pretty bad. I had the idea to instead store the browser-ui-test version into a docker ARG like:

ARG BROWSER_UI_TEST_VERSION=0.8.0

And then use it as such in the command to make the parsing more reliable.

Or we could store this version into a file and import this file into the Dockerfile and read it from the builder.

Any preference or maybe another solution?

r? @Mark-Simulacrum

@GuillaumeGomez GuillaumeGomez added the T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. label Mar 11, 2022
@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Mar 11, 2022
@Mark-Simulacrum
Copy link
Member

A file seems OK, maybe in src/test/rustdoc-gui -- though I'm not sure if we have access to that from within Docker, so you'll have to check. If we can't do that then reading a concrete version number from the CI directory (but still in a separate file) is likely fine.

@GuillaumeGomez GuillaumeGomez marked this pull request as ready for review March 11, 2022 16:57
@GuillaumeGomez
Copy link
Member Author

Seems like it's working like this. Does it seem acceptable to you?

@bors
Copy link
Contributor

bors commented Mar 13, 2022

☔ The latest upstream changes (presumably #94895) made this pull request unmergeable. Please resolve the merge conflicts.

@GuillaumeGomez
Copy link
Member Author

Fixed the conflict.

@Mark-Simulacrum
Copy link
Member

Did the file in src/test/rustdoc-gui not work? If not, please put the file in src/ci/docker/host-x86_64/x86_64-gnu-tools, rather than /scripts -- it is not really a global file at least right now and isn't a script.

@Mark-Simulacrum Mark-Simulacrum added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 13, 2022
@rust-log-analyzer

This comment has been minimized.

@GuillaumeGomez
Copy link
Member Author

Did the file in src/test/rustdoc-gui not work? If not, please put the file in src/ci/docker/host-x86_64/x86_64-gnu-tools, rather than /scripts -- it is not really a global file at least right now and isn't a script.

Seems like it's "out of docker scope". I'll move it to the other folder then.

@GuillaumeGomez GuillaumeGomez force-pushed the browser-ui-test-version branch 2 times, most recently from 6851afc to 3b3d383 Compare March 13, 2022 19:17
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@GuillaumeGomez GuillaumeGomez force-pushed the browser-ui-test-version branch 2 times, most recently from aa67663 to c194aa3 Compare March 13, 2022 21:23
@rust-log-analyzer

This comment has been minimized.

@GuillaumeGomez
Copy link
Member Author

Perfect, seems like I was able to make it work! \o/ Removing the GUI test changes then.

@GuillaumeGomez
Copy link
Member Author

Should be ready now.

@GuillaumeGomez
Copy link
Member Author

@Mark-Simulacrum Anything else to be done?

@GuillaumeGomez GuillaumeGomez added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Mar 16, 2022
@bors
Copy link
Contributor

bors commented Mar 18, 2022

☔ The latest upstream changes (presumably #95065) made this pull request unmergeable. Please resolve the merge conflicts.

@GuillaumeGomez
Copy link
Member Author

I added a second commit to run rustdoc GUI tests when browser-ui-test version is updated too.

@Mark-Simulacrum
Copy link
Member

@bors r+ rollup

@bors
Copy link
Contributor

bors commented Mar 18, 2022

📌 Commit c8158e9 has been approved by Mark-Simulacrum

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 18, 2022
Dylan-DPC added a commit to Dylan-DPC/rust that referenced this pull request Mar 18, 2022
…ion, r=Mark-Simulacrum

Compare installed browser-ui-test version to the one used in CI

I happened a few times to run into (local) rustdoc GUI tests errors because I forgot to update my browser-ui-test version. I know at least two others who encountered the same problem so I think emitting a warning to let us know about this version mismatch would make it easier to figure out.

So now, I'm not too sure that this PR is the right approach because it requires to parse a Dockerfile, which feels pretty bad. I had the idea to instead store the browser-ui-test version into a docker ARG like:

```docker
ARG BROWSER_UI_TEST_VERSION=0.8.0
```

And then use it as such in the command to make the parsing more reliable.

Or we could store this version into a file and import this file into the Dockerfile and read it from the builder.

Any preference or maybe another solution?

r? `@Mark-Simulacrum`
bors added a commit to rust-lang-ci/rust that referenced this pull request Mar 18, 2022
…askrgr

Rollup of 7 pull requests

Successful merges:

 - rust-lang#94115 (Let `try_collect` take advantage of `try_fold` overrides)
 - rust-lang#94295 (Always evaluate all cfg predicate in all() and any())
 - rust-lang#94848 (Compare installed browser-ui-test version to the one used in CI)
 - rust-lang#94993 (Add test for >65535 hashes in lexing raw string)
 - rust-lang#95017 (Derive Eq for std::cmp::Ordering, instead of using manual impl.)
 - rust-lang#95058 (Add use of bool::then in sys/unix/process)
 - rust-lang#95083 (Document that `Option<extern "abi" fn>` discriminant elision applies for any ABI)

Failed merges:

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 0f002eb into rust-lang:master Mar 19, 2022
@rustbot rustbot added this to the 1.61.0 milestone Mar 19, 2022
@GuillaumeGomez GuillaumeGomez deleted the browser-ui-test-version branch March 19, 2022 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants