-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
Rollup of 6 pull requests #150606
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
Rollup of 6 pull requests #150606
Conversation
If the tool (yarn) does not exists, spawn() raise an error, but the error message is just like a `No such file or directory`. So it is hard to understand which application/file/directory has a problem. This commit maps the error to expose the problem is around yarn.
Discovered while porting libstd to hexagon-unknown-qurt: the unwinder data size refers to the count of pointers in _Unwind_Exception but when I put the value "35" intiially for hexagon linux, I incorrectly considered the size of the exception context hexagon_thread_state_t data structure. Correct the value for hexagon linux and expand it to cover all hexagon architecture instead.
Corrected "work" to "works", and "byte vector" to "a byte vector" to match the phrasing of "a byte slice" in the documentation of the trait `AsMut` Fixes rust-lang#149609
Fixes the sentence "Attempts to converts a Vec<u8> to a CString.", where "converts" should be in the base form as it is part of the to-infinitive form.
…Mark-Simulacrum mapping an error from cmd.spawn() in npm::install If the tool (yarn) has a problem, spawn in the install() raises an error, but the error message is hard to understand which/how application/file/directory has a problem. This commit enhances the error to explain why it fails. For example, when I ran `./x test tidy --extra-checks=js`: ```bash ... tidy check tidy [extra_checks]: IO error: No such file or directory (os error 2) tidy [extra_checks]: FAIL tidy: The following check failed: extra_checks ``` .. It doesn't explain yarn has a problem (in that case, my env didn't have yarn). After this PR, the same command prints: ```bash tidy check can not run yarn install tidy [extra_checks]: IO error: unable to run yarn: entity not found tidy [extra_checks]: FAIL tidy: The following check failed: extra_checks ```
Expose kernel launch options as offload intrinsic args Allows modifying the workgroup and thread grid dimensions directly from the intrinsic call. ```rust core::intrinsics::offload(_kernel_1, [256, 1, 1], [32, 1, 1], (x,)) ``` r? `@ZuseZ4`
…-Simulacrum Correct hexagon "unwinder_private_data_size" Discovered while porting libstd to hexagon-unknown-qurt: the unwinder data size refers to the count of pointers in _Unwind_Exception but when I put the value "35" intiially for hexagon linux, I incorrectly considered the size of the exception context hexagon_thread_state_t data structure. Correct the value for hexagon linux and expand it to cover all hexagon architecture instead.
Fix a typo in the docs of AsMut for rust-lang#149609 This PR fixes the documentation of the trait `AsMut`, where in the sentence "[ ... ] interface which work with any type [ ... ]", "work" should be replaced by "works". This also changes the later "[ ... ] into a byte slice ([u8]) or byte vector (Vec<u8>) [ ... ]" to be "[ ... ] into a byte slice ([u8]) or a byte vector (Vec<u8>) [ ... ]" to maintain consistency between "a byte slice" and "a byte vector". Issue: rust-lang#149609
mir_build: Separate match lowering for string-equality and scalar-equality - Follow-up to rust-lang#150238 --- This PR takes some match-lowering code that is responsible for equality tests, and splits it into distinct code paths for string-equality and scalar-equality. The split results in more lines of code overall, but makes the separated code paths easier to understand individually. r? Nadrieril
Fix typo in the docs of `CString::from_vec_with_nul` This PR fixes the sentence "Attempts to converts a Vec<u8> to a CString." in the documentation of the method `CString::from_vec_with_nul` (line 639). This is because "converts" in that sentence should form a to-infinitive form, and therefore should be in its base form.
|
@bors r+ rollup=never p=5 |
|
☀️ Test successful - checks-actions |
|
📌 Perf builds for each rolled up PR:
previous master: 5497a36a7f In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 5497a36 (parent) -> 85c8ff6 (this PR) Test differencesShow 66 test diffs66 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 85c8ff69cb3efd950395cc444a54bbbdad668865 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (85c8ff6): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 1.5%, secondary 1.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 3.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 471.287s -> 473.026s (0.37%) |
Successful merges:
CString::from_vec_with_nul#150594 (Fix typo in the docs ofCString::from_vec_with_nul)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup