santiagomed opened a new pull request, #3417:
URL: https://github.com/apache/thrift/pull/3417

   ## Summary
   - re-enable the dedicated  CI job
   - bump the Rust toolchain pin from 1.83.0 to 1.85.1 in CI
   - update the repo  pin to 1.85.1
   
   ## Why
   The Rust CI job is currently disabled, and the previous 1.83.0 toolchain no 
longer resolves the current dependency graph cleanly. Validating the Rust 
generator change on top of a healthy dedicated Rust CI job makes the follow-up 
codegen PR easier to review.
   
   ## Validation
   - 
   - 
   running 5 tests
   test tests::must_be_able_to_use_constructor ... ok
   test tests::must_be_able_to_use_constructor_without_option_wrap ... ok
   test tests::must_be_able_to_use_constructor_with_no_fields ... ok
   test tests::unknown_union_variant_in_struct_field_is_treated_as_none ... ok
   test tests::must_be_able_to_use_defaults ... ok
   
   test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.00s
   
   
   running 0 tests
   
   test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.00s
   
   
   running 0 tests
   
   test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.00s
   
   
   running 0 tests
   
   test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.00s
   - 
   running 0 tests
   
   test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.00s
   
   
   running 0 tests
   
   test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.00s
   
   
   running 0 tests
   
   test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.00s
   
   
   running 0 tests
   
   test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; 
finished in 0.00s
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to