Skip to content
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

tests/open_wrapper: Handle the Ubuntu 64-bit time_t apocalypse #3290

Merged
merged 2 commits into from
Mar 18, 2024

Conversation

RAOF
Copy link
Contributor

@RAOF RAOF commented Mar 18, 2024

We're mostly insulated from this, but our tests need to intercept calls to open, which means that we're exposed to some glibc internals that change under _TIME_BITS=64.

Fortunately umockdev in the archive has already hit this, so adapt that fix to our use.

Fixes: #3285

@RAOF RAOF requested a review from a team as a code owner March 18, 2024 01:23
Copy link

codecov bot commented Mar 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.39%. Comparing base (8e5f965) to head (a4819a9).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3290   +/-   ##
=======================================
  Coverage   77.38%   77.39%           
=======================================
  Files        1063     1063           
  Lines       67816    67816           
=======================================
+ Hits        52482    52488    +6     
+ Misses      15334    15328    -6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

We're *mostly* insulated from this, but our tests need to intercept calls to `open`, which means
that we're exposed to some glibc internals that change under `_TIME_BITS=64`.

Fortunately umockdev in the archive has already hit this, so adapt that fix to our use.
@RAOF RAOF force-pushed the MIRENG-401-fix-time64-fallout branch from 2290c93 to 7ce2002 Compare March 18, 2024 02:11
@RAOF RAOF force-pushed the MIRENG-401-fix-time64-fallout branch from 89875a4 to a4819a9 Compare March 18, 2024 03:52
Copy link
Collaborator

@AlanGriffiths AlanGriffiths left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Magic!?

@AlanGriffiths AlanGriffiths added this pull request to the merge queue Mar 18, 2024
Merged via the queue into main with commit bc1ba1e Mar 18, 2024
34 of 36 checks passed
@AlanGriffiths AlanGriffiths deleted the MIRENG-401-fix-time64-fallout branch March 18, 2024 09:33
@Saviq Saviq mentioned this pull request Mar 28, 2024
mattkae pushed a commit that referenced this pull request Mar 28, 2024
We're *mostly* insulated from this, but our tests need to intercept
calls to `open`, which means that we're exposed to some glibc internals
that change under `_TIME_BITS=64`.

Fortunately umockdev in the archive has already hit this, so adapt that
fix to our use.

Fixes: #3285
mattkae pushed a commit that referenced this pull request Mar 28, 2024
We're *mostly* insulated from this, but our tests need to intercept
calls to `open`, which means that we're exposed to some glibc internals
that change under `_TIME_BITS=64`.

Fortunately umockdev in the archive has already hit this, so adapt that
fix to our use.

Fixes: #3285
AlanGriffiths added a commit that referenced this pull request Apr 3, 2024
We're *mostly* insulated from this, but our tests need to intercept
calls to `open`, which means that we're exposed to some glibc internals
that change under `_TIME_BITS=64`.

Fortunately umockdev in the archive has already hit this, so adapt that
fix to our use.

Fixes: #3285
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PPA FTBFS armhf/noble
2 participants