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

Cram tests not robust enough #1647

Open
michael-schwarz opened this issue Dec 18, 2024 · 0 comments
Open

Cram tests not robust enough #1647

michael-schwarz opened this issue Dec 18, 2024 · 0 comments
Milestone

Comments

@michael-schwarz
Copy link
Member

Locally, I get a bunch of errors of the type (for various things):

+++ b/_build/.sandbox/7396a923cc6398b0b3f839e1fce54e87/default/tests/regression/56-witness/66-ghost-alloc-lock.t.corrected
@@ -20,13 +20,13 @@
   - entry_type: ghost_instrumentation
     content:
       ghost_variables:
-      - name: alloc_m559918035_locked
+      - name: alloc_m135980175_locked
         scope: global
         type: int
         initial:
           value: "0"
           format: c_expression
-      - name: alloc_m861095507_locked
+      - name: alloc_m349172907_locked
         scope: global
         type: int
         initial:
@@ -46,7 +46,7 @@
           column: 3
           function: t_fun
         updates:
-        - variable: alloc_m559918035_locked
+        - variable: alloc_m135980175_locked
           value: "1"
           format: c_expression

However, those things work in the CI...

@sim642 suspects it has to do with vids leaking into the names of ghost variables, which is not really stable across version.

@sim642 sim642 added this to the v2.6.0 milestone Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants