-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Compare installed browser-ui-test version to the one used in CI #94848
Conversation
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. |
8f725fc
to
93104ac
Compare
Seems like it's working like this. Does it seem acceptable to you? |
☔ The latest upstream changes (presumably #94895) made this pull request unmergeable. Please resolve the merge conflicts. |
93104ac
to
f6db6c5
Compare
Fixed the conflict. |
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. |
f6db6c5
to
29d7358
Compare
This comment has been minimized.
This comment has been minimized.
29d7358
to
9f3768d
Compare
Seems like it's "out of docker scope". I'll move it to the other folder then. |
6851afc
to
3b3d383
Compare
This comment has been minimized.
This comment has been minimized.
3b3d383
to
f984899
Compare
This comment has been minimized.
This comment has been minimized.
f984899
to
e77a2a7
Compare
This comment has been minimized.
This comment has been minimized.
e77a2a7
to
3c34701
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
cc66e8e
to
1cc2329
Compare
This comment has been minimized.
This comment has been minimized.
aa67663
to
c194aa3
Compare
This comment has been minimized.
This comment has been minimized.
c194aa3
to
b00b34c
Compare
Perfect, seems like I was able to make it work! \o/ Removing the GUI test changes then. |
b00b34c
to
1c35b0c
Compare
Should be ready now. |
@Mark-Simulacrum Anything else to be done? |
☔ The latest upstream changes (presumably #95065) made this pull request unmergeable. Please resolve the merge conflicts. |
1c35b0c
to
c8158e9
Compare
I added a second commit to run rustdoc GUI tests when |
@bors r+ rollup |
📌 Commit c8158e9 has been approved by |
…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`
…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
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:
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