- 
                Notifications
    You must be signed in to change notification settings 
- Fork 13.9k
[EXPERIMENTAL] Try to use NTFS dev-drive for Windows CI #134056
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
Conversation
| @bors try | 
| I'm dumb and forgot to specify try-job, oops. | 
…=<try> [EXPERIMENTAL] Try to use NTFS dev-drive for Windows CI What if this makes spurious failures less likely? Grasping at straws here. The dev-drive setup was adapted from rust-lang#131880, courtesy of `@GnomedDev's` PR. r? `@ghost` try-job: x86_64-msvc
| Apparently you just have to be faster than bors picking up the try-job, we're so back | 
      
        
              This comment has been minimized.
        
        
      
    
  This comment has been minimized.
| 💔 Test failed - checks-actions | 
| mfw | 
abcb699    to
    dff2489      
    Compare
  
    | Here we go again with a temporary test skip | 
…=<try> [EXPERIMENTAL] Try to use NTFS dev-drive for Windows CI What if this makes spurious failures less likely? Grasping at straws here. The dev-drive setup was adapted from rust-lang#131880, courtesy of `@GnomedDev's` PR. r? `@ghost` try-job: x86_64-msvc
| You might also want to try a windows-gnu build. I haven't pinpointed what breaks ld.bfd but at least on ReFS dev-drive, I couldn't get it to link Rust without failing with error. | 
      
        
              This comment has been minimized.
        
        
      
    
  This comment has been minimized.
| 💔 Test failed - checks-actions | 
| ok i was lazy and didnt test the --skip syntax... what on earth is the syntax | 
| It might be that  (I think it should really error if  | 
| Yeah, I just needed to check the invocation locally, i was lazy lol | 
| 
 Yeah, I know one of the windows jobs fail w/ ReFS at stage2 rustc from #131880, I'm mostly trying to make anything work at all first. (Which is why I'm not using ReFS atm 😆) | 
dff2489    to
    85895c1      
    Compare
  
    | ☀️ Try build successful - checks-actions | 
| @bors try | 
…=<try> [EXPERIMENTAL] Try to use NTFS dev-drive for Windows CI What if this makes spurious failures less likely? Grasping at straws here. The dev-drive setup was adapted from rust-lang#131880, courtesy of `@GnomedDev's` PR. r? `@ghost` // try-job: dist-x86_64-msvc (msi/wxs installer fails to build) // try-job: x86_64-msvc-ext1 (fails due to insufficient disk space) try-job: i686-mingw try-job: i686-msvc try-job: x86_64-msvc
| ☀️ Try build successful - checks-actions | 
| @bors try | 
      
        
              This comment was marked as resolved.
        
        
      
    
  This comment was marked as resolved.
      
        
              This comment was marked as resolved.
        
        
      
    
  This comment was marked as resolved.
1eb9122    to
    6a80e77      
    Compare
  
    | @bors try | 
…=<try> [EXPERIMENTAL] Try to use NTFS dev-drive for Windows CI What if this makes spurious failures less likely? Grasping at straws here. The dev-drive setup was adapted from rust-lang#131880, courtesy of `@GnomedDev's` PR. r? `@ghost` // try-job: dist-x86_64-msvc (msi/wxs installer fails to build) // try-job: x86_64-msvc-ext1 (fails due to insufficient disk space) try-job: i686-mingw try-job: i686-msvc try-job: x86_64-msvc
| ☀️ Try build successful - checks-actions | 
| @bors try | 
…=<try> [EXPERIMENTAL] Try to use NTFS dev-drive for Windows CI What if this makes spurious failures less likely? Grasping at straws here. The dev-drive setup was adapted from rust-lang#131880, courtesy of `@GnomedDev's` PR. r? `@ghost` // try-job: dist-x86_64-msvc (msi/wxs installer fails to build) // try-job: x86_64-msvc-ext1 (fails due to insufficient disk space) try-job: i686-mingw try-job: i686-msvc try-job: x86_64-msvc
| ☀️ Try build successful - checks-actions | 
Co-authored-by: GnomedDev <david2005thomas@gmail.com>
6a80e77    to
    c4a9699      
    Compare
  
    | I cannot get  @bors try | 
…=<try> [EXPERIMENTAL] Try to use NTFS dev-drive for Windows CI What if this makes spurious failures less likely? Grasping at straws here. The dev-drive setup was adapted from rust-lang#131880, courtesy of `@GnomedDev's` PR. r? `@ghost` // try-job: dist-x86_64-msvc (msi/wxs installer fails to build) // try-job: x86_64-msvc-ext1 (fails due to insufficient disk space) try-job: i686-mingw try-job: i686-msvc try-job: x86_64-msvc
…=<try> [EXPERIMENTAL] Try to use NTFS dev-drive for Windows CI What if this makes spurious failures less likely? Grasping at straws here. The dev-drive setup was adapted from rust-lang#131880, courtesy of `@GnomedDev's` PR. r? `@ghost` // try-job: dist-x86_64-msvc (msi/wxs installer fails to build) // try-job: x86_64-msvc-ext1 (fails due to insufficient disk space) try-job: i686-mingw try-job: i686-msvc try-job: x86_64-msvc
| 💥 Test timed out | 
What if this makes spurious failures less likely? Grasping at straws here.
The dev-drive setup was adapted from #131880, courtesy of @GnomedDev's PR.
r? @ghost
// try-job: dist-x86_64-msvc (msi/wxs installer fails to build)
// try-job: x86_64-msvc-ext1 (fails due to insufficient disk space)
try-job: i686-mingw
try-job: i686-msvc
try-job: x86_64-msvc