Conversation
This converts a few functions to more compact versions of themselves, and moves `RUSTDOC_MOBILE_BREAKPOINT` to main.js where it's actually used.
This is based on the compatibility data for `window.matchMedia` and `MediaQueryList`'s `EventTarget` implementation. https://developer.mozilla.org/en-US/docs/Web/API/MediaQueryList#browser_compatibility https://developer.mozilla.org/en-US/docs/Web/API/Window/matchMedia#browser_compatibility * EventTarget would require us to drop support for all Chrome versions before 39. However, we already require Chrome 49, because rustdoc requires [CSS variables]. * EventTarget would also limit us to Firefox 55, but since rust-lang#106502 rustdoc only supports Firefox > 68. * EventTarget limits us to Mobile Safari version 14, but rust-lang#102404 shows that our CSS is broken in Safari versions before 15.5. [CSS variables]: https://developer.mozilla.org/en-US/docs/Web/CSS/--*#browser_compatibility
…mpiler-errors Fix bad suggestion for clone/is_some in field init shorthand Fixes rust-lang#108470
…_output, r=pietroalbini Bugfix: avoid panic on invalid json output from libtest rust-lang#108659 introduces a custom test display implementation. It does so by using libtest to output json. The stdout is read and parsed; The code trims the line read and checks whether it starts with a `{` and ends with a `}`. If so, it concludes that it must be a json encoded `Message`. Unfortunately, this does not work in all cases: - This assumes that tests running with `--nocapture` will never start and end lines with `{` and `}` characters - Output is generated by issuing multiple `write_message` [statements](https://github.com/rust-lang/rust/blob/master/library/test/src/formatters/json.rs#L33-L60). Where only the last one issues a `\n`. This likely results in a race condition as we see multiple json outputs on the same line when running tests for the `x86_64-fortanix-unknown-sgx` target: ``` 10:21:04 �[0m�[0m�[1m�[32m Running�[0m tests/run-time-detect.rs (build/x86_64-unknown-linux-gnu/stage1-std/x86_64-fortanix-unknown-sgx/release/deps/run_time_detect-8c66026bd4b1871a) 10:21:04 10:21:04 running 1 tests 10:21:04 test x86_all ... ok 10:21:04 �[0m�[0m�[1m�[32m Running�[0m tests/thread.rs (build/x86_64-unknown-linux-gnu/stage1-std/x86_64-fortanix-unknown-sgx/release/deps/thread-ed5456a7d80a6193) 10:21:04 thread 'main' panicked at 'failed to parse libtest json output; error: trailing characters at line 1 column 135, line: "{ \"type\": \"suite\", \"event\": \"ok\", \"passed\": 1, \"failed\": 0, \"ignored\": 0, \"measured\": 0, \"filtered_out\": 0, \"exec_time\": 0.000725911 }{ \"type\": \"suite\", \"event\": \"started\", \"test_count\": 1 }\n"', render_tests.rs:108:25 ``` This PR implements a partial fix by being much more conservative of what it asserts is a valid json encoded `Message`. This prevents panics, but still does not resolve the race condition. A discussion is needed where this race condition comes from exactly and how it best can be avoided. cc: `@jethrogb,` `@pietroalbini`
Refactor `find_*_stability` functions The idea is to split the monolithic function into the 3 cases: stability, const stability, and body stability.
…GuillaumeGomez rustdoc: clean up `storage.js`
Deeply check well-formedness of return-position `impl Trait` in trait Walk the bounds of RPITITs to see if we find any more RPITITs 😸
miri: fix raw pointer dyn receivers r? `@oli-obk` Fixes rust-lang/miri#2786
…riddle Add GUI test for "Auto-hide item methods' documentation" setting Part of rust-lang#66181. r? `@notriddle`
|
@bors r+ rollup=never p=7 |
|
⌛ Testing commit beac95a with merge 27f0045cf33cf3c538ac843ac04a07414b772ec5... |
|
💔 Test failed - checks-actions |
|
@bors retry "no more archived files" |
|
⌛ Testing commit beac95a with merge e5a94c74eae87992134d52b91ccd2bc8b0c492b9... |
|
💔 Test failed - checks-actions |
|
@bors retry |
|
⌛ Testing commit beac95a with merge 78a48a7a204a21602ee9c19c9fa76ae44e4deb93... |
|
💔 Test failed - checks-actions |
|
@bors retry |
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
☀️ Test successful - checks-actions |
|
📌 Perf builds for each rolled up PR: previous master: b72e896268 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (96bd50d): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
|
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
The job Click to see the possible cause of the failure (guessed by this bot) |
Successful merges:
find_*_stabilityfunctions #109539 (Refactorfind_*_stabilityfunctions)storage.js#109542 (rustdoc: clean upstorage.js)impl Traitin trait #109545 (Deeply check well-formedness of return-positionimpl Traitin trait)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup