Skip to content

Conversation

@ivanpauno
Copy link
Member

@ivanpauno ivanpauno commented Nov 16, 2020

It seems that I ran CI in #1408 using master instead of the appropriate branch πŸ€¦β€β™‚οΈ .

I think this fixes the Windows issues, if not I'm going to revert:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

Signed-off-by: Ivan Santiago Paunovic <[email protected]>
@ivanpauno ivanpauno added the bug Something isn't working label Nov 16, 2020
@ivanpauno ivanpauno self-assigned this Nov 16, 2020
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
@ivanpauno
Copy link
Member Author

ivanpauno commented Nov 16, 2020

The macos failure was also introduced in #1408, but it's because this line here doesn't make sense (the pointer is null).

I'm not fixing that here to avoid rerunning CI, I can fix that simple error tomorrow.

@ivanpauno
Copy link
Member Author

Windows is building ok again.
The test failure is the same problem that macOS.

@clalancette
Copy link
Contributor

I'll point out that there are also 70 new build warnings on Windows, all in qos_overridding_options.hpp

@ivanpauno
Copy link
Member Author

Thanks @clalancette, I didn't see that.
I will revert #1408 and open a take 2 PR tomorrow.

@ivanpauno ivanpauno closed this Nov 16, 2020
@clalancette clalancette deleted the ivanpauno/fix-windows branch January 15, 2021 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants